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

Switch Windows build to Qt-5.5.1 #2131

Closed
wants to merge 2 commits into from

Conversation

Jojo-Schmitz
Copy link
Contributor

as a follow up to fc8fad9.

Unfortunatly PCH still fails miserably, even with the (minor) compiler update that comes with Qt-5.5

@Jojo-Schmitz
Copy link
Contributor Author

Very strange, I'm 100% sure to have it compiled and running, opened a score, verified in "About Qt" that is really got built against Qt-5.5, but now it just crashes on startup with During startup program exited with code 0xc0000139, no idea why?

@Gootector
Copy link
Contributor

New Qt = a new problems with displaying, etc. (fonts) :P

@Jojo-Schmitz
Copy link
Contributor Author

Nope, my Gonville-vtest PR was done with Qt-5.4.2

@lasconic
Copy link
Contributor

Qt is not used to layout or draw musical glyphs anymore...

@Jojo-Schmitz
Copy link
Contributor Author

Which may explain the differences seen in that Gonville-vtest PR, the previous version had been done prior to the switch to freefont

@Jojo-Schmitz
Copy link
Contributor Author

I just tried again, but it still crashes on startup with During startup program exited with code 0xc0000139, no idea why? Various hints point at incompatible compiler versions and/or Qt DLLs, but I don't see how this applies here?

@ericfont
Copy link
Contributor

I got a similar startup message when I was first trying to build mscore in windows. Turns out that I didn't have all of the library directores in my %PATH%. I don't know if this helps you.

@Jojo-Schmitz
Copy link
Contributor Author

Hmm, I'm using similar settings to the 5.4 build, but of course adjusted to 5.5:
set QTDIR=C:\Qt\5.5\mingw492_32
set PATH=%QTDIR%\bin
set PATH=%PATH%;C:\Program Files (x86)\CMake\bin
set PATH=%PATH%;C:\Qt\Tools\mingw492_32\bin;C:\Qt\Tools\mingw492_32\lib
set PATH=%PATH%;C:\Qt\Tools\QtCreator\bin
set PATH=%PATH%;%SystemRoot%\System32

@ericfont
Copy link
Contributor

where is GnuWin32\bin? Where is is \Jack\lib?

(I actually had to include those, despite what the handbook said about the build process assuming they are in the default directories. Go ahead and add them to path and try make again...)

@Jojo-Schmitz
Copy link
Contributor Author

Not in PATH, and why should it? It isn't needed for Qt-5.4, resp. autodetected by the builds (cmake?), for freetype and jack

@ericfont
Copy link
Contributor

build doesn't need them. But execution does, I believe.

@Jojo-Schmitz
Copy link
Contributor Author

Certainly not when building for/with 5.4

@ericfont
Copy link
Contributor

maybe disregard what I'm saying...i might be off track.

@ericfont
Copy link
Contributor

Jojo, if you are using QT 5.5 on windows, I would appreciate if you respond to https://musescore.org/en/node/71731 to let me know if you are able to use any [Shift]+key commands (e.g. Shift+comma for crescendo). I want to determine if this is a QT 5.5 specific issue, or if it is some funny thing with my linux setup. No one responded to my post so I have no idea why I was running into that issue, and I don't want to try to setup QT 5.5 on windows now. I apologise if this is comment is not the appropriate place to alert your attention.

@Jojo-Schmitz
Copy link
Contributor Author

Eric, I can't get it to run at all, so can't really check, sorry

@briff
Copy link
Contributor

briff commented Oct 7, 2015

I managed to start 3 times, last time it did not crash. Problem was that it found qt creator dlls on path, so dll references got mixed up.

@Jojo-Schmitz Jojo-Schmitz changed the title Switch Windows build to Qt-5.5 Switch Windows build to Qt-5.5.1 Oct 16, 2015
@Jojo-Schmitz
Copy link
Contributor Author

Just upgraded to Qt-5.5.1, rebased the PR and adjusted slighly (QtPositioning.dll is available again, seems it was missing in 5.5). Seems to work fine

as a follow up to fc8fad9.

Unfortunatly PCH still fails miserably,
even with the (minor) compiler
update that comes with Qt-5.5
in DEBUG builds on Windows, due unhandled case QtInfoMsg
@lasconic
Copy link
Contributor

See #2476

@lasconic lasconic closed this Mar 23, 2016
@Jojo-Schmitz Jojo-Schmitz deleted the Qt-5.5 branch March 23, 2016 15:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants