The libraries themselves compile, but when I try to link against
libv8_base.a and libv8_snapshot.a, I get the following error:
ld: warning: ignoring file /Users/cowboyd/vendor/v8/out/x64.release/
libv8_base.a, file was built for archive which is not the architecture
being linked (x86_64)
ld: warning: ignoring file /Users/cowboyd/vendor/v8/out/x64.release/
libv8_snapshot.a, file was built for archive which is not the
architecture being linked (x86_64)
I see the commit detailed here https://chromiumcodereview.appspot.com/9808065 on master, but still can't actually get it to build. Any help greatly
appreciated, including pointers or where I should look to fix it
myself.
> The libraries themselves compile, but when I try to link against
> libv8_base.a and libv8_snapshot.a, I get the following error:
> ld: warning: ignoring file /Users/cowboyd/vendor/v8/out/x64.release/
> libv8_base.a, file was built for archive which is not the architecture
> being linked (x86_64)
> ld: warning: ignoring file /Users/cowboyd/vendor/v8/out/x64.release/
> libv8_snapshot.a, file was built for archive which is not the
> architecture being linked (x86_64)
> I see the commit detailed here
> https://chromiumcodereview.appspot.com/9808065 > on master, but still can't actually get it to build. Any help greatly
> appreciated, including pointers or where I should look to fix it
> myself.
> > The libraries themselves compile, but when I try to link against
> > libv8_base.a and libv8_snapshot.a, I get the following error:
> > ld: warning: ignoring file /Users/cowboyd/vendor/v8/out/x64.release/
> > libv8_base.a, file was built for archive which is not the architecture
> > being linked (x86_64)
> > ld: warning: ignoring file /Users/cowboyd/vendor/v8/out/x64.release/
> > libv8_snapshot.a, file was built for archive which is not the
> > architecture being linked (x86_64)
> > I see the commit detailed here
> >https://chromiumcodereview.appspot.com/9808065 > > on master, but still can't actually get it to build. Any help greatly
> > appreciated, including pointers or where I should look to fix it
> > myself.