Skip to content
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

Qt 5.12.2 #2889

Closed
IlyaFinkelshteyn opened this issue Mar 16, 2019 · 14 comments

Comments

Projects
None yet
5 participants
@IlyaFinkelshteyn
Copy link
Member

commented Mar 16, 2019

#2760 (comment)

Updating symlinks:

rd C:\Qt\latest
mklink /J C:\Qt\latest C:\qt\5.12.2

rd C:\Qt\5.12
mklink /J C:\Qt\5.12 C:\qt\5.12.2
@vadi2

This comment has been minimized.

Copy link

commented Mar 20, 2019

The 32bit binaries is a big deal - we'd love to have access to them asap.

@nschimme

This comment has been minimized.

Copy link

commented Apr 2, 2019

@IlyaFinkelshteyn Clearly 3/24 is not the deadline. Are we targeting a new date for updating the image? The reason I'm asking is because checking this issue every day, lol

@nschimme

This comment has been minimized.

Copy link

commented Apr 18, 2019

@IlyaFinkelshteyn 🎉 Thank you! 🎉 Works like a charm!

@pbek

This comment has been minimized.

Copy link

commented Apr 19, 2019

Anyone else getting this error when starting a binary built with 5.12.2 and mingw73_32?

https://github.com/pbek/QOwnNotes/blob/develop/appveyor.yml

@nschimme

This comment has been minimized.

Copy link

commented Apr 19, 2019

@pbek I haven't run into that with my build if you want to reference how I build my Qt app: https://github.com/MUME/MMapper/blob/master/.appveyor.yml

@pbek

This comment has been minimized.

Copy link

commented Apr 19, 2019

thanks a lot @nschimme, I'll take a look at your config!

@pbek

This comment has been minimized.

Copy link

commented Apr 22, 2019

I added some paths, that seems to have solved my issues. Thanks again, @nschimme!

@vadi2

This comment has been minimized.

Copy link

commented Apr 23, 2019

-lglut is no longer found with this version whereas it was with 5.11. Is the version of Qt hosted by Appveyor custom-compiled or is it the official one from Qt downloads?

@IlyaFinkelshteyn

This comment has been minimized.

Copy link
Member Author

commented Apr 23, 2019

@vadi2 yes, its official. Actually installation of Qt is the only installation we could not automate so far and we do it with "QT Maintenance Tool" manually :) Do you have -lglut with 5.12.2 on your dev box?

@vadi2

This comment has been minimized.

Copy link

commented Apr 25, 2019

No, and it turns out I don't need it! On my Windows dev box I took out -lglut and things compiled okay. Meanwhile doing the same AppVeyor generates so many errors that even the full log doesn't have the start of them! https://ci.appveyor.com/project/Mudlet/mudlet/builds/24031928

@IlyaFinkelshteyn

This comment has been minimized.

Copy link
Member Author

commented Apr 25, 2019

@vadi2 Can you open the build which was successful before QT update and press RE-BUILD COMMIT button?

@vadi2

This comment has been minimized.

Copy link

commented Apr 26, 2019

All other builds that still use Qt 5.11 (and link to -lglut) are successful: https://ci.appveyor.com/project/Mudlet/mudlet/history

So I've created a PR that still uses 5.11 but removes -lglut since that works OK for me locally, and that works on AppVeyor as well: https://ci.appveyor.com/project/Mudlet/mudlet/builds/24113246

So it's just the -lglut + 5.12 that bombs out on AppVeyor - which is strange and I'm not sure how to proceed.

@vadi2

This comment has been minimized.

Copy link

commented May 1, 2019

Aha, got it solved - we were mixing 64bit and 32bit (Mudlet/Mudlet@e196115). Nothing to do with AppVeyor!

@IlyaFinkelshteyn

This comment has been minimized.

Copy link
Member Author

commented May 1, 2019

Thanks a lot for the update because I was out of ideas :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.