When parsing a link command, sometimes is not obvious if the output is a binary, versus an object or a library. The extension is tracking some special linker switches and file extensions but this is not enough, so we include sometimes more launch targets than what can really be debugged or launched via this extension.
The only solution that ensures only the binaries are listed (regardless of any new compilers/linkers or switches) is a live query of output file attributes to include only executables.
Example: github.com/FidoProject/Fido.git (the dryrun output finds one object launch target)
When parsing a link command, sometimes is not obvious if the output is a binary, versus an object or a library. The extension is tracking some special linker switches and file extensions but this is not enough, so we include sometimes more launch targets than what can really be debugged or launched via this extension.
The only solution that ensures only the binaries are listed (regardless of any new compilers/linkers or switches) is a live query of output file attributes to include only executables.
Example: github.com/FidoProject/Fido.git (the dryrun output finds one object launch target)