Remove default import library inheritance/configuration.

Remove default import library inheritance/configuration.

BUG=176040
Committed: https://code.google.com/p/gyp/source/detail?r=1584

[Sigurður Ásgeirsson, 2013-02-13 19:08:11]

Please check this out - I'm still testing to see whether I need to roll deps to
this with the Chrome-side change to common.gypi.

[scottmg, 2013-02-13 19:26:36]

Won't this break gyptest-link-default-libs.py?

[Sigurður Ásgeirsson, 2013-02-14 21:58:42]

Hey Jean Luc, please take a look at the changes in msvs.py for sanity checking.
This accomplishes my ends in that default library inheritance is disabled across
the boards, and I now have tests failing equally across VS2008, VS2010 and
ninja.

Next step - if you guys don't object vehemently to the form or content here, is
to fix the tests...

[bradn, 2013-02-14 23:45:04]

lg aside from echoing jean-luc's concern about consistency.
The set of non-chromium gyp users is probably constrained enough that we can
safely do this.

[Sigurður Ásgeirsson, 2013-02-19 20:44:11]

Hey guys, please take another look.
I attempted to make this behave consistently across all of 
'AdditionalIncludeDirectories', 
'AdditionalLibraryDirectories'
'AdditionalOptions'
'DelayLoadDLLs'
'DisableSpecificWarnings'
'PreprocessorDefinitions'
but the fallout in the Chrome build configuration is more than I want to get
into, at least for now.
Notably, disabling inheritance of 'PreprocessorDefinitions' causes the projects
not to pick up ("_UNICODE", "UNICODE") or "_MBCS" from the projects
"CharacterSet" setting.

[scottmg, 2013-02-19 22:33:55]

lgtm for ninja

[Sigurður Ásgeirsson, 2013-02-20 13:35:00]

On 2013/02/19 22:33:55, scottmg wrote:
> lgtm for ninja

Thanks, jeanluc - can you please review the msvs changes? Also, how do I go
about landing this? Is one of you guys going to push it for me, or do I need to
be a committer?

[bradn, 2013-02-21 20:23:07]

My offhand reaction is that working out of the box is a ship that's somewhat
sailed already.

I think the right way to fix that is to factor out of build/common.gypi the
"standard" things that any project needs to make practical use of gyp and put
that in tools/gyp, referenced by an include.
Projects like nacl actually end up duplicating logic from common.gypi for their
standalone mode that really is project generic.
We do have a few downstream users, but they often have their own common.gypi's
so I suspect the fallout is likely to be limited. And we'd be better off
addressing this was some standard gypis in tools/gyp. As it stands the vcproj
you get out with no specification of configurations is pretty weird anyhow
(certainly doesn't look like the msvs default project).

LGTM assuming you:
- run some gyp try jobs before landing
- confirm you can roll this into chrome at least on windows cleanly

[Sigurður Ásgeirsson, 2013-02-25 22:29:39]

Committed patchset #4 manually as r1584.