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: fix gyp configs in debug #53605

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

legendecas
Copy link
Member

@legendecas legendecas commented Jun 27, 2024

Gyp generated build files should be able to be built in either Release/Debug mode.

  • make: single entry build file, two configurations by cli:
    make -C out BUILDTYPE=Release and make -C out BUILDTYPE=Debug.
  • msbuild: single entry build file, two configurations by cli:
    msbuild node.sln /p:Configuration=Release and
    msbuild node.sln /p:Configuration=Debug.
  • ninja: two directories in out/, build with
    ninja -C out/Release or ninja -C out/Debug.

Variables that changes with either Release or Debug configuration
should be defined in a configuration level, instead of the root level.
Example:

node/common.gypi

Lines 132 to 133 in 8e5d88b

'configurations': {
'Debug': {

This fixes generating invalid build files.

Additionally, v8_gypfiles/toolchain.gypi duplicates defines in
v8_gypfiles/features.gypi. Remove the duplications in
toolchains.gypi

Fixes: #53446

Gyp generated build files can be built in either Release/Debug mode.

- make: single directory, two configurations by cli:
  `make -C out BUILDTYPE=Release` and `make -C out BUILDTYPE=Debug`.
- msbuild: single directory, two configurations by cli:
  `msbuild node.sln /p:Configuration=Release` and
  `msbuild node.sln /p:Configuration=Debug`.
- ninja: two directories in `out/`, build with
  `ninja -C out/Release` or `ninja -C out/Debug`.

Variables that changes with either Release or Debug configuration
should be defined in a configuration level, instead of the root level.
This fixes generating invalid build files.

Additionally, `v8_gypfiles/toolchain.gypi` duplicates defines in
`v8_gypfiles/features.gypi`. Remove the duplications in
`toolchains.gypi`
@nodejs-github-bot
Copy link
Collaborator

Review requested:

  • @nodejs/gyp
  • @nodejs/v8-update
@nodejs-github-bot nodejs-github-bot added build Issues and PRs related to build files or the CI. needs-ci PRs that need a full CI run. tools Issues and PRs related to the tools directory. v8 engine Issues and PRs related to the V8 dependency. labels Jun 27, 2024
@legendecas
Copy link
Member Author

./configure --debug option is not removed as it sets the default build type as well.

configure.py Outdated Show resolved Hide resolved
Copy link
Member

@targos targos left a comment

Choose a reason for hiding this comment

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

LGTM, but it doesn't change the fact that ./configure --ninja --debug && make still builds in Release and Debug modes, right?

Co-authored-by: Mohammed Keyvanzadeh <mohammadkeyvanzade94@gmail.com>
@legendecas
Copy link
Member Author

it doesn't change the fact that ./configure --ninja --debug && make still builds in Release and Debug modes, right?

Yes, it still builds both Release and Debug products.

@legendecas legendecas added the request-ci Add this label to start a Jenkins CI on a PR. label Jul 1, 2024
@github-actions github-actions bot removed the request-ci Add this label to start a Jenkins CI on a PR. label Jul 3, 2024
@nodejs-github-bot

This comment was marked as outdated.

@nodejs-github-bot
Copy link
Collaborator

nodejs-github-bot commented Jul 8, 2024

CI: https://ci.nodejs.org/job/node-test-pull-request/60187/

Rebasing on to latest main since there were reverts on reproducible snapshot.

@nodejs-github-bot
Copy link
Collaborator

nodejs-github-bot commented Jul 9, 2024

CI: https://ci.nodejs.org/job/node-test-pull-request/60195/

Restarting since #53755 landed addressing the snapshot reproducible test.

@legendecas
Copy link
Member Author

Tried to reproduce locally and skip the sea test if the debug build is too large: #53918

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. needs-ci PRs that need a full CI run. tools Issues and PRs related to the tools directory. v8 engine Issues and PRs related to the V8 dependency.
5 participants