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
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
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
"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
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
