Skip to content

build: don't print directory for GNUMake - #13042

Closed
danbev wants to merge 1 commit into
nodejs:masterfrom
danbev:build-dont-print-directory
Closed

build: don't print directory for GNUMake#13042
danbev wants to merge 1 commit into
nodejs:masterfrom
danbev:build-dont-print-directory

Conversation

@danbev

Copy link
Copy Markdown
Contributor

Currently when running make targets the directory is printed on some
operating systems (Linux for example):

$ make lintmake[1]: Entering directory '/work/node'Running JS linter..../node tools/eslint/bin/eslint.js --cache --rulesdir=tools/eslint-rules--ext=.js,.md \ benchmark doc lib test toolsmake[1]: Leaving directory '/work/node'make[1]: Entering directory '/work/node'Running C++ linter...

On other operating systems the directory is not printed. This commit
suggests adding a flag to make this consistent for GNUMake by not
printing the directory.

Checklist
  • make -j4 test (UNIX), or vcbuild test (Windows) passes
  • commit message follows commit guidelines
Affected core subsystem(s)

build

Currently when running make targets the directory is printed on some
operating systems (Linux for example):
$ make lint
make[1]: Entering directory '/work/node'
Running JS linter...
./node tools/eslint/bin/eslint.js --cache --rulesdir=tools/eslint-rules
--ext=.js,.md \
benchmark doc lib test tools
make[1]: Leaving directory '/work/node'
make[1]: Entering directory '/work/node'
Running C++ linter...
On other operating systems the directory is not printed. This commit
suggests adding a flag to make this consistent for GNUMake by not
printing the directory.
@nodejs-github-botnodejs-github-bot added the build Issues and PRs related to build files or the CI. label May 15, 2017
@danbev

Copy link
Copy Markdown
ContributorAuthor

@gibfahn

Copy link
Copy Markdown
Member

The only make directory output on the Linux job is now what comes from node-gyp, which we still want, so this looks good.

danbev added a commit to danbev/node that referenced this pull request May 17, 2017
Currently when running make targets the directory is printed on some
operating systems (Linux for example):
$ make lint
make[1]: Entering directory '/work/node'
Running JS linter...
./node tools/eslint/bin/eslint.js --cache --rulesdir=tools/eslint-rules
--ext=.js,.md \
benchmark doc lib test tools
make[1]: Leaving directory '/work/node'
make[1]: Entering directory '/work/node'
Running C++ linter...
On other operating systems the directory is not printed. This commit
suggests adding a flag to make this consistent for GNUMake by not
printing the directory.
PR-URL: nodejs#13042
Reviewed-By: Gibson Fahnestock <gibfahn@gmail.com>
@danbev

Copy link
Copy Markdown
ContributorAuthor

Landed in ad7b98b

@danbevdanbev closed this May 17, 2017
@danbev
danbev deleted the build-dont-print-directory branch May 17, 2017 10:43
anchnk pushed a commit to anchnk/node that referenced this pull request May 19, 2017
Currently when running make targets the directory is printed on some
operating systems (Linux for example):
$ make lint
make[1]: Entering directory '/work/node'
Running JS linter...
./node tools/eslint/bin/eslint.js --cache --rulesdir=tools/eslint-rules
--ext=.js,.md \
benchmark doc lib test tools
make[1]: Leaving directory '/work/node'
make[1]: Entering directory '/work/node'
Running C++ linter...
On other operating systems the directory is not printed. This commit
suggests adding a flag to make this consistent for GNUMake by not
printing the directory.
PR-URL: nodejs#13042
Reviewed-By: Gibson Fahnestock <gibfahn@gmail.com>
@jasnelljasnell mentioned this pull request May 28, 2017
@gibfahngibfahn mentioned this pull request Jun 15, 2017
3 tasks
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

buildIssues and PRs related to build files or the CI.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants

@danbev@gibfahn@MylesBorins@nodejs-github-bot