LinkFileList generation needs to use quoting

[jakepetroules]

Non-Apple linkers require quoting in order to handle projects with spaces in their path.

This is handled in LdLinkerSpec when evaluating __INPUT_FILE_LIST_PATH__.

[FareesHussain]

@jakepetroules can i pick this, can you guide me through the issue

[jakepetroules]

You're welcome to try fixing it!

To give you some pointers to get started, I'd begin by looking in LinkerTools.swift near the comment "ld64 reads lines from the file using fgets, without doing any other processing."

Apple's linker needs the arguments NOT quoted, while others (at least GNU, not sure about lld) need it quoted.

You can check the type of linker using code like this:

let optionContext = await discoveredCommandLineToolSpecInfo(cbc.producer, cbc.scope, delegate)
let linkerContext = (optionContext as? DiscoveredLdLinkerToolSpecInfo)
if linkerContext?.linker == .ld64 {
    ...

You might perform quoting using code like this:

UNIXShellCommandCodec(encodingStrategy: .singleQuotes, encodingBehavior: .argumentsOnly).encode(...)

though it's worth investigating how GNU ld actually interprets quoted arguments in file lists, and whether that's by parsing through the system shell, or something else. We should then apply the reverse transformation.

Finally, you'll want to run the test suite to see if any tests need adjustment, and if necessary, introduce at least one build operation test which includes spaces in the project path such that it will trigger a build failure without your change, and builds successfully after your change.