On Tuesday, 7 January 2020 14:21:25 UTC, Jakob Gruber wrote: > > > > On Tue, Jan 7, 2020 at 3:13 PM Thomas Preston <[email protected] > <javascript:>> wrote: > >> On Tuesday, 7 January 2020 09:14:36 UTC, Jakob Gruber wrote: >>> >>> On Mon, Jan 6, 2020 at 6:30 PM Thomas Preston <[email protected]> >>> wrote: >>> >>>> Hi, >>>> We have noticed that the latest version of Chromium makes the v8 >>>> snapshot build mandatory. >>>> We were turning this off for building under Buildroot (for linux, >>>> targetting 32-bit ARM), because Buildroot has no concept of multilib, and >>>> host packages can't be installed with 32-bit memory architectures. >>>> Is there any way to continue to disable v8 snapshot building? If not, >>>> where can we find out more about building ARM 32-bit V8 snapshots on x64 >>>> hosts? >>>> >>> >>> Unfortunately there's currently no easy way to do this. A 64-bit >>> mksnapshot binary (currently) cannot create 32-bit snapshots. >>> >>> Your best bet is to build snapshot_blob.bin and embedded.S elsewhere >>> (e.g. on the host system or in a VM). The final build could then use these >>> generated files and skip the mksnapshot step. Would that be an option for >>> you? >>> >>> See also the Known Issues section here >>> <https://docs.google.com/document/d/1Irnq29OIGWMkcsXmazECZii95eIGQoyrYsmriHvpk-M/edit#heading=h.k26jzph28qte> >>> . >>> >>> >> That's useful, thanks. It looks like checking-in pre-built 32-bit >> artifacts is the way to go. >> >> Is it possible to just run mksnapshot? Maybe we can just tell ninja to >> build `obj/v8/v8_snapshot/embedded.o` >> > > Yes that's certainly possible. Try the run_mksnapshot target > <https://cs.chromium.org/chromium/src/v8/BUILD.gn?l=1253&rcl=73b25eab2d914aa2be8eb2d223eee7c1b93b45a0>. > > Make sure to use the same git hash and build config though between the > mksnapshot run and the final V8 build! >
Has anyone tried this? We are able to create a 32-bit snapshot_blob.bin and embedded.S, but we can't inject it into our 64-bit-host build because ninja wants to recreate the artifacts. I understand ninja uses timestamps to figure out which files are dirty, but I'm not sure which files specifically I need to touch to trick ninja into using my snapshot_blob.bin and embedded.S. I've tried touching the following combinations: - snapshot_blob.bin, gen/v8/embedded.S, obj/v8/run_mksnapshot_default.stamp - All dirty files output from `ninja -n -d explain -C out/Release run_mksnapshot_default` -- -- 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/v8-users/0f666e2e-7b25-4364-8dfe-ae4ceac2b160%40googlegroups.com.
