1) gyp is a hard dependency. ICU is not. I'm not aware of gyp being available as a stand alone package on any Linux I use. Personally, I hate it. I wish Chromium/v8 team would go to a plain Makefile build system. But, its their project, not mine. Use the following in your v8 pull folder to get around having to do a 'make dependencies': svn co http://gyp.googlecode.com/svn/trunk build/gyp
2) Most of your questions about ICU are answered here <https://code.google.com/p/v8/wiki/I18NSupport>. The short, you can use make use_system_icu=1 or make i18nsupport=off 3) See #1. -L On Thu, Oct 3, 2013 at 1:49 PM, Anatol Pomozov <[email protected]> wrote: > Hi, > > I am speaking from Linux Arch package manager point of view who wants to > make a great v8 package for its favorite distro. > > When I build v8 following things look non-typical for me: > > 1) v8 build process pulls gyp and ICU sources from a third_party repo. I > understand that you need it for users who has no tools installed (e.g. on > Windows) but Linux/OSX developers use package managers actively. The package > managers usually include these tools in their repos/PPA/.. In this build > process should not pull any third-party projects. It should use 'system' > version of the tools. For example Arch has packages both for GYP and ICU. Is > there any way to "turn-off" dependency pull/build? > > 2) What is more important is that system version of ICU differs from what v8 > uses. Arch has latest stable version (51) and v8 pulls version 46. Why V8 > does not use the latest ICU version? Instead of going into shared libraries > hell and having multiple version of libicu*.so I would prefer that packages > use the same version (i.e. 51). Is there any patch that ports v8 to ICU51? > It would be really great if I can combine it with #1, avoid ICU compilation > and instead use system version of ICU library. > > Bottom line: how to compile current v8 HEAD against system ICU version 51 > (and btw 52 will be released really soon). > > > 3) This is a minor issue though. Have you guys though about making your > build Python3 friendly? You don't have python extensions so most likely it > will be easy to make the scripts both 2.7 and 3.3 compatible. This will make > life easier for those who moved to Python3.3 as a default version. > > -- > -- > v8-users mailing list > [email protected] > http://groups.google.com/group/v8-users > --- > You received this message because you are subscribed to the Google Groups > "v8-users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/groups/opt_out. -- -- v8-users mailing list [email protected] http://groups.google.com/group/v8-users --- You received this message because you are subscribed to the Google Groups "v8-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
