Well, the /MD flag didn't work, due to linker problems related to MS's broken declarations of exception types, when exceptions are turned off.
I found this discussion from chromium-dev: https://groups.google.com/a/chromium.org/forum/?fromgroups=#!topic/chromium-dev/wMzDP2jKsQQ M-A says that they use /MT linking for a reason, but there is no further details. I am curious, does anyone know the reason? I don't really want to mix MS runtimes in my app if I can help it, as I suspect at some point it'll break something unrelated. thanks, Paul On 11 December 2012 22:04, Paul Harris <[email protected]> wrote: > Hi, > > I had to hack common.gypi to switch from /MT to /MD, > To do this, I changed this: > ['OS=="win" and component=="shared_library"', { > 'RuntimeLibrary': '2', #/MD > }, { > 'RuntimeLibrary': '2', #/MT <-- was a different number > before > > That seemed to work (not fully tested yet with a full build). > > > I have looked around for reasons why v8 is linking against /MT, I think it > is simply because you assume if its a static build, it should also link > against the static runtime library. > From what I've read, this is wrong, and there should be an independent > option available for choosing the runtime library to use. > > Example, C++ Boost has an option like this in their bjam build system. > > > ... and I was unsuccessful at adding the /LTCG flag, > > I tried this: > 'VCLinkerTool': { > 'LinkTimeCodeGeneration': '1', # ADDED: link-time code > generation > 'LinkIncremental': '1', > 'OptimizeReferences': '2', > 'EnableCOMDATFolding': '2', > }, > > But that didn't seem to work for at least some of the projects. > > > Perhaps there can be some tweaks made to the gyp build system? > > cheers, > Paul > > -- v8-users mailing list [email protected] http://groups.google.com/group/v8-users
