Opened 12 years ago
Last modified 11 years ago
#44067 new enhancement
use "configure.includes {path1 path2}" instead of "configure.cppflags -I{path1} -I{path2}"
| Reported by: | mojca (Mojca Miklavec) | Owned by: | macports-tickets@… |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | base | Version: | 2.3.0 |
| Keywords: | Cc: | neverpanic (Clemens Lang), larryv (Lawrence Velázquez) | |
| Port: |
Description
Given that some build systems like CMake don't directly support CPPFLAGS (see #42872) (but also for other reasons) it would be nice to specify the include paths with an array of paths as opposed to "hardcoded" configure.cppflags -I{path1} -I{path2} -I{path3}.
The advantage of this approach would be that one could easily switch to -isystem {path1} -isystem {path2} or set CMAKE_INCLUDE_PATH={path1}:{path2} or whatever, depending on OS version, build system etc.
A similar flag would be nice for library paths ('-L/opt/local/lib') and framework paths (-F/opt/local/Library/Frameworks).
Note: See
TracTickets for help on using
tickets.
Cc Me!