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

Request: support out of tree build #10748

Closed
nmschulte opened this issue Jan 12, 2017 · 7 comments
Closed

Request: support out of tree build #10748

nmschulte opened this issue Jan 12, 2017 · 7 comments
Labels
build Issues and PRs related to build files or the CI. feature request Issues that request new features to be added to Node.js.

Comments

@nmschulte
Copy link

nmschulte commented Jan 12, 2017

Currently, the configure script and Makefile assume they're being executed with the work tree as the current working directory. This isn't always the case, and supporting out-of-tree building is very useful; it supports automation, and it supports development, in the cases where the make targets change what is/is not installed.

I updated configure to support this, but failed to realize the project is not using Automake, and once I had, didn't attempt to update the Makefile. Certain tools (from the tools/ directory) are hardcoded in the Makefile rules.

@jasnell jasnell added feature request Issues that request new features to be added to Node.js. build Issues and PRs related to build files or the CI. labels Jan 12, 2017
@jbergstroem
Copy link
Member

@nmschulte:
This isn't always the case

Out of curiosity. What is your use case where in-place builds doesn't work?

@nmschulte
Copy link
Author

nmschulte commented Jan 12, 2017

What is your use case where in-place builds doesn't work?

I am currently running up against issue npm/npm#10343, and I am building (and installing) multiple versions of node, and wishing to retain the build configuration/build. This is most trivially (and typically) done by building in a separate directory for each configuration.

@sxa
Copy link
Member

sxa commented Jan 19, 2017

@nmschulte Did you tag the wrong issue in your last comment? The one you've referenced is about updates to CONTRIBUTING.md

@nmschulte
Copy link
Author

Did you tag the wrong issue in your last comment?

@sxa555, ah! I meant npm/npm#10343, indeed.

@Trott Trott added the help wanted Issues that need assistance from volunteers or PRs that need help to proceed. label Aug 2, 2017
@bnoordhuis
Copy link
Member

#10751 was closed and there haven't been requests from the community or enthusiasm from maintainers so I'm going to go ahead and close this out.

@refack refack removed the help wanted Issues that need assistance from volunteers or PRs that need help to proceed. label May 28, 2018
@refack
Copy link
Contributor

refack commented May 28, 2018

P.S. configure can now be called from anywhere:

node/configure

Lines 38 to 39 in 9f4bf4c

# If not run from node/, cd to node/.
os.chdir(os.path.dirname(__file__) or '.')

and using ninja instead of make allows building from out of tree, so this is essentially implemented.

@nmschulte
Copy link
Author

If you're looking to keep the labels accurate, I guess I should have clarified what I meant by out-of-tree: the artifacts of the build would be pwd local, so you could build different commits / patches to different build directories from the same source repository / directory.

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. feature request Issues that request new features to be added to Node.js.
Projects
None yet
Development

No branches or pull requests

7 participants