Skip to content

build: adds configure flag notargettype - #7437

Closed
eljefedelrodeodeljefe wants to merge 1 commit into
nodejs:masterfrom
eljefedelrodeodeljefe:build/notargettype
Closed

eljefedelrodeodeljefe wants to merge 1 commit into
nodejs:masterfrom
eljefedelrodeodeljefe:build/notargettype

Conversation

@eljefedelrodeodeljefe

@eljefedelrodeodeljefe eljefedelrodeodeljefe commented Jun 27, 2016 •

Copy link
Copy Markdown
Contributor
Checklist
  • make -j4 test (UNIX), or vcbuild test nosign (Windows) passes
  • tests and/or benchmarks are included
  • documentation is changed or added
  • commit message follows commit guidelines
Affected core subsystem(s)

build

Description of change

In the wake of #7440 in order to replace GYP nodejs/CTC#2, this would be the first step. Effectively ./configure --no-target-type will still compile any dependency and run js2c, but not let gyp gcc src/*.cc -c -o out/*.o and run the linker as last build step.

This can be used, as presented in the above PR, to build node-core with node itself.

In order to fully compile without gyp, it's a long way, but definitely doable

This flag is useful, to make gyp not build and link node cores /src/*.cc files.
However all dependecnies will be built.

This can be used to build node proper with an arbitrary build runner and/ or
with itself.
@mscdex mscdex added the build Issues and PRs related to Node.js builds or CI infrastructure. label Jun 27, 2016
@jasnell

jasnell commented Jun 27, 2016

Copy link
Copy Markdown
Member

@nodejs/build

@eljefedelrodeodeljefe

Copy link
Copy Markdown
Contributor Author

Ref: This is needed for #7440 but can also used in other contexts.

@rvagg

rvagg commented Jul 7, 2016

Copy link
Copy Markdown
Member

I'm not seeing anything in here that warrants doing this as a separate PR, particularly in vcbuild.bat where the new variable isn't even used. I'd suggest closing this and rolling it up in proposed changes in #7440 unless you can demonstrate usefulness outside of that work.

@jasnell

jasnell commented Mar 1, 2017

Copy link
Copy Markdown
Member

Closing due to lack of forward progress on this

@jasnell jasnell closed this Mar 1, 2017
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 Node.js builds or CI infrastructure.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants