Community
Participate
Working Groups
Build Identifier: M20110210-1200 The configure command line allows certain control variables to be set. CFLAGS is an obvious example. These variables may contain spaces which require escaping or quoting to pass them correctly into the configure script. Whilst these can be successfully provided by changing the configure command the same text does not work in the Additional Command Line Options field. Reproducible: Always Steps to Reproduce: 1. Create "hello world" autotools project using wizard 2. Configure project properties 3. Enter CFLAGS="-g -debug" into the configure -> Advanced -> Additional Command Line Options field. 4. Attempt to build project. This results in a failure to build. I have tried using single and double quotes as well as escaping (and double escaping) the space. All result in failure. Correct behaviour is observed if the CFLAGS="-g -debug" is appended to the configure command.
(In reply to comment #0) > Build Identifier: M20110210-1200 > > The configure command line allows certain control variables to be set. CFLAGS > is an obvious example. > > These variables may contain spaces which require escaping or quoting to pass > them correctly into the configure script. Whilst these can be successfully > provided by changing the configure command the same text does not work in the > Additional Command Line Options field. > I'll take a look at it. Right now only the command gets stripped of environment variables.
(In reply to comment #0) Fix has been made in master repository. You can now specify environment variables in either the configure command or in the additional options. In addition, I added code to display command-line environment variables in the configure console as the launcher just shows the command. You should see the fix shortly in our nightly builds for Juno. Unfortunately, this is too late to make Indigo SR1 but will appear on our nightly Indigo build site once SR1 is complete.
Setting target milestone.
