sorry for the long delay in answering. I don't know how to control the rpath, maybe asking on gn-...@chromium.org is an option?
On Mon, Nov 28, 2016 at 11:05 AM John Gardner <gardnerjo...@gmail.com> wrote: > Ah awesome, thanks! > > Similar question: is it possible to set the rpath at linking-time when > compiling a component build? It doesn't seem like ldflags can be modified > from a configuration-level. Perhaps I'm using the wrong approach... > > I need each dylib to be compiled with an absolute rpath (specifically, > /usr/local/opt). Currently, it's attempting to load shared libraries from > the executable's path, which doesn't work for the intended directory > arrangement: > > lib > lib/libv8.dylib > lib/libicuuc.dylib > lib/libicui18n.dylib > bin > bin/v8 > > > On Monday, 28 November 2016 20:51:45 UTC+11, Jochen Eisinger wrote: > > with https://codereview.chromium.org/2373783002/ it should be possible to > set v8_static_library to true to get static libraries > > On Sat, Nov 26, 2016 at 9:05 AM John Gardner <gardne...@gmail.com> wrote: > > A tracking issue <https://github.com/electron/electron/issues/7940> at > Electron's repository confirms that it's not possible to build static > libraries using GN: > > Under gn, there is no way to have v8 build as a standalone static library. > This is because v8 and other intermediate targets used to build chrome.exe > are source_set targets in chrome's gn files <https://goo.gl/VM4xOk>. > These are like virtual targets, and only object (.o) files are ever > generated for them. > > > A trick described here > <https://groups.google.com/forum/#!topic/v8-users/Y05xPj956Ys> involves > modifying *v8/gni/v8.gni* to force static library generation: > > template("v8_source_set") { > static_library(target_name) { > > Which results in these files being included in *out.gn/x64.release/obj/ > <http://out.gn/x64.release/obj/>* after building with Ninja: > > - > - libfuzzer_support.a > - libjson_fuzzer.a > - libparser_fuzzer.a > - libregexp_fuzzer.a > - libsimple_fuzzer.a > - libv8_base.a > - libv8_external_snapshot.a > - libv8_libbase.a > - libv8_libplatform.a > - libv8_libsampler.a > - libv8_nosnapshot.a > - libv8_snapshot.a > - libwasm_asmjs_fuzzer.a > - libwasm_fuzzer.a > > > > On Saturday, 26 November 2016 17:34:00 UTC+11, tbl...@icloud.com wrote: > > Actually, that's the wrong link. I've completely forgotten where I found > out that information. > > -- > -- > v8-users mailing list > > v8-u...@googlegroups.com > > > 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 v8-users+u...@googlegroups.com. > > > For more options, visit https://groups.google.com/d/optout. > > -- > -- > v8-users mailing list > v8-users@googlegroups.com > 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 v8-users+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- -- v8-users mailing list v8-users@googlegroups.com 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 v8-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.