MantisBT - CMake | |||||
View Issue Details | |||||
ID | Project | Category | View Status | Date Submitted | Last Update |
0015530 | CMake | CMake | public | 2015-04-23 18:05 | 2015-11-02 09:13 |
Reporter | Bill Torpey | ||||
Assigned To | |||||
Priority | normal | Severity | feature | Reproducibility | always |
Status | closed | Resolution | won't fix | ||
Platform | x86_64 | OS | Linux | OS Version | RH6 |
Product Version | CMake 2.8.12.2 | ||||
Target Version | Fixed in Version | ||||
Summary | 0015530: is it possible to run the build as a child process of cmake? | ||||
Description | When setting environment variables in a cmake script these obviously don't survive the invocation of cmake itself, and are therefore not available to the subsequent build command (e.g., make). It would be very helpful if cmake could invoke the build as a sub-process such that any environment variables set in the cmake script would still be available. I realize that there are (many) other ways to accomplish a similar result. In our case, it would be nice to consolidate the build logic in one place (cmake), rather than to have it spread out in different scripts etc. I initially thought the --build option to cmake might do this, but it doesn't appear to (or I'm doing something wrong). | ||||
Steps To Reproduce | |||||
Additional Information | |||||
Tags | No tags attached. | ||||
Relationships | |||||
Attached Files | |||||
Issue History | |||||
Date Modified | Username | Field | Change | ||
2015-04-23 18:05 | Bill Torpey | New Issue | |||
2015-04-27 09:59 | Brad King | Note Added: 0038612 | |||
2015-04-27 09:59 | Brad King | Status | new => resolved | ||
2015-04-27 09:59 | Brad King | Resolution | open => won't fix | ||
2015-11-02 09:13 | Robert Maynard | Note Added: 0039789 | |||
2015-11-02 09:13 | Robert Maynard | Status | resolved => closed |
Notes | |||||
|
|||||
|
|
||||
|
|||||
|
|