Cannot link DLL with static (non-import) library on Windows

[nmfisher]

When building a DLL on Windows, linking with a static .lib (i.e. not an import library) requires the library names to come immediately after the /link flag. There's no option in RunCBuilder that accommodates this. This isn't an issue on other platforms as we can pass everything via the flags argument (e.g. -lsomelib or -framework someframework), but that doesn't work with cl on Windows (or at least, I haven't found a way to do so; I have fairly limited experience with Windows command line tools).

Here's my current workaround:
nmfisher@7d9036b#diff-3be70b0004f01804719416f1e5931eaa8e2d618280bb0f9fa9bdaf2edc468964

This was just a quick hack which is why I'm not submitting as a PR, if you have any preference for the best way to address this, let me know and I'm happy to put one together.

[dcharkes]

Thanks for the report @nmfisher!

This helper lib is just in its infancy, so we welcome all contributions!

Maybe we should turn linkWith into -l for the other platforms. Yes it will be duplicate with flags, but we'll likely end up with duplicate ways to do something anyway (e.g. a separate frameworks option was suggested in #1228 as well).

Also, to make this into a PR:

• It should be also used in an executable?
• Can it be used in a static library?
• And it should be covered by a test that fails if the linkWith is not set.

[nmfisher]

Thanks @dcharkes. I'm a bit swamped at the moment but I'll try and put together a PR in the next week or two.