We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
It is possible to specify a custom linker if you are using msbuild (for example on CI) by specifying the LinkToolPath property. It works like this:
msbuild
LinkToolPath
msbuild /p:LinkToolPath:crinkler.exe ...
It might also be possible to hack this into a vcxproj file but I didn't try.
vcxproj
The text was updated successfully, but these errors were encountered:
Perhaps this is an idea?
<!-- In your library project. --> <Target Name="CrinklerTarget"> <Exec Command="$(CRINKLER_PATH).crinkler.exe /TINYHEADER /TINYIMPORT /AND-SO-ON" /> </Target>
And in the project you want to use crinkler:
<! In your demo. --> <Target Name="Name"> <MSBuild Projects="" Properties="TargetsTriggeredByCompilation=CrinklerTarget" /> </Target>
Sorry, something went wrong.
Within a .vcxproj file, use e.g. <LinkToolExe>third_party/crinkler/crinkler.exe</LinkToolExe>.
.vcxproj
<LinkToolExe>third_party/crinkler/crinkler.exe</LinkToolExe>
See https://github.com/demoscene-source-archive/oscar-s-chair/blob/master/Oscar's%20Chair.vcxproj#L25
No branches or pull requests
It is possible to specify a custom linker if you are using
msbuild
(for example on CI) by specifying theLinkToolPath
property. It works like this:It might also be possible to hack this into a
vcxproj
file but I didn't try.The text was updated successfully, but these errors were encountered: