-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Overriding default flags in common.gypi #1087
Comments
I think the answer is no. node-gyp doesn't set /MP itself, it inherits it from node's common.gypi. As a workaround:
|
Got it. One last question, would that be the same if I wanted to change |
You might be able to override that with a If that works for you, you could file an issue with nodejs/node requesting that node switches over to |
sounds good. Thank you for the help! |
As a follow-up to this: I am finding that adding Interestingly, I find in the file
I think this needs to be removed from common.gypi as it makes the |
Forcing this option makes the option ```MultiProcessorCompilation``` in ```msvs_settings``` useless. It also means that one cannot use ```#import``` or they will be faced with this error when trying to build: ``` error C2813: #import is not supported with /MP (compiling source file...) ``` Please see additional discussion of this here: nodejs/node-gyp#1087 and here: nodejs/node-gyp#26
FYI: GYP allows for removing items from list with the {
'targets': [
{
'target_name': 'binding',
'defines': [ 'V8_DEPRECATION_WARNINGS=1' ],
'sources': [ 'binding.cc' ],
'msvs_settings': {
'VCCLCompilerTool': {
'AdditionalOptions!': [
'/MP'
]
}
}
}
]
} or using the ...
'msvs_settings': { 'VCCLCompilerTool': {
'AdditionalOptions=': []
} }
... |
@refack I'm not being able to remove the
Build output:
|
I have a case where I'd like to disable all multi-process builds on windows. Basically I'm wondering if there is a way to negate this msbuild flag /MP on the build machine machine wide.
I took a look at #26 but that seems to be for package developers, rather than as a build step after the fact, please correct me if I'm wrong.
so are there any flags, env vars, configuration files, command line argument, etc that I can set to override that either globally on the machine or when installing any npm packages?
The text was updated successfully, but these errors were encountered: