feature: fake linker to capture link target

[qtcdxxyuc]

Is it possible to a fake linker(ln), then we capture this information.
In this way, we can select the target we need to extract from a list.
Instead of manually specifying the target

[ianamason]

Which linker are you talking about? The one that clang calls behind our backs? Or the llvm_link we use to link bitcode?

[qtcdxxyuc]

I think this linker mean /usr/bin/ld . iIf we monitor his input， can know the real library or executable program produced by the project. Not specified by the user select which lib or exe. Then extract these together.

[ianamason]

This information probably can be gleaned from the log.
Set the logging level and logging file and then look for 'linking'

Build systems rarely call ld directly. For example libtool.

[ianamason]

Can I close this @qtcdxxyuc?

[woodruffw]

Not sure if it'll help, but one of the projects that I use gllvm on also uses blight for this kind of introspection of the linker and other generic build tools: https://github.com/trailofbits/blight

It won't work in all circumstances, but it'll get you pretty far and composes painfully with gllvm on builds.

[Luweicai]

Hi, I come accross the situation that the build system use the libtool directly. How can I deal with situation?

[ianamason]

You would have to be more specific as the what the problem is.