Compilation of chrome on linux with sysroot

[Cezary Kulakowski]

Hello,

I try to set up minimal version of Debian which will be used to
compile chromium based browser. I believe sysroot fetched by gclient
contains all necessary headers and libraries required to compile
chrome, but I get linking errors like:

FAILED: v8_context_snapshot.bin
python ../../build/gn_run_binary.py ./v8_context_snapshot_generator
--output_file=v8_context_snapshot.bin
././v8_context_snapshot_generator: error while loading shared
libraries: libasound.so.2: cannot open shared object file: No such
file or directory
./v8_context_snapshot_generator failed with exit code 127

when I try to compile chrome. I can see that libasound is part of
sysroot and I am able to link chrome when I set LD_LIBRARY_PATH to
point to sysroot. Is it necessary to set it manually? Shouldn't it be
set by gn?

Best regards,
Czarek

[Mike Frysinger]

isn't the sysroot only for compiling/linking against ?  tools that run on the host need things installed on the host (such as the asound libs apparently).  they're orthogonal sets of files.

-mike

--
--
Chromium Developers mailing list: chromi...@chromium.org
View archives, change email options, or unsubscribe:
    http://groups.google.com/a/chromium.org/group/chromium-dev
---
You received this message because you are subscribed to the Google Groups "Chromium-dev" group.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-dev/CA%2B%3Dz4Qv7h8Ha64MQ2JZbsVadu18Q8Kg91%2BmZHqk5HNNMsj4ZSQ%40mail.gmail.com.

[Cezary Kulakowski]

Yes, I know, that's why I wrote I want to set up minimal version of

Debian which will be used to

compile chrome, not to run it.

> To unsubscribe from this group and stop receiving emails from it, send an
> email to chromium-dev...@chromium.org.

> To view this discussion on the web visit

> https://groups.google.com/a/chromium.org/d/msgid/chromium-dev/CAAbOSckzS9e39y-ab6PkNaFf%3DeOxenbuZ1N2pJxGkF07OYwH9Q%40mail.gmail.com.

[Mike Frysinger]

that's a chroot you run inside of, not a sysroot you build against externally.  the former is something you'd set up, and that's not what the sysroot gn arg does.

-mike