On 06/02/13 15:05, Micheil Smith wrote:
> Minor thought on this: Isn't the general "change the build output directory"
> done with a PREFIX flag?
I thought about inverting the logic since Gyp was originally meant to be able
to support out-of-tree builds by starting in the
build directory.
That can make use of the configure "--srcdir" option and Make's $(srcdir).
Unfortunately, despite several hours messing about with it, because of some
Chrome-specific hacks to Gyp involving the "--depth" option, I've found no way
to persuade Gyp to write the
node*{target,host}.mk files to the build directory. Instead it writes them to a
relative path calculated based on the source's location but applied to the
build directory - which ends up creating an
entire new directory hierarchy in some random grand-parent of the build
directory.
I'll take another look at this approach when I have more time but for now my
current patch works for building. I noticed whilst investigating "--srcdir"
options that I've missed some paths in the
Makefile for some of the doc and test targets; I'll deal with them this weekend.
--
--
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 nodejs@googlegroups.com
To unsubscribe from this group, send email to
nodejs+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en
---
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 nodejs+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
