Brad King wrote: > IIUC currently real library paths like foo.framework/foo have no > special handling right now. They are (correctly) not split and > there is no include directory added for them.
Correct. > So, the question is: do we want to add *new* special handling for > library paths inside frameworks to also add include directories? Yep. > I think this makes sense as long as it is only for raw paths and > not imported targets (which can solve this with usage reqs). Yes. > Any > project depending on this will already have platform-specific > code to #include with the framework name. Yes. I'm not familiar enough with mac or frameworks myself to know how useful or 'expected' this new behavior would be? Thanks, Steve. -- Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
