Skip to content
New issue

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

Document msbuild's LinkToolPath property #6

Open
mrexodia opened this issue Sep 28, 2020 · 2 comments
Open

Document msbuild's LinkToolPath property #6

mrexodia opened this issue Sep 28, 2020 · 2 comments

Comments

@mrexodia
Copy link

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 /p:LinkToolPath:crinkler.exe ...

It might also be possible to hack this into a vcxproj file but I didn't try.

@MarijnStevens
Copy link

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>

@gpakosz
Copy link

gpakosz commented Aug 5, 2021

Within a .vcxproj file, use e.g. <LinkToolExe>third_party/crinkler/crinkler.exe</LinkToolExe>.

See https://github.com/demoscene-source-archive/oscar-s-chair/blob/master/Oscar's%20Chair.vcxproj#L25

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants