Hi all!
Just so you can adapt your responses (:-) I am a total newb with chromium
and v8. Over the years I have become more of a systems enginee and have
never been a web developer.
I have spent the last few days getting a build of libcef/chromium working
on buildroot for an arm target (32 bits). FYI, I am not using depot_tools
but a tar.gz and implementing the gclient hooks manually, well in my
libcef.mk recipe file.
I am instructing chromium's build to use linux:unbundle with buildroot's
target sysroot for the target binaries. But in the spirit of reducing
dependencies towards the build host as well as buildroot, I have opted to
let chromium's build system use the the install-sysroot.py generated
sysroots for arm64 (build host) and i386 (v8 snapshots). This was just
somewhat blindly following the advice of the error message to invoke
install-sysroot --arch=arm64 and i386.
After having to tweak build/config/linux/pkg_config.gni to provide the
sysroot argument (-s) to pkg-config.py (?? I don't know how this can work
for anyone and why I had to do this.) After a long while, I finally got
binaries.
However, the v8_context_snapshot_generator I have, which should be able to
run on the build host, doesn't have rpaths to
chromium/build/linux/debian_sid_i386-sysroot/... so the
action("generate_v8_context_snapshot")
from tools/v8_context_snapshot/BUILD.gn fails because it's not finding
libraries. ldd shows it's looking at the host rootfs (/). I can hack things
with LD_LIBRARY_PATH, but again, I'm thinking: How does this even work for
anyone!?
Thanks for helping me understand what's wrong with my setup.
--
--
v8-dev mailing list
[email protected]
http://groups.google.com/group/v8-dev
---
You received this message because you are subscribed to the Google Groups
"v8-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/v8-dev/0d39beec-b386-46e0-ae38-134a67b3a0e6n%40googlegroups.com.
