Uh oh!
There was an error while loading. Please reload this page.
build: clean up napi build in test-addons-clean - #13034
Conversation
gibfahn
commented
May 15, 2017
cc/ @nodejs/n-api @nodejs/build |
refack
commented
May 15, 2017
So you're exempt from dealing with |
refack
left a comment
There was a problem hiding this comment.
Approving no need for changes in vcbuild.bat
joyeecheung
commented
May 15, 2017
@refack I agree there can be similar rules in |
IMHO there's no need... (If there was any logic IMHO is should have been changed here...) |
gibfahn
commented
May 15, 2017
Interesting question, not sure if there's any difference between the two, except that if you've added some new files and not committed yet, The subtargets like |
mhdawson
commented
May 16, 2017
refack
commented
May 16, 2017
Well then you enjoy your well-thought-of Makefile targets 😞 |
@refack Hmm..I didn't realize that |
mhdawson
commented
May 16, 2017
I tend to agree that since there is a clean target for regular addons, bringing napi in line with that makes sense. If we decide that there is a better approach then a PR could address that for both the original addons and napi-addons. Any objections to landing based on that approach ? |
refack
commented
May 16, 2017
I was always +1, and as I said no need to add to |
mhdawson
commented
May 17, 2017
Landed as 6342988 |
PR-URL: nodejs#13034 Ref: nodejs#13031 Reviewed-By: Daniel Bevenius <daniel.bevenius@gmail.com> Reviewed-By: Gibson Fahnestock <gibfahn@gmail.com> Reviewed-By: Refael Ackermann <refack@gmail.com> Reviewed-By: Michael Dawson <michael_dawson@ca.ibm.com> Reviewed-By: Rajaram Gaunker <rajarams@gmail.com>
Checklist
make -j4 test(UNIX), orvcbuild test(Windows) passesRefs: #13031
Affected core subsystem(s)
build