On 17/06/15 16:29, Michael Jackson wrote:
> Just to follow up with this issue in case anyone else has issues with Xcode
> here is what happened. Thanks to Gregor for taking a look at the generated
> project file he was able to identify an issue where there were file paths in
> the form of "//" inside the project file. They specifically showed in the
> form of: /* // */. This was enough to throw the Xcode parser and send Xcode
> into the spin-of-death. The root cause of the issue is that I had a cmake
> variable that held all my source files. In that list was a file path, where
> the path was completely created through cmake variables,
>
> set(FOO_FILE "${SomethingLib_path}/${SOME_HEADER_PATH})
>
> but neither of those variables had been defined for this project. (Copy paste
> mistake). This resulted in the cmake variable (FOO_FILE from above) being
> empty but still included as a source in the add_library() call. Fixing the
> cmake variables fixed the Xcode generation issue.
I will create a topic branch with a fixed Xcode generator.
Thanks,
Gregor
--
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:
http://public.kitware.com/mailman/listinfo/cmake
