Displaying 7 results from an estimated 7 matches for "additionalopt".
2014 Oct 01
2
[LLVMdev] size_t?
...getting the -m64 argument?
>>
>> I recall that you copied the win32 platform toolset xml files over by
>> hand, and I don't think they will have the correct flags. If you see this
>> line in the x64 toolset.props file, replace -m32 with -m64 and try again:
>> <AdditionalOptions>-m32 -fmsc-version=1700
>> %(AdditionalOptions)</AdditionalOptions>
>>
>> In the meantime, I think Hans is trying to fix the installation of
>> those xml files and hopefully that will fix issues for other users going
>> forwards.
>>
>> On Tue,...
2014 Sep 30
2
[LLVMdev] size_t?
...sure clang is getting the -m64 argument?
>
> I recall that you copied the win32 platform toolset xml files over by
> hand, and I don't think they will have the correct flags. If you see
> this line in the x64 toolset.props file, replace -m32 with -m64 and
> try again:
> <AdditionalOptions>-m32 -fmsc-version=1700
> %(AdditionalOptions)</AdditionalOptions>
>
> In the meantime, I think Hans is trying to fix the installation of
> those xml files and hopefully that will fix issues for other users
> going forwards.
>
> On Tue, Sep 30, 2014 at 1:55 PM,...
2014 Sep 30
2
[LLVMdev] size_t?
I'm getting compile errors because size_t is getting redefined. My
"forced include file" starts with:
#if BUILDING_FOR_WINDOWS
#define NOMINMAX
/* deal with the fact that windef.h also defines BOOL */
#define BOOL WINBOOL
#include <windows.h>
#include <intrin.h>
#undef BOOL
#endif
Looking at the preprocessor expansion of a typical .cpp file, I see that
crtdefs.h
2014 Sep 29
2
[LLVMdev] Windows Installer
...gt;
> <LibraryPath>$(LLVMInstallDir)\lib\clang\3.6.0\lib\windows;$(LibraryPath)</LibraryPath>
> </PropertyGroup>
>
> <ItemDefinitionGroup>
> <ClCompile>
> <!-- Set the value of _MSC_VER to claim for compatibility -->
> <AdditionalOptions>-m64 -fmsc-version=1800
> %(AdditionalOptions)</AdditionalOptions>
> </ClCompile>
> </ItemDefinitionGroup>
> </Project>
>
> It still doesn't work... Is there something else I need to change?
>
> Regards,
> Eric
>
>
> On 9/...
2014 Oct 01
2
[LLVMdev] size_t?
...re you sure clang is getting the -m64 argument?
>
> I recall that you copied the win32 platform toolset xml files over by
> hand, and I don't think they will have the correct flags. If you see this
> line in the x64 toolset.props file, replace -m32 with -m64 and try again:
> <AdditionalOptions>-m32 -fmsc-version=1700
> %(AdditionalOptions)</AdditionalOptions>
>
> In the meantime, I think Hans is trying to fix the installation of those
> xml files and hopefully that will fix issues for other users going forwards.
>
> On Tue, Sep 30, 2014 at 1:55 PM, Eric Ma...
2014 Sep 30
2
[LLVMdev] Windows Installer
...)\lib\clang\3.6.0\lib\windows;$(LibraryPath)</LibraryPath>
>> </PropertyGroup>
>>
>> <ItemDefinitionGroup>
>> <ClCompile>
>> <!-- Set the value of _MSC_VER to claim for compatibility -->
>> <AdditionalOptions>-m64 -fmsc-version=1800
>> %(AdditionalOptions)</AdditionalOptions>
>> </ClCompile>
>> </ItemDefinitionGroup>
>> </Project>
>>
>> It still doesn't work... Is there something else I need to change?
>&...
2014 Sep 29
2
[LLVMdev] Windows Installer
Open the file toolset-vs2013.props and you'll understand what's happening
and where the path is set. It tries to fetch the LLVM installation path
from the Windows registry. Just fix this (maybe editing your registry or
editing the .props file, whatever suits you best).
On Mon, Sep 29, 2014 at 5:33 PM, Eric Mader <emader at gmx.us> wrote:
> I copied the x64 toolsets by hand and