Dub packages: Best practices for windows support

[Guillaume Piolat via Digitalmars-d-learn]

On Saturday, 30 January 2016 at 01:17:13 UTC, Mike Parker wrote:
> On Friday, 29 January 2016 at 19:46:40 UTC, Johannes Pfau wrote:
>
>> Now on windows, things are more complicated. First of all, I 
>> can't seem
>> to simply use "libs": ["foo"] as the linker won't find the C
>> import .lib file. Then apparently there's no way to add a 
>> library search
>> path with the MSVC linker? So I have to use the full path:
>> "libs": [$PACKAGE_DIR\\path\\foo]. Without $PACKAGE_DIR paths 
>> are
>> incorrect for applications using the library because of a dub 
>> problem.
>> And then I'll have to use different import libraries and paths 
>> for -m32,
>> -m64 and -m32mscoff.
>
> Now you know my motivation for creating Derelict.
>

+1, make a Derelict-style binding and never deal with import 
library ever again.