Missing quotation marks in 64-bit custom build rule

[dreijer]

Hi,

The 64-bit compilation of Crypto++ 5.5.2 fails when trying to compile
the assembly file if the path to the library includes spaces. For
instance, for the Release configuration, the custom build rule looks
as follows:

<FileConfiguration
        Name="Release|x64"
        >
        <Tool
                Name="VCCustomBuildTool"
                CommandLine="ml64.exe /c /nologo /Fo&quot;$(IntDir)
\x64masm.obj&quot; /Zi $(InputPath)&#x0D;&#x0A;"
                Outputs="$(IntDir)\x64masm.obj"
        />
</FileConfiguration>

I fixed the problem by adding quotation marks around $(InputPath),
like so:

<FileConfiguration
        Name="Release|x64"
        >
        <Tool
                Name="VCCustomBuildTool"
                CommandLine="ml64.exe /c /nologo /Fo&quot;$(IntDir)
\x64masm.obj&quot; /Zi &quot;$(InputPath)&quot;&#x0D;&#x0A;"
                Outputs="$(IntDir)\x64masm.obj"
        />
</FileConfiguration>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the "Crypto++ Users" 
Google Group.
To unsubscribe, send an email to [EMAIL PROTECTED]
More information about Crypto++ and this group is available at 
http://www.cryptopp.com.
-~----------~----~----~----~------~----~------~--~---