Skip to content

Conversation

Tormund
Copy link
Contributor

@Tormund Tormund commented Feb 26, 2018

Use gcc @file feature at linker phase

@Tormund
Copy link
Contributor Author

Tormund commented Feb 27, 2018

Any suggestions?

let isCmdFileUsed = cCompiler == ccGcc and linkCmd.len >= 32_767
let cmdFile = projectfile & "_linker_cmd.txt"
if isCmdFileUsed:
let gccExeIdx = linkCmd.find("-o")
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is a hacky post processing step and the non-hacky solution is to change how execLinkCmd works.

@Tormund
Copy link
Contributor Author

Tormund commented Feb 27, 2018

Workaround moved to execLinkCmd
And may also work for vcc ( but I can't test this now)
https://docs.microsoft.com/en-us/cpp/build/reference/at-specify-a-linker-response-file

Vladimir Melnichuk added 2 commits February 27, 2018 16:55
@Araq
Copy link
Member

Araq commented Oct 9, 2018

Since we now have pathutils.relativeTo there is a much nicer way of fixing this.

@Araq Araq closed this Oct 9, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants