Re: [v8-users] Re: building v8 fails on bytecode-peephole-table.cc because libv8_libbase.dylib not found

If you build for x87, mips (big endian), ppc, or s390, use gyp, the rest is on gn. On Tue, Oct 18, 2016 at 11:04 PM Zac Hansen wrote: > How do I find out what the current supported build process is for a > platform? I've been told "if gn doesn't work, use gyp, because it's > supported until gn

Re: [v8-users] Re: building v8 fails on bytecode-peephole-table.cc because libv8_libbase.dylib not found

How do I find out what the current supported build process is for a platform? I've been told "if gn doesn't work, use gyp, because it's supported until gn works on a platform".. but when neither works, I don't know which to ask about how to use. Thank you for all your help. --Zac On Tue, Oct 1

Re: [v8-users] Re: building v8 fails on bytecode-peephole-table.cc because libv8_libbase.dylib not found

I tried to fix this here but concluded it's "not supported": https://codereview.chromium.org/22382003/ On Tue, Oct 18, 2016 at 9:33 AM Zac Hansen wrote: > "component build" = dylib? > > It's always worked fine - but this error is new. > > Linking against the static version takes forever, so dyli

Re: [v8-users] How to retain or reacquire v8::ScriptCompiler::Source object?

You'll need to keep a reference to the source yourself - either pass the string as an external string resource to v8 in the first place, or keep a persistent handle to the string. On Wed, Oct 12, 2016 at 10:38 AM Zac Hansen wrote: > the stringification of a function doesn't get me back the entir

Re: [v8-users] 18n support flags with gn build

I haven't tried this myself yet, but you should be able to use the system icu by following the steps outlined here: https://cs.chromium.org/chromium/src/build/linux/unbundle/README for icu. On Mon, Oct 17, 2016 at 7:25 PM Temuri Imnaishvili wrote: > Hi, > > There's this page: https://github.com/

[v8-users] Re: Enable Debug of V8 scripts and use a remote debugger.

Looking at the bug, less than 2 hours ago I see: [inspector] Turn on inspector by default Not sure if that means what I think it means, but maybe it's ready to go? On Tuesday, October 18, 2016 at 1:39:48 AM UTC-7, Zac Hansen wrote: > > bad news: there is currently no way to do this. > > good ne

[v8-users] Re: Enable Debug of V8 scripts and use a remote debugger.

bad news: there is currently no way to do this. good news: there is active work on it. >From a thread I was on a week ago or so: > The V8 inspector migration is almost complete--the majority of work has been done. You can follow development in the source

[v8-users] Enable Debug of V8 scripts and use a remote debugger.

I know this question has been somewhat answered before but I am scouting round for some more definitive pointer's on how to get this done. I currently Run many v8 isolate on many threads. Each thread runs its own set of scripts within a single isolate. I want to attach a debugger to one (or m

Re: [v8-users] Re: building v8 fails on bytecode-peephole-table.cc because libv8_libbase.dylib not found

"component build" = dylib? It's always worked fine - but this error is new. Linking against the static version takes forever, so dylibs are the only way to go. On Tue, Oct 18, 2016 at 12:31 AM, Jochen Eisinger wrote: > I'm surprised that the component build with gyp on mac ever worked for > yo

Re: [v8-users] Re: building v8 fails on bytecode-peephole-table.cc because libv8_libbase.dylib not found

I'm surprised that the component build with gyp on mac ever worked for you, it never did for me :-/ On Tue, Oct 18, 2016 at 5:32 AM Zac Hansen wrote: > manually copying the file into /usr/local/lib works. Someone said it > might have to do with the "install_name" being /usr/local/lib, but I do