MantisBT - CMake
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0013602CMakeCMakepublic2012-10-24 04:482016-06-10 14:31
ReporterBoian Petkantchin 
Assigned ToKitware Robot 
PrioritynormalSeverityminorReproducibilityalways
StatusclosedResolutionmoved 
PlatformLinuxOSUbuntuOS Version12.04
Product VersionCMake 2.8.7 
Target VersionFixed in Version 
Summary0013602: SET behaves differently for environment variables and normal variables
DescriptionWhen setting a value as:
set(ENV{FOO} a b c)
the resulting value of ENV{FOO} is "a".

On the other hand
set(FOO a b c)
sets the value of FOO to be "a;b;c".

Shouldn't the two behave identically?
Steps To Reproduce
Additional Information
TagsNo tags attached.
Relationships
Attached Filestxt CMakeLists.txt (178) 2012-10-24 04:48
https://public.kitware.com/Bug/file/4530/CMakeLists.txt
Issue History
Date ModifiedUsernameFieldChange
2012-10-24 04:48Boian PetkantchinNew Issue
2012-10-24 04:48Boian PetkantchinFile Added: CMakeLists.txt
2012-10-24 06:58David ColeNote Added: 0031302
2016-06-10 14:28Kitware RobotNote Added: 0042135
2016-06-10 14:28Kitware RobotStatusnew => resolved
2016-06-10 14:28Kitware RobotResolutionopen => moved
2016-06-10 14:28Kitware RobotAssigned To => Kitware Robot
2016-06-10 14:31Kitware RobotStatusresolved => closed

Notes
(0031302)
David Cole   
2012-10-24 06:58   
Hmmmmm...

They should probably behave identically.

But if we change it now, it will give different results for people who've come to rely on the behavior as it is. On the other hand, this is the first we've heard of it after (presumably it must have been like this for) many releases.

How to fix a bug like this is always the big question.
(0042135)
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.