Fix resolving .lib dependencies on windows.

[QAston]

This fixes building vibe.d dependent projects on windows with dmd 2.063.2

[s-ludwig]

Interesting, can you give a short sketch of the failing project's structure? (Just the project with a dependency to vibe.d?) I ask because Windows is my primary development platform and I didn't have issues so far. Handling of .libs needs to be fixed in any case though (e.g. proper handling of library search paths), I just want to make sure I understand what's happening.

[QAston]

{
    "name": "fancyprojname",
    "targetType": "library",
    "sourcePaths": ["protocol", "../util"],
    "dflags": ["-unittest"],
    "dependencies": {
        "vibe-d": {"version": "~master", "path": "../../vibe.d"}
    },
    "versions" : ["VibeCustomMain", "TraLaLa"],
}

fails with Error: Error reading file 'wsock32.lib' message

[QAston]

Ok, I've just noticed that dub does 2 stage build with dmd sometimes, in that case the fix won't work because it's dmd who solves -L-l flags, not optlink.

[QAston]

Odd, the problem has disappeared.

[s-ludwig]

Okay, so it fails when generating static libraries. I think that should be resolved by removing all -lib dependencies from the linker command line altogether. They are added on dependent projects anyway and usually shouldn't have an effect when "linked" against another .lib.

[s-ludwig]

Odd, the problem has disappeared.

I can still reproduce it BTW