Skip to content

Conversation

@MaartenBent
Copy link
Contributor

I tried to fix #993 myself.

The problem is that in EnvironmentConfig::ApplyEnv the active environment variables where loaded, where active is the build configuration active in the workspace.
In some cases (e.g. batch build from #993), the active build configuration is not the configuration active in the workspace.

I added a parameter to ApplyEnv to indicate what build configuration to use. ApplyEnv is only used by EnvSetter, so I also added the parameter to the relevant EnvSetter constructor.

For all the usages of the EnvSetter constructor, I added the used build configuration, or wxEmptyString when unknown.

Not of the configuration active in the workspace.

Fixes: #993
eranif added a commit that referenced this pull request Nov 6, 2015
Load environment variables of configuration being used.
    fixes: #993
@eranif eranif merged commit ac9a3b8 into eranif:master Nov 6, 2015
@MaartenBent MaartenBent deleted the correct_envvars branch November 13, 2015 18:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Batch build uses same settings for all configurations

2 participants