Thanks for this info! I had not checked this blog post but it sure will give me a lot of useful context to make a more educated decision.
Going over my intuition that I was doing something incorrectly, I tried fooling with LD_LIBRARY_PATH when manually launching v8_context_snapshot_generator exe so the dyn linker would pick-up the libs in debian_sid_i386-sysroot. But even within that sysroot itself, some of the .so's in there depend on a version of libdbus-1 which is not even in the sysroot! I will post on the main chromium-dev group about this I think... unless you guys believe this discussion belongs here? On Thursday, February 25, 2021 at 2:09:48 AM UTC-4 [email protected] wrote: > Depends on how large your initial heap state is / how expensive it is to > set up. +Yang Guo may have more details, and I guess you've seen > https://v8.dev/blog/custom-startup-snapshots. In any case, your build > issues sound solvable (it works with ninja after all), but with a custom > environment it may be difficult to get help. > > On Wed, Feb 24, 2021 at 4:15 PM Jean-François Dagenais < > [email protected]> wrote: > >> Thanks for your answers guys! So isn't there "major" performance >> drawbacks of not using pre-made snapshots ? Especially for an older arm cpu >> system? >> >> On Wednesday, February 24, 2021 at 2:47:44 AM UTC-4 Hitoshi Yoshida wrote: >> >>> cc->bcc: v8-dev@ >>> Hi, Jeff, >>> >>> I'm sorry, I'm not familiar with the non-standard infrastructures >>> ,either. >>> (To be honest, it is quite difficult to set up the build configuration >>> for v8_context_snapshot_generator in a cross-build environment.) >>> >>> If it works for you, I recommend to avoid using v8_context_snapshot, >>> with setting "use_v8_context_snapshot >>> <https://source.chromium.org/chromium/chromium/src/+/master:tools/v8_context_snapshot/v8_context_snapshot.gni>=false" >>> >>> in your gn.args. >>> Then the action is not invoked, and Chromium should run correctly. Now >>> on ChromeOS and Android, Chrome is built in this setting. >>> >>> >>> 2021年2月24日(水) 15:09 Jakob Gruber <[email protected]>: >>> >>>> >>>> >>>> On Tue, Feb 23, 2021 at 5:04 PM Jean-François Dagenais < >>>> [email protected]> wrote: >>>> >>>>> 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!? >>>>> >>>> >>>> You're on the wrong list, the v8_context_snapshot is part of chromium, >>>> not v8. In any case, I'm not sure anyone here will be able to help; we >>>> usually use the standard build tools and thus don't run into these kinds >>>> of >>>> issues. Fwiw, +Hitoshi Yoshida who implemented v8_context_snapshots. >>>> >>>> >>>>> >>>>> 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 >>>>> >>>>> <https://groups.google.com/d/msgid/v8-dev/0d39beec-b386-46e0-ae38-134a67b3a0e6n%40googlegroups.com?utm_medium=email&utm_source=footer> >>>>> . >>>>> >>>> >>> >>> -- >>> Hitoshi Yoshida (Peria) >>> email: [email protected] >>> >> -- >> -- >> 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/cb7965ed-3872-49b0-b6bc-3270db290406n%40googlegroups.com >> >> <https://groups.google.com/d/msgid/v8-dev/cb7965ed-3872-49b0-b6bc-3270db290406n%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> > -- -- 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/a1fab9ac-5d06-45c6-8756-0b12062711a9n%40googlegroups.com.
