-
Notifications
You must be signed in to change notification settings - Fork 77
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
try enabling tests on Windows #122
Conversation
Well that didn't work. I still don't know what's going wrong with those link errors. |
Right :-/ I tried the same in a branch here earlier https://github.com/ahayzen-kdab/cxx-qt/commits/windows-exploration . I'll see if we can have someone with Windows knowledge spend some time trying to build the project locally and see if the cause can be found. |
Just a random thought: We're in some places defining GCC has been warning about this for a while, as C doesn't have references, and we'd technically have to use pointers. |
I don't see any compile warnings from GCC using GCC 11.2.1 locally on Fedora 35 nor on the Ubuntu CI. |
IIRC the warnings were actually from clang and hence why we used to have this warning disable cxx-qt/cxx-qt-gen/src/cxx_qt.cpp Line 42 in 3828f36
The Windows issues appear to be maybe linker related but it'll probably be more obvious on an actual machine than trying to fight CI, we just need to spend some time investigating what is missing/wrong. |
Can this be closed? |
We don't there are problems ...
|
We still need to figure out what to do about adding Qt to PATH to fix the DLL not found errors when running the tests... or figure out some hack around #224. |
However, the link errors with the tests have been fixed since overhauling the build system to compile the generated C++ with Cargo. The remaining issues are setting the required environment variables at runtime. |
@Be-ing this can be closed now as there are working Windows tests? 🎉 |
Yes superseded by #500 |
Maybe #105 fixed the link errors?