Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

build: avoid calling configure twice from vcbuild #2128

Closed

Conversation

jbergstroem
Copy link
Member

This was introduced in a merge from nodejs (dcbb9e1).

/R= @nodejs/build

This was introduced in a merge from nodejs (dcbb9e1).
@jbergstroem
Copy link
Member Author

@jbergstroem
Copy link
Member Author

The final step after merging this PR would be removing the jenkins configure step alternatively passing noprojgen as part of the build step.

@Fishrock123 Fishrock123 added the build Issues and PRs related to build files or the CI. label Jul 8, 2015
@orangemocha
Copy link
Contributor

@jbergstroem I think there might still be some issues. I opened #2131 because it's probably faster than iterating over this PR.

@@ -86,19 +86,12 @@ if "%i18n_arg%"=="intl-none" set i18n_arg=--with-intl=none

call :getnodeversion || exit /b 1

@rem Set environment for msbuild
:project-gen
@rem Skip project generation if requested.
if defined noprojgen goto msbuild
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We still need to set the environment even if we skip project generation

@jbergstroem
Copy link
Member Author

Closed in favour of #2131.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
build Issues and PRs related to build files or the CI.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants