Honestly, a lot of modules fail, sometimes in subtle ways, in debug mode,
(including very popular ones like "websocket" used by socket.io), as it is
very common for the javascript-side to simply
"require('../build/Release/foo');", which will not be the right path on a
debug build, or might be a path to something stale from a previous build,
etc. When I was forced to use a "debug" version of Node at some point
(which makes npm implicitly install in --debug mode by default), I
eventually had to alias npm to always pass --debug=false to have anything
with native code not break/misbehave, so I am now very wary of building
anyone else's module in debug mode.
A much simpler question might be, can you just build your one module in
debug, and leave everything else alone?
On Thursday, April 23, 2015 at 11:57:51 AM UTC-7, ryandesign wrote:
>
>
> On Apr 23, 2015, at 5:26 AM, Gabriel Schulhof wrote:
>
> > When I run npm install on my package which contains a native addon, it
> works. However, when I run npm install --debug, it fails, because one of
> the files uses DEBUG as an enum member, and so that effectively gets edited
> out by the preprocessor, breaking the syntax of the enum. I don't control
> the code that contains the offending enum member, so I was wondering if
> there is a way to tell node-gyp via binding.gyp to not add -DDEBUG to the
> command line when building in debug mode. It also adds -D_DEBUG, so that
> should still be sufficient.
> >
> > Is it possible?
>
> I don't know. You should report the problem to whoever wrote the module
> that fails, so that they can fix it.
>
>
>
>
--
Job board: http://jobs.nodejs.org/
New group rules:
https://gist.github.com/othiym23/9886289#file-moderation-policy-md
Old group rules:
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
---
You received this message because you are subscribed to the Google Groups
"nodejs" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/nodejs/52202458-84d1-4375-82da-49d3eb58b6c6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
