Hey Zac, I'm also trying to build on MinGW right now. I have successfully built on MSVC2015 but would much prefer MinGW (as all of our other products run under MinGW in Windows). I have had no luck thus far, have you been able to successfully build yet? I personally haven't got very far...
On Friday, April 15, 2016 at 12:42:40 AM UTC-4, Zac Hansen wrote: > > I'm trying to do this right now and having a helluva time trying to figure > this out. > > Can you post the steps you took to get this far? I ended up with very > large .a files on OS X (much larger than what you're seeing), but the > linked binaries files were only ~35-40MB. > > On Thursday, April 7, 2016 at 6:49:57 PM UTC-7, Caleb Champlin wrote: >> >> After more effort than I would have anticipated I finally got a new >> version of v8 (5.0) to build on mingw. I noticed however that v8lib_base.a >> is huge! Rougly 310MB. >> >> drwxr-xr-x 1 x x 4096 Apr 7 16:39 . >> drwxr-xr-x 1 x x 0 Apr 7 14:36 .. >> -rw-r--r-- 1 x x 322118626 Apr 7 16:19 libv8_base.a >> -rw-r--r-- 1 x x 252536 Apr 7 16:22 libv8_libbase.a >> -rw-r--r-- 1 x x 690768 Apr 7 16:22 libv8_libplatform.a >> -rw-r--r-- 1 x x 1033412 Apr 7 16:22 libv8_snapshot.a >> >> Here's how I built: >> >> GYPFLAGS="-Dv8_use_external_startup_data=0" CFLAGS=" -msse -msse2 -msse3" >> CXXFLAGS=" -std=c++11 -msse -msse2 -msse3" CFLAGS_host=" -msse -msse2 >> -msse3" CXXFLAGS_host=" -std=c++11 -msse -msse2 -msse3" make >> i18nsupport=off x64.release >> >> >> I built as release, and I'm basically wondering if it's normal for the >> file to be this large. I was able to successfully link a Go application >> against and everything with V8 seemed to work fine. >> >> >> Thanks. >> > -- -- v8-users mailing list [email protected] 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
