Just tried this again in Win32 beta (5.7.492.44) it seems to work fine on a shared component build. However, when I add the static library flag it doesn't seem to output anything useful unfortunately. The DLL's are fine for now, I'm honestly just happy that I can get it building using GN with the latest versions.
On Wednesday, January 11, 2017 at 4:53:09 AM UTC-5, Hans Maier wrote: > > Ok, thanks for the Info. I will be using it as soon 5.7 becomes stable. > > Am Mittwoch, 11. Januar 2017 10:46:05 UTC+1 schrieb Jochen Eisinger: >> >> With the latest dev version of V8 (5.7), you should be able to get static >> libraries using the gn flag v8_static_library = true >> >> On Tue, Jan 10, 2017 at 4:26 PM Hans Maier <tbae...@gmail.com> wrote: >> >>> Hi, >>> >>> I had the same issue. I ended up creating the static libs from the >>> obj-files using the MSVC lib tool manually. >>> >>> Unsatisfactory, but it was working for me. >>> >>> Am Montag, 9. Januar 2017 15:55:40 UTC+1 schrieb Brendan Bates: >>>> >>>> Hello, >>>> >>>> I have seen this issue pop up a couple times on here and wondering what >>>> the current status is. I was spending the morning trying to get ahead of >>>> the game and switch from a Gyp build to a GN build. We are using MSVC >>>> 2015 >>>> to perform the build. I am successfully configuring and building using >>>> the >>>> following commands: >>>> >>>> > gn gen out/x86.debug --args="is_debug=true v8_use_snapshot=false >>>> target_cpu=\"x86\" disable_libfuzzer=true" >>>> Done. Made78 targets from 44 files in 1900ms >>>> >>>> > ninja-C out/x86.debug d8 >>>> ninja: Entering directory `out.gn/x86.debug' >>>> [49/886] LINK mkpeephole.exe mkpeephole.exe.pdb >>>> LINK : warning LNK4075: ignoring '/INCREMENTAL' due to '/OPT:ICF' >>>> specification >>>> [886/886] LINK d8.exe d8.exe.pdb >>>> LINK : warning LNK4075: ignoring '/INCREMENTAL' due to '/OPT:ICF' >>>> specification >>>> >>>> The build results are confusing, however. In the "out" directory, I >>>> find the v8.dll, along with the icu*.dll files. What seems to be missing >>>> are the static .lib files that were necessary in previous builds >>>> (v8_libbase.lib, v8_libplatform.lib and v8_nosnapshot.lib). My build with >>>> new new v8 DLL does not seem to work without these. So I attempted a >>>> static build, by adding the GN argument `is_component_build=false`. To my >>>> surprise, no static libraries were generated at all! Is this something >>>> that is planning on being supported in the future? If not, what is the >>>> way >>>> around this? I certainly don't want to transition my project to use GN. >>>> Thoughts? Thanks in advance. >>>> >>> -- >>> -- >>> 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.
