Skip to content

Question: MergeObjCmd with windows toolchain

In m4/fp_setup_windows_toolchain.m4 we set MergeObjsCmd="" but I am unsure what this is designed to achieve.

In m4/find_merge_objects.m4 the test test -x "$MergeObjsCmd will evaluate to true so we then set MergeObjsCmd to the result of command -v $LD.

Then apparently the tests to check if the linker works pass, so despite the comment in the windows toolchain which says

LLD does not support -r

the LLD provided by windows toolchain does pass the configure check.

If you fix the test in m4/find_merge_objects.m4 to check if a variable is unset rather than empty, then I imagine the check will fall through to the next cases and they will fail.. because MergeObjsCmd=""

So all-in-all it seems that currently you have to provide a functional linker for MergeObjsCmd. What is the correct thing to do in the windows case?

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information