[JIRA] (JENKINS-13049) Expand environment variables in definition of CMake generator

[fifteenknots...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Martin Weber closed an issue as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-13049  
 
 
  Expand environment variables in definition of CMake generator   
 

  
 
 
 
 

 
Change By: 
 Martin Weber  
 
 
Status: 
 Resolved Closed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-13049) Expand environment variables in definition of CMake generator

[anthony.ber...@arm.com (JIRA)]

Anthony Berent created JENKINS-13049:


 Summary: Expand environment variables in definition of CMake 
generator
 Key: JENKINS-13049
 URL: https://issues.jenkins-ci.org/browse/JENKINS-13049
 Project: Jenkins
  Issue Type: Improvement
  Components: cmakebuilder
Affects Versions: current
Reporter: Anthony Berent
Priority: Minor


Expand environment variables in definition of CMake generator, so that one can 
set the generator to the value of an environment variable.

Justification:

I have a number of Jenkins jobs using CMake that are multi-configuration 
projects have to build on both Windows and Linux. Because the environments are 
different I have to use different CMake generators on Windows and Linux (CMake 
doesn't support Unix Makefiles on Windows or Visual Studio 9 2008 on 
Linux). At the moment the only way to do this is to use conditional build 
steps. This means that I have to define everything about the CMake step twice. 
This would be much cleaner if I could set an environment variable in the node 
configuration (e.g. CMakeDefaultGenerator) and then set the Makefile 
Generator entry to ${CMakeDefaultGenerator} in the configuration of the CMake 
builder. 

Environment variables already work in some of the other configuration fields of 
the CMake builder. For example on Windows I am setting my make command to 
${Msbuild35Exe} /t:rebuild Project.sln

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira