Cross compile wrong binary name and extension

[rracariu]

System information

• dub version: dub 1.8.1
• OS Platform and distribution: Linux
• compiler version : ldc 1.10.0

Bug Description

When cross-compiling from a Linux host to a Windows target the library name is following the host naming convention. For example, a library project foo when compiled will generate a library named libfoo.a. This is wrong, because if you use that project as a dependency then linking will fail as the linker will be using the library that has a wrong extension. The error in this case is:

Error: unrecognized file extension a

How to reproduce?

Make sure you have the VC and Platform libraries from a Visual Studio setup, then use

DFLAGS="-mtriple=x86_64-pc-windows-msvc -link-internally" dub --compiler=ldc2

Expected Behavior

A way to specify the target platform, similar to --arch, an option --platform, to force dub to use a specific platform. For example:

DFLAGS="-mtriple=x86_64-pc-windows-msvc -link-internally" dub --compiler=ldc2 --platform=windows

[gedaiu]

I think dub should know how to add the compiler flags if you just provide the platform argument. This feature will not work with dmd...

[kinke]

Resolved by #1755; the switch is --arch.