On Tue, 11 Feb 2014 20:27:07 GMT, Stephan Dilly wrote:
On Tue, 11 Feb 2014 19:22:41 GMT, Stephan Dilly wrote:
On Tue, 11 Feb 2014 17:45:30 GMT, Sönke Ludwig wrote:
On Tue, 11 Feb 2014 17:06:34 GMT, Stephan Dilly wrote:
Ok I just used the build.bat and got a dub.exe and copyd it over the exe of the 0.9.20 installation. using that the error with the mysql-native version is gone and a new error building mysql-native is there. it seems like the dmd cyclic bug again but wasn't that supposed to be work arounded by the new dub ? here is the output:
Building mysql-native configuration "library", build type debug. Running dmd... (...) FAIL C:\Users\DILLY\AppData\Roaming\dub\packages\mysql-native-master\.dub\build\library-debug-x86-dmd-59E6A9CD1869C6A35E0C61D4B0A344C4\ mysql-native staticLibrary Error executing command run: DMD compile run failed with exit code 1
Yeah, I got that, too, with DMD 2.064 - 2.065-b3 works fine, tough. What the latest DUB fixed was just that such error happen randomly, but unfortunately in this case the new fixed order seems to be wrong. #235 would probably offer an opportunity to work around this, but I'd like to keep that to the next release. The good news is that such errors will now hopefully not slip in as easy as they used to do anymore.
Wait, you got the error too but not when used with dmd 2.064 but with previous versions? I used 2.064 when I got that error ;( So there is no way for me to build the mysql-native lib currently and with the next dub release (0.9.21) ??
Ok I investigated a bit further and everything builds fine with dub 0.9.20 right now (just on windows, with those vibe.d beta tags) but the std.tratis template build errors appear on windows too as soon as i use the dub git HEAD...
That's probably due to 0.9.20 building everything at once. You could verify that by using dub build --combined
with git HEAD, which should work, too (it does work for me - nice, didn't think about that as a workaround).
is the plan now to keep it consistently failing on both systems with dmd 2.064 on linux and windows (with dub 0.9.21) ?
You could say so, yes. The plan is of course not to have it fail per se, but it's impossible to predict which order fixes it or breaks it. At least it should be consistent now, so that the package developer notices it immediately.