In order to build test executables with a link line that explicitly includes init.o, fini.o, etc we need to have greater control over the order of the link args from the target_info class.
Details
Diff Detail
- Repository
- rL LLVM
Event Timeline
Are the changes that actually use this feature going to be upstreamed as well? Or are they specific to an internal build? It's never great to introduce seemingly dead or unused code.
libcxx/utils/libcxx/compiler.py | ||
---|---|---|
32 | If we just need this to pass object files to the link, then I think making it specific to that purpose might be better. IE link_objects instead of first_link_flags. |
I will find out if I can upstream the build configuration that leverages this feature.
libcxx/utils/libcxx/compiler.py | ||
---|---|---|
32 | The order of the items on the link line is critical and it's important that the items in first_link_flags appear before -lc++ -lc++abi. I don't think link_objects conveys that same sort of interface/guarantee. If first_link_flags is not clear or generic enough, it could be before_cxx_libs or something else more appropriate. |
If we just need this to pass object files to the link, then I think making it specific to that purpose might be better. IE link_objects instead of first_link_flags.