Order of IMPORTED target include directories

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Order of IMPORTED target include directories

Ephi Sinowitz (BLOOMBERG/ 919 3RD A)
Hi,
I would like to ensure that all include directories propagated from IMPORTED targets come after the include directories propagated from non-imported targets. On gcc the includes from IMPORTED targets are marked with -isystem which effectively moves these directories to the end of the include search path. Unfortunately not all compilers have an analagous compiler switch. Is there something else I can do to get the imported targets includes moved to the end?

Thanks
-ephi

--

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
https://cmake.org/mailman/listinfo/cmake
Reply | Threaded
Open this post in threaded view
|

Re: Order of IMPORTED target include directories

Brad King
On 04/10/2018 01:50 PM, Ephi Sinowitz (BLOOMBERG/ 919 3RD A) wrote:
> I would like to ensure that all include directories propagated from
> IMPORTED targets come after the include directories propagated from
> non-imported targets. On gcc the includes from IMPORTED targets are
> marked with -isystem which effectively moves these directories to the
> end of the include search path. Unfortunately not all compilers have
> an analagous compiler switch. Is there something else I can do to get
> the imported targets includes moved to the end?

CMake would have to be taught how to change the order during generation.
It would make sense to do that even for compilers that do not have
-isystem since that would make the directory ordering consistent with
compilers that do have -isystem.

If you want to work on this, look at IsSystemIncludeDirectory and its
call sites.

-Brad
--

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
https://cmake.org/mailman/listinfo/cmake