64-bit

Making a 64 bit shared library that dynamically links to a 32 bit library on Mac OS X Snow Leopard

[亡魂溺海] 提交于 2020-01-01 19:25:08
问题 Update: After some more reading I see that this problem is totally general, you can't mix architectures in the same process, so 64 bit Java cannot dlopen() a 32 bit library like FMOD. Is there any possible workaround for this, keeping in mind I'm writing my own C interface to the FMOD library? I need to make a 64-bit dylib on Max OS X because Java Native Access only likes 64-bit libraries on 64-bit machines. The problem is, my C source code dynamically includes FMOD which on Mac only provides

NULL definition problem on 64 bit system

二次信任 提交于 2020-01-01 18:18:34
问题 I'm running on RHEL 5.1 64 bit platfrom using gcc 4.1.2. I have a utility function: void str_concat(char *buff, int buffSize, ...); which concats char * passed in variadic list(...), while last argument should be NULL, to designate end of the arguments. On 64 bit system NULL is 8 bytes. Now to the problem. My application includes directly/indirectly 2 stddef.h files. First one is /usr/include/linux/stddef.h which defines NULL as following: #undef NULL #if defined(__cplusplus) #define NULL 0

NULL definition problem on 64 bit system

£可爱£侵袭症+ 提交于 2020-01-01 18:18:29
问题 I'm running on RHEL 5.1 64 bit platfrom using gcc 4.1.2. I have a utility function: void str_concat(char *buff, int buffSize, ...); which concats char * passed in variadic list(...), while last argument should be NULL, to designate end of the arguments. On 64 bit system NULL is 8 bytes. Now to the problem. My application includes directly/indirectly 2 stddef.h files. First one is /usr/include/linux/stddef.h which defines NULL as following: #undef NULL #if defined(__cplusplus) #define NULL 0

Error when building 64-bit Z3 on Windows

泪湿孤枕 提交于 2020-01-01 12:14:06
问题 I followed the instructions to build Z3 on a 64-bit Windows 8.1 system with Visual Studio Community 2015 by running python scripts/mk_make.py -x but when I run nmake, I get the following error: C:\Program Files (x86)\Windows Kits\8.1\include\um\winbase.h(8848): error C3861: '_InterlockedIncrement64': identifier not found C:\Program Files (x86)\Windows Kits\8.1\include\um\winbase.h(8879): error C3861: '_InterlockedDecrement64': identifier not found C:\Program Files (x86)\Windows Kits\8.1

WiX: register .NET COM component both x86 x64

断了今生、忘了曾经 提交于 2020-01-01 11:42:06
问题 I have C# COM .dll. I would like to install the .dll once, but have it be registered for both x86 and x64. Here's the WiX I have for registering only x64: <Component Id="NETDLL.dll" Directory="INSTALLDIR"> <File Id="NETDLL.dll" Name="NETDLL.dll" KeyPath="yes" Source="..\NETDLL.dll" /> <Class Id="{78BE...}" Context="InprocServer32" Description="NETDLL" ThreadingModel="both" ForeignServer="mscoree.dll"> <ProgId Id="NETDLL" Description="NETDLL" /> </Class> <RegistryValue Root="HKCR" Key="CLSID\

Getting syswow64 directory using 32-bit application

陌路散爱 提交于 2020-01-01 08:10:06
问题 I'm trying to find a file inside the system directory. The problem is that when using Environment.SystemDirectory On a x64 machine, i'm still getting the System32 directory, instead of the Systemwow64 directory. I need to get the "System32" directory on x86 machines, and "SystemWow64" directory on x64 Any ideas? EDIT: To find the SysWow64 i'm using the "GetSystemWow64Directory". (more information here: pinvoke Notice that on non-x64 machines - result is '0'. Hope this helps someone 回答1: Use

In C++, what is the difference between 1 and 1i64?

倖福魔咒の 提交于 2020-01-01 07:33:06
问题 I'm converting some 32-bit compatible code into 64-bit - and I've hit a snag. I'm compiling a VS2008 x64 project, and I receive this warning: warning C4334: '<<' : result of 32-bit shift implicitly converted to 64 bits (was 64-bit shift intended?) Here's the original line of code: if ((j & (1 << k)) != 0) { And here's what it looks like if I follow Microsoft's advice: if ((j & (1i64 << k)) != 0) { Is this safe to do, when the code will be compiled on both 32-bit and 64-bit systems? If so,

Why are there differing definitions of INT64_MIN? And why do they behave differently?

给你一囗甜甜゛ 提交于 2020-01-01 06:52:09
问题 The stdint.h header at my company reads: #define INT64_MIN -9223372036854775808LL But in some code in my project, a programmer wrote: #undef INT64_MIN #define INT64_MIN (-9223372036854775807LL -1) He then uses this definition in the code. The project compiles with no warnings/errors. When I attempted to remove his definition and use the default one, I got: error: integer constant is so large that it is unsigned The two definitions appear to be equivalent. Why does one compile fine and the

Clipboard Copy-Paste doesn't work in a service on Win Server 2008/Vista 64bit

≡放荡痞女 提交于 2020-01-01 06:30:30
问题 Update: This issue has been resolved. you can read about the solution in here: Creating a process in a non-zero session from a service in windows-2008-server? Thanks everyone! Hi, I am trying to use Clipboard API (in Delphi) to extract images from Word documents. my code works OK in Windows XP/2003 but in windows 2008 64 bit it doesn't work. in win 2008 i get an error saying that Clipboard.Formats is empty and doesn't contain any format. The image seems to be copied to the Clipboard (i can

Clipboard Copy-Paste doesn't work in a service on Win Server 2008/Vista 64bit

怎甘沉沦 提交于 2020-01-01 06:30:10
问题 Update: This issue has been resolved. you can read about the solution in here: Creating a process in a non-zero session from a service in windows-2008-server? Thanks everyone! Hi, I am trying to use Clipboard API (in Delphi) to extract images from Word documents. my code works OK in Windows XP/2003 but in windows 2008 64 bit it doesn't work. in win 2008 i get an error saying that Clipboard.Formats is empty and doesn't contain any format. The image seems to be copied to the Clipboard (i can