| View Issue Details [ Jump to Notes ] | [ Print ] | ||||||||
| ID | Project | Category | View Status | Date Submitted | Last Update | ||||
| 0011842 | CMake | CMake | public | 2011-02-11 01:31 | 2016-06-10 14:31 | ||||
| Reporter | Mark MacVicar | ||||||||
| Assigned To | Kitware Robot | ||||||||
| Priority | normal | Severity | major | Reproducibility | always | ||||
| Status | closed | Resolution | moved | ||||||
| Platform | Apple Mac | OS | Mac OS X | OS Version | 10.6.6 | ||||
| Product Version | CMake 2.8.3 | ||||||||
| Target Version | Fixed in Version | ||||||||
| Summary | 0011842: CMake Xcode generator creates one project when it should create two projects | ||||||||
| Description | CMake Xcode generator creates one project when it should create two projects This issue occurred with CMake 2.8.3 When running "cmake -G Xcode" on a CMakeLists.txt containing two projects, only one xcodeproj is created with the name of the second project. Expected behavior is that two xcodeproj files would be created. | ||||||||
| Steps To Reproduce | Reproducible Steps: 1) using the CMakeLists.txt below, run "Cmake -G Xcode" ===== project(test-foo) add_executable(test-foo test-foo.c) project(test-bar) add_executable(test-bar test-bar.c) ===== a test-bar.xcodeproj is created, but no test-foo project is created. | ||||||||
| Tags | No tags attached. | ||||||||
| Attached Files | |||||||||
| Relationships | |
| Relationships |
| Notes | |
|
(0026081) David Cole (manager) 2011-04-04 12:49 |
It is expected, and customary, (although apparently not well-enforced), that there is only one PROJECT command used in any given CMakeLists.txt file. The "right" way to generate multiple .xcodeproj projects is to have multiple CMakeLists.txt files, with one PROJECT command in each. |
|
(0026093) Mark MacVicar (reporter) 2011-04-05 01:41 |
My mistake, please feel free to close this issue as invalid. If it can be put on a wishlist, that would be nice. |
|
(0030607) David Cole (manager) 2012-08-13 15:12 |
Sending old, not-recently-updated issues to the backlog. (The age of the bug alone means that nobody is actively working on it...) If an issue you care about is sent to the backlog when you feel it should have been addressed in a different manner, please bring it up on the CMake mailing list for discussion. Sign up for the mailing list here, if you're not already on it: http://www.cmake.org/mailman/listinfo/cmake [^] It's easy to re-activate a bug here if you can find a CMake developer who has the bandwidth to take it on, and ferry a fix through to our 'next' branch for dashboard testing. |
|
(0041801) Kitware Robot (administrator) 2016-06-10 14:28 |
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. |
| Notes |
| Issue History | |||
| Date Modified | Username | Field | Change |
| 2011-02-11 01:31 | Mark MacVicar | New Issue | |
| 2011-04-04 12:49 | David Cole | Note Added: 0026081 | |
| 2011-04-05 01:41 | Mark MacVicar | Note Added: 0026093 | |
| 2011-07-28 18:18 | David Cole | Assigned To | => David Cole |
| 2011-07-28 18:18 | David Cole | Status | new => assigned |
| 2012-08-13 15:12 | David Cole | Status | assigned => backlog |
| 2012-08-13 15:12 | David Cole | Note Added: 0030607 | |
| 2012-08-13 15:18 | David Cole | Assigned To | David Cole => |
| 2016-06-10 14:28 | Kitware Robot | Note Added: 0041801 | |
| 2016-06-10 14:28 | Kitware Robot | Status | backlog => resolved |
| 2016-06-10 14:28 | Kitware Robot | Resolution | open => moved |
| 2016-06-10 14:28 | Kitware Robot | Assigned To | => Kitware Robot |
| 2016-06-10 14:31 | Kitware Robot | Status | resolved => closed |
| Issue History |
| Copyright © 2000 - 2018 MantisBT Team |