On Thursday, June 14, 2012 1:36:31 AM UTC-7, Jakob Kummerow wrote: > > > > On Thu, Jun 14, 2012 at 7:13 AM, Rohit <[email protected]> wrote: > >> I don't have experience building V8 using SCONS, but you might want to >> look at: >> http://code.google.com/p/v8/wiki/CrossCompilingForARM > > > Please do not rely on V8's SCons build. It will go away soon. The GYP/make > build is fully capable of cross-compiling for ARM, simply export > CC=/path/to/your/crosscompiler . > > You might also want to look at the "android.gypi" file which is used >> to build V8 for android targetting ARM [1]. > > > I don't think android.gypi contains anything useful for this case. It > really aims to bundle stuff that's specific to development/debugging on > *Android*, not general ARM definitions, and nothing that's required in > production (both the Android Browser and Chrome for Android use V8, but > neither requires android.gypi). ARM is fully supported by the regular gyp > files. > > >> V8 needs at least the >> standard C/C++ libarries, libm and libpthread. >> >> [1]: >> http://code.google.com/p/v8/source/search?q=android.gypi&origq=android.gypi&btnG=Search+Trunk >> >> On Jun 13, 9:21 pm, slide <[email protected]> wrote: >> > I am looking at embedding a JavaScript engine into an embedded >> application, >> > one that does not have an OS, but runs baremetal on an ARM chip. What I >> > would like to do is not worry about creating a static library to link >> > against or anything like that, but to just build the V8 files right >> along >> > with my baremetal code. >> > > Why are you trying to avoid using a *static* library? A static library is > basically just an archive containing the raw .o files created by the > compiler. It is "extracted" by the linker and the contents put into the > created executable. The end result is a binary that looks just like what > you're trying to get, it doesn't depend on anything at runtime (in > particular, not on the static library). > > Note that as Rohit pointed out, even a statically built V8 will still > require a few basic OS libraries. I assume that your toolchain has a way > around that. >
The main reason I am trying to avoid a static library is that I will have multiple targets (different variations of ARM cores v5, v6, v7, etc) that I will need to build for. I guess I could just have a static lib for each variant and that would avoid recompiling V8 every time. > > >> Has anyone done something like this? What might be >> > the best way to go about it? I really just need to get the source code >> > configured for the ARM target, and then get a file list of what I need >> to >> > compile into my application. Is there an easy way to do something like >> this? >> > > Look at tools/gyp/v8.gyp. It contains definitions of all sub-targets and > the files (or other build steps) they consist of. But as outlined above, I > don't see why you would need to go to all that trouble. > > > >> > Thanks in advance, >> > >> > slide >> > > > Thanks again for the help, I'll dig in and see what I can come up with. slide -- v8-users mailing list [email protected] http://groups.google.com/group/v8-users
