Missing quotation marks in 64-bit custom build rule

1 view
Skip to first unread message
Message has been deleted

dreijer

unread,
Nov 1, 2008, 11:54:44 PM11/1/08
to Crypto++ Users
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>
Reply all
Reply to author
Forward
0 new messages