/usr/bin/ld: skipping incompatible foo.so when searching for foo
remove -m32 in command line flags to build with 32bit binary, you have to install sudo apt-get install gcc-multilib and sudo apt-get install ia32-libs-dev
remove -m32 in command line flags to build with 32bit binary, you have to install sudo apt-get install gcc-multilib and sudo apt-get install ia32-libs-dev
As far as I’m concerned, the single most important thing about porting C/C++ code to 64-bit Windows is to test your application with MEM_TOP_DOWN allocations enabled (AllocationPreference registry value) as described in 4-Gigabyte Tuning: To force allocations to allocate from higher addresses before lower addresses for testing purposes, specify MEM_TOP_DOWN when calling VirtualAlloc or set … Read more
If you want to compile and link for 32 bit using cmake use this for creating libraries and binaries: Creating libraries: add_library(mylib SHARED my_source.c) set_target_properties(mylib PROPERTIES COMPILE_FLAGS “-m32” LINK_FLAGS “-m32”) creating executables: add_executable(mybin sources.c) set_target_properties(mybin PROPERTIES COMPILE_FLAGS “-m32” LINK_FLAGS “-m32”)
Hit Ctrl+Alt+Del to open the Windows Task manager and switch to the processes tab. 32-bit programs should be marked with *32.
A LongPtr is always correct for your process. You do not need to worry about its size. You do not need the WIN64 constant to use it. In fact, the only constant you normally need is VBA7 that tells you whether the LongPtr is even available. If it is, use it, if it’s not, you … Read more
This is an elaboration of the answer from Springy76. Do this: public class AssemblyResolver { public static void HandleUnresovledAssemblies() { AppDomain currentDomain = AppDomain.CurrentDomain; currentDomain.AssemblyResolve += currentDomain_AssemblyResolve; } private static Assembly currentDomain_AssemblyResolve(object sender, ResolveEventArgs args) { if (args.Name == “System.Data.SQLite”) { var path = Path.Combine(pathToWhereYourNativeFolderLives, “Native”); if (IntPtr.Size == 8) // or for .NET4 use … Read more
That depends on which variant of toolchain you’re currently using. Both DWARF and SEH variants (which come starting from GCC 4.8.0) are only single-target. You can see it yourself by inspecting the directory structure of their distributions, i.e. they contain only the libraries with either 64- or 32-bit addressing, but not both. On the other … Read more
That line you see indicates how the python interpreter was built. Breaking it down: Python 2.7 — Python version (r27:82525, Jul 4 2010, 07:43:08) — The build date and revision from src trunk that was used to build this. [MSC v.1500 64 bit (AMD64)] — Compiled with MSVC compiler targeting 64-bit on win32 — All … Read more
Yes, a 32-bit architecture is limited to addressing a maximum of 4 gigabytes of memory. Depending on the operating system, this number can be cut down even further due to reserved address space. This limitation can be removed on certain 32-bit architectures via the use of PAE (Physical Address Extension), but it must be supported … Read more
From TechNet article on 64-bit editions of Office 2010: If you have installed Office 2010 including Microsoft Outlook 2010, Outlook sets a registry key named Bitness of type REG_SZ on the computer on which it is installed. The Bitness registry key indicates whether the Outlook 2010 installation is 32-bit or 64-bit. This may be useful … Read more