MantisBT - CMake
1. CMake leaves the product paths (paths to library files and executables) blank, so it's impossible to tell which has been build, and which hasn't.
2. Many paths in Xcode must be relative paths from the Xcode project for Xcode to work properly. CMake accounts for this nuance, but it does so as if the project file were at the root of the source. Doing any out of source builds (the common case, I believe) results in the inability to open files in sub-projects (projects that were included by a CMake "add_subdirectory(project_dir)" that has a CMakeLists.txt with a "project(project_name)" statement at the top of it, which were most likely external to the project, and through the use of git submodules or similar mechanisms, were included as part of the build of the outer project.
1. On a Mac with Xcode: from the root ("TheMainApp/") do a "mkdir build; cd build; cmake -G Xcode .."
2. Do a "open TheMainApp.xcodeproj"
3. In the file browser panel (on the left side of the Xcode window) Look at the "Product" folder, as well as the "ConsolePrinter" and "Sleeper" folders. You will see that they are in red.
Under normal circumstances, the Product folder files will be red until they are built, but because the path doesn't exist (that can be seen in Xcode 4 or later in the panel on the right side of the window) these Products will always be red.
To whomever picks-up this ticket: Thank you very much for the great product that is CMake! It has made my cross platform development much easier.
TheMainApp.tar.bz2 (15,207) 2012-07-06 07:46https://public.kitware.com/Bug/file/4381/TheMainApp.tar.bz2