MantisBT - CMake
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0010901CMakeCMakepublic2010-06-28 07:482016-06-10 14:31
ReporterAndres G. Aragoneses 
Assigned ToBrad King 
PrioritynormalSeverityfeatureReproducibilityalways
StatusclosedResolutionmoved 
PlatformOSOS Version
Product VersionCMake-2-8 
Target VersionFixed in Version 
Summary0010901: Cannot set a value to an environment variable for a custom command
DescriptionI have seen that you cannot set a value to an environment variable for a custom command, and the workaround is to create a new cmake file that gets called by a custom command [1] which seems very hacky.

Any idea if this is desirable to fix decently in the future?
Steps To Reproduce
Additional Information[1] http://www.mail-archive.com/cmake@cmake.org/msg15583.html [^]
TagsNo tags attached.
Relationships
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2010-06-28 07:48Andres G. AragonesesNew Issue
2010-07-13 09:23Bill HoffmanStatusnew => assigned
2010-07-13 09:23Bill HoffmanAssigned To => Brad King
2010-07-13 10:08Brad KingNote Added: 0021384
2012-08-13 10:36Brad KingStatusassigned => backlog
2012-08-13 10:36Brad KingNote Added: 0030484
2016-06-10 14:28Kitware RobotNote Added: 0041718
2016-06-10 14:28Kitware RobotStatusbacklog => resolved
2016-06-10 14:28Kitware RobotResolutionopen => moved
2016-06-10 14:31Kitware RobotStatusresolved => closed

Notes
(0021384)
Brad King   
2010-07-13 10:08   
We've considered doing this several times. However the implementation is very difficult because we have to convince the native build tool (make, VS IDE, Xcode) to set the value. Furthermore, it would not be possible to do any logic evaluation to compute the proper value at build time.
(0030484)
Brad King   
2012-08-13 10:36   
Sending issues I'm not actively working on to the backlog to await someone with time for them.

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 or contributor who has the bandwidth to take it on.
(0041718)
Kitware Robot   
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.