RejectedSoftware Forums

Sign up

2.063.2 vs 2.064 package import compatibility issue

I want my library to work with both versions of these compilers, so I'm distributing both a classic-style "mypackage.all" module and the new package module-style "package.d" file. However dub will not work if it finds a "package.d" file and uses an older compiler, it seems to automatically include it in the build process.

Can we add an exclude file in the package configuration but only if a specific version of a compiler is being ran?

Re: 2.063.2 vs 2.064 package import compatibility issue

On Sun, 03 Nov 2013 19:25:32 GMT, Andrej Mitrovic wrote:

I want my library to work with both versions of these compilers, so I'm distributing both a classic-style "mypackage.all" module and the new package module-style "package.d" file. However dub will not work if it finds a "package.d" file and uses an older compiler, it seems to automatically include it in the build process.

Can we add an exclude file in the package configuration but only if a specific version of a compiler is being ran?

Ok, I've found a temporary fix, I'm using:

"excludedSourceFiles": ["src/dchip/package.d"],

I still wish I could do that with only specific versions of the compiler.

OT: Actually I wish even more that we've implemented package imports in a backward-compatible way.