EXTRA_CUSTOM_FRAMEWORKS - different path needed for CMake, but wrong in Xcode
dacrome opened this issue · 7 comments
Hey FRUT devs,
thanks for this project, we really need the ability to build our desktop app via command line / CI.
We have a problem with the EXTRA_CUSTOM_FRAMEWORKS paths. We have custom c++ libs which we are using as frameworks in Xcode and Xcode expects to have a path which are relativ to the xcodeproj file. But when building with cmake, the paths have to be different, because it needs to be relativ to the CMakeLists.txt. This is only because the cmake build checks if the paths existing. Projucer is not doing that, the content of "Extra Custom Frameworks" is only copied to the xcode project file.
Is it possible to switch off the check of whether the path exists for the cmake build?
or how can I configure it to able to build with cmake and have the path correct for xcode?
Thanks
David
Hi David,
Thanks for opening this issue. Based on what you are describing, it seems that there is a bug in Reprojucer.cmake. I'll have a look as soon as possible.
Cheers,
Alain
wow, awesome! That was fast! Thanks!
I give it a try today, and give you feedback later.
Hey @McMartin,
the paths in EXTRA_CUSTOM_FRAMEWORKS are working now, but we found out we have the same problem with the HEADER_SEARCH_PATHS. I have to change them before running reprojucer...
Side note: When I changed the header search paths the compiler can use these headers and start to compile, but I get compile errors because our dependencies (c++ libs) using ambiguous references. I know this is not part of your project, but when we generate the xcodeproj file with Projucer, we dont have these kind of errors... so I compared both Xcode configurations. e.g. the Projucer generated Xcode config has user-defined setting MTL_HEADER_SEARCH_PATHS created. The are some more different settings and I try to find out what is the important difference.