Notes |
|
(0035571)
|
Brad King
|
2014-03-31 09:57
|
|
Why do you need to change the SYMROOT? If there is a good reason then CMake should have a first-class interface to do it. Hacking the attribute value may make object locations computed in cmGlobalXCodeGenerator::GetObjectsNormalDirectory wrong. |
|
|
(0035593)
|
Michał Cichoń
|
2014-04-01 03:01
|
|
Default value for SYMROOT in Xcode project is 'build' and there is no way to keep it that way because CMake generator always replace it with absolute path to its output directory.
We relay on default value. |
|
|
(0035598)
|
Brad King
|
2014-04-01 09:37
|
|
Re 0014853:0035593: I'd like to understand your use case in more detail, please. How and why do you rely on the default value? |
|
|
(0035643)
|
Michał Cichoń
|
2014-04-07 02:23
|
|
We have build scripts spread on multiple branches written with assumption that build artifacts lands in default directory. It was more reasonable to change CMake than to edit scripts to match generated project.
Bottom line is I was unable to create Xcode project with settings that match default values and I think it may be an issue. If you decide it is not we just stick to modified version. |
|
|
(0042525)
|
Kitware Robot
|
2016-06-10 14:29
|
|
Resolving issue as `moved`.
This issue tracker is no longer used. Further discussion of this issue may take place in the current CMake Issues page linked in the banner at the top of this page. |
|