How can I check the exact commands passed to the linker? lazarus / 13-General ---------------------------------------------------------------------- vfclists · 2016-09-19 00:16 I have configured a project to link in some precompiled object files by adding their path to the libraries text box in the Project Options dialog, where it says Libraries (-Fl), but it doesn't seem to work properly. Is there some option of saving the exact commands passed to the linker so I can check it properly? In effect is does Lazarus have a way to generate as script that you can run on the command line to check what is going on? ---------------------------------------------------------------------- Phil · 2016-09-19 00:26 With FPC, you can use the -Cn switch to omit the link phase. Then look at the ppas.sh and link.res files which are normally deleted. ---------------------------------------------------------------------- marcov · 2016-09-19 07:39 Note that on windows the linker is internal. ---------------------------------------------------------------------- vfclists · 2016-09-19 08:40 Does that mean it is built into the fpc.exe itself? I am using Windows and that may be why I didn't see a separate link command in ppas.s Quote from: marcov on September 19, 2016, 09:39:57 amNote that on windows the linker is internal. ---------------------------------------------------------------------- molly · 2016-09-19 09:09 Note that i only know this for fpc, no idea what lazarus does. if you add -va you also see the object files it is attempting to locate. In case of static linking and compiling the main project file the compiler will let you know at least which symbols are missing. Additionally you could perhaps use the -sh switch. It generates a .bat and link file for external linking on the host, but afaik it should be more or less identical to what the internal linker tries to attempt ? ---------------------------------------------------------------------- marcov · 2016-09-19 09:26 Quote from: vfclists on September 19, 2016, 10:40:36 amDoes that mean it is built into the fpc.exe itself? I am using Windows and that may be why I didn't see a separate link command in ppas.s Well, ppc386.exe, but yes. You can link eternally by adding -Xe though.