Thanks so much. Yes I was just issuing make in the top level.
Ben: I just tried 'make -C out BUILDTYPE=Release' and that's not doing it
either. Still seeing a rebuild of the deps. I'll try a new tree also.
I have no clock skew issues on other projects, and they are on the same fs.
Any other ideas?
-Ed
On Wednesday, March 7, 2012 7:20:24 AM UTC-6, Ben Noordhuis wrote:
>
>
> > I am doing some customization of the inner workings of node.js, and am
> > rebuilding the tree frequently.
> >
> > However, I am not that familiar with gyp system - and every time I modify
> > something (for instance a small change in node.cc) I get a complete
> rebuild
> > of the dependencies. Needless to say this slows down testing of code.
> >
> > Could someone tell me how to avoid this, or point me in the right
> direction
> > in terms of documentation?
>
> `make -C out BUILDTYPE=Release` (or Debug) does an incremental build
> unless you've touched the *.gyp or *.gypi files.
>
> Check for clock skew issues if you keep getting whole tree rebuilds.
> GNU make usually but not always warns about it ("timestamp in future",
> that kind of thing). `rm -rf out` and running configure again has a
> high probability of fixing that.
>
>
--
Job Board: http://jobs.nodejs.org/
Posting guidelines:
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 post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en
