Regarding the gyp issue you created, you can specify a "flavor" to create the Makefile for, by doing something like `gyp -f make-linux --depth=.`. That ends up creating a Makefile equivalent to what would be created if ran directly on linux. That's how I do cross-compiling for my RPi from OS X: http://n8.io/cross-compiling-nodejs-v0.8/
On Wed, Jul 10, 2013 at 2:01 AM, Adam Malcontenti-Wilson < adman....@gmail.com> wrote: > Hi all, > I'm looking at writing a patch to add the functionality to specify the > target triplet in the configure to ease cross-compiling of nodejs. > > The idea is that, ideally, to cross-compile for another device or > operating system, rather than requiring complex scripts like the android > one recently merged into the master branch or one of the many others for > Raspberry Pi, you can just run './configure --target=arm-linux-androideabi > && make'. > > The patch is on GitHub, > https://github.com/adammw/node/compare/build;configure-patch.diff , > however as I know from experience it seems that every change to the > configure script to try and set cross-compiling right breaks something else > for someone somewhere and then must subsequently be reverted. I'm posting > this on the mailing list for two reasons: 1) I'm not sure if this is a > feature that anyone really wants/needs or would be considered by the core > devs, and 2) for people with exotic systems to test it out and make sure > that I haven't inadvertently broken something. > > It includes some of what was trying to be achieved in acbdabb (which was > later reverted as it caused build issues for some users), in that it can > correctly identify the host_arch, however it only does so when the target > parameter is specified (hopefully minimising issues other people will run > into - and essentially be backwards-compatible with the "old" way of > cross-compiling). > > I found also that by doing the correct thing (setting the host_arch and > build flavours), you can't cross-compile on Mac because of the way it > includes xcode settings emulation. I have filed a GYP bug report at > https://code.google.com/p/gyp/issues/detail?id=355 but I may not have > been very clear or perhaps my patch uses GYP incorrectly which is why the > error occurs. > > Feedback welcome. =) > > Thanks, > Adam. > > -- > -- > 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. > > > -- -- 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.
