Bugzilla – Full Text Bug Listing
| Summary: | options passed to miscellaneous/linker flags should be allowed to be passed at the end of the link command | ||
|---|---|---|---|
| Product: | [Tools] CDT | Reporter: | charlls_quarra |
| Component: | cdt-build-managed | Assignee: | Project Inbox <cdt-build-managed-inbox> |
| Status: | NEW --- | QA Contact: | Jonah Graham <jonah> |
| Severity: | enhancement | ||
| Priority: | P3 | CC: | yevshif |
| Version: | 8.0 | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
added a new enhancement request for having the indexer see the included paths (https://bugs.eclipse.org/bugs/show_bug.cgi?id=326845) |
Build Identifier: 20100917-0705 build variables for linkage steps (like pkg-config --cflags..) can be passed to the compiler adding to properties->c++ build->settings->tool settings->c++ compiler(miscellaneous) and to 'other flags' textbox like ${MY_PKGCONFIG_VAR} (that will make it compile, but won't get so far as update the indexer, but thats another story). However, if one tries to do the same thing for the linkage step (adding to tool settings->c++ linker(miscellaneous) 'linker flags'), then any options in the build variable like -L and -l are placed at the beggining of the command (before the input .o files, for instance), and that will not work in general (compilers like gcc linker will only proceed to link options after the object source files) Reproducible: Always Steps to Reproduce: 1.add a build variable for a link step that includes -L or -l options 2.add the build variable to properties->c++ build->settings->tool settings->c++ linker(miscellaneous) 'linker flags 3.