Closed katyo closed 4 years ago
Same errors still happened after #9. See Travis-CI log. Branch windows-ci.
To @kukuen Can you help to fix this issue?
It seems I fixed waf invocation by forcing python to be 3.x, but now I have linking issues: Travis CI log @kukuen What do you think about it?
Possibly it related to different static library name (aubio.lib instead of libaubio.a). But I dont sure. Also maybe WAF used MSVC to build aubio, but Rust target is mingw. Which WAF behavior in case of windows?
I'm fairly new to Rust, so I don't know if MSVC is usually more used than mingw or if it's the opposite, but I think checking both targets in the CI would be the best way the handle windows. I'll check what's happening with the mingw build.
I tried to force WAF use GCC with --check-c-compiler=gcc
(for GNU target env) but WAF ignores it and still use MSVC instead.
UPD: Oh, it seems I mistyped env name in checking (gcc instead of gnu).
UPD2: Yes, it works, but build still failed (nm
not found).
Linking failed (several undefined references)
log.
UPD: Only doc samples failed to link.
UPD2: It seems, I fixed using of 'aubio_lib' crate by code samples with old-style extern crate aubio_lib;
instead of use aubio_lib;
. Now It works fine.
Great ! I wasn't available lately, but let me know if you need more help on the windows side.
Currently windows builds disabled due to strange error:
Because that related to waf (and particularly python) I temporarly disable windows support. I tried to fix it using solutions from stackoverflow but nothing help me to do it. I'm not an expert in windows so I don't understand what happens wrong and how it can be fixed.