search for: _usrdll

Displaying 4 results from an estimated 4 matches for "_usrdll".

2014 Oct 02
2
[LLVMdev] Header File Not Found?
...b-dir-1] /IC:\[top-level-dir]\[source-dir]\[sub-dir-2] /IC:\[top-level-dir]\[dest-dir]\[dest-sub-dir]\include /IC:\[SDK-dir]\[SDK-source-dir]\[SDK-sub-dir]\include /IC:\[SDK-dir]\[SDK-source-dir]\[SDK-sub-dir]\include\[include-sub-dir] /Zi /nologo /W3 /WX- /Od /D WIN32 /D _DEBUG /D _WINDOWS /D _USRDLL /D [elided] /D _t_env_os_WIN32 /D [also-elided] /D _SCL_SECURE_NO_WARNINGS /D _CRT_SECURE_NO_WARNINGS /D OBJC_OLD_DISPATCH_PROTOTYPES=1 /D _WIN64 /D "__x86_64__= 1" /D _WINDLL /D _UNICODE /D UNICODE /Gm- /EHsc /RTC1 /MDd /GS /fp:precise /Zc:wchar_t /Zc:forScope /Fo"Debug\x64\\&qu...
2014 Oct 01
2
[LLVMdev] size_t?
...gt;> >> Later on, I get an error saying that crtdefs.h is trying to redefine >> size_t from an unsigned int to an unsigned long long... >> >> Perhaps one of my preprocessor defines is causing these errors: >> >> WIN32 >> _DEBUG >> _WINDOWS >> _USRDLL >> _SCL_SECURE_NO_WARNINGS >> _CRT_SECURE_NO_WARNINGS >> _WIN64 >> _x86_64_ = 1 >> >> (I added the "SECURE_NO_WARNINGS" defines when I ported an earlier >> version of this code to VS 2005; don't remember why any more...) >> (There are a...
2014 Oct 01
2
[LLVMdev] size_t?
...gt; ^ ~~~~~~~~~~~~~~~~~~~ > > Later on, I get an error saying that crtdefs.h is trying to redefine > size_t from an unsigned int to an unsigned long long... > > Perhaps one of my preprocessor defines is causing these errors: > > WIN32 > _DEBUG > _WINDOWS > _USRDLL > _SCL_SECURE_NO_WARNINGS > _CRT_SECURE_NO_WARNINGS > _WIN64 > _x86_64_ = 1 > > (I added the "SECURE_NO_WARNINGS" defines when I ported an earlier version > of this code to VS 2005; don't remember why any more...) > (There are a couple of other defines that are...
2014 Sep 30
2
[LLVMdev] size_t?
Hi Reid, I copied the x64 toolsets by hand; they got installed to C:\Program Files (x86)\LLVM\tools\msbuild\x64; they just didn't get moved correctly by install.bat. I just verified that the LLVM-vs2013 toolset.props is correct. If it is a bitness problem, perhaps I'm failing to define something correctly? Regards, Eric On 9/30/14, 11:29 AM, Reid Kleckner wrote: > This looks