no nightly builds for windows
Once again there are no nighly builds for windows since almost a week, latest is MuseScoreNightly-2013-05-18-1909-cd7698d.7z
As per http://musescore.org/en/developers-handbook/references/development-infr… these should automatically build every hour, if there are new commits. They were plenty in these past days...
Comments
It should be solved. The build process was not sure which branch to merge. I added an IRC notification for successful build and so I should be able to know faster if the build process is stopped.
In reply to It should be solved. The by [DELETED] 5
Thanks.
So we now have MuseScoreNightly-2013-05-23-1104-a256907.7z
And possiby another problem: notification emails are not generated?
In reply to Thanks.So we now have by Jojo-Schmitz
I have no indication that the emails are not being sent. All signs here looks ok, but let me know later if you still feel like you don't receive emails. Let's also find out if others report the same. Thanks.
In reply to No indication by Thomas
Emails arrived just now, guess I was just too impatient ;-)
no nightly builds for Windows since MuseScoreNightly-2013-11-25-1322-d760826.7z
Mac and Linux got updates though
In reply to no nightly builds for Windows by Jojo-Schmitz
Still no new nightlies for Windows...
In reply to Still no new nightlies for by Jojo-Schmitz
Seems they are back now.
In reply to no nightly builds for Windows by Jojo-Schmitz
No nightly builds for Windows
Latest is MuseScoreNightly-2013-12-03-1009-63ee4cc.7z
In reply to No nightly builds for Windows by Jojo-Schmitz
fixed.
In reply to fixed. by [DELETED] 5
MuseScoreNightly-2013-12-10-1509-d01ef14.7z is incomplete, just 28MB vs. the 44MB of the previous versions and it crashes with an error reg. a missing windows plugin
Edit: fixed with the next nightly
No new nightly build for Windows since yesterday noon, regardless of several new commits
New Mac nightlies are available though
In reply to No new nightly build for by Jojo-Schmitz
Lasconic is currently out of office until the beginning of Feb, and currently we have no idea why the Windows build server is not working. The best strategy would be for someone to try to build MuseScore locally on Windows and report back.
In reply to No good idea yet by Thomas
Built successfully with Qt5.1.1, Win8.1 64bit, git 26777eb.
Installed Qt5.2.0, build failed with error cannot find "sndfile.h" but it exists in the same folder as it was in 5.1.1.
Latest nightly build using Qt 5.1.1 available from http://ist.uwaterloo.ca/~schepers/musescore
In reply to Built successfully with by schepers
I have no problem building with Qt 5.2.0 (yes, I finally got my own build environment set up! And now I know for sure that I need a new computer, the build took more than 2 hours!).
Did you put
include\sndfile.hintoC:\Qt\Tools\mingw48_32\i686-w64-mingw32\include, as the developers' handbook states?Oops, forget about it, I though I built with 5.2.0, but now see that it actually was 5.1.1. I'll try again later...
Also it seems nighly builds are back, I see MuseScoreNightly-2014-01-16-1923-d65c722.7z
In reply to I have no problem building by Jojo-Schmitz
I had numerous issues trying to build with 5.2.0. Most went away after multiple build attempts but it did have one consistent error at the end. When compiling mscore.exe I would get an error about "qt5v8", I don't remember the exact text.
EDIT: Installed Qt5.2.0 at home and built. The error is below. Indeed, I can't find "qt5v8.dll" in the Qt5.2.0 directory but it is in Qt5.1.0.
Linking CXX executable mscore.exe
d:/qt520/tools/mingw48_32/bin/../lib/gcc/i686-w64-mingw32/4.8.0/../../../../i686
-w64-mingw32/bin/ld.exe: cannot find -lQt5V8
collect2.exe: error: ld returned 1 exit status
mscore\CMakeFiles\mscore.dir\build.make:8241: recipe for target 'mscore/mscore.e
xe' failed
mingw32-make[3]: *** [mscore/mscore.exe] Error 1
mingw32-make[3]: Leaving directory 'D:/MSTRUNK/build.release'
CMakeFiles\Makefile2:264: recipe for target 'mscore/CMakeFiles/mscore.dir/all' f
ailed
mingw32-make[2]: *** [mscore/CMakeFiles/mscore.dir/all] Error 2
mingw32-make[2]: Leaving directory 'D:/MSTRUNK/build.release'
makefile:135: recipe for target 'all' failed
mingw32-make[1]: *** [all] Error 2
mingw32-make[1]: Leaving directory 'D:/MSTRUNK/build.release'
makefile.mingw:27: recipe for target 'release' failed
mingw32-make: *** [release] Error 2
In reply to I had numerous issues trying by schepers
Qt5V8 is mentioned in build/mingw32.mingw.cmake and mscore/CMakeLists.txt
The former also sets this:
set (CROSSQT C:/Qt/5.1.1/mingw48_32)
And both uses that setting later
In reply to Qt5V8 is mentioned in by Jojo-Schmitz
The dependency to Qt5V8 should be deleted in build/mingw32.mingw.cmake in order for the compilation with Qt5.2.0 to succeed.
See also:
http://dev-list.musescore.org/Qt-5-2-and-MuseScore-td7578529.html
Now precompiled header are disabled by default for Windows build (and that's why the compilation takes a really long time).
Moreover, the Qt5Positioning.dll seems to be needed during installation.
Therefore:
- in mscore/CMakeLists.txt the line ${CROSSQT}/bin/Qt5V8.dll should be deleted and replaced by ${CROSSQT}/bin/Qt5Positioning.dll
- in build/mingw32.mingw.cmake the line Qt5V8 should be deleted
- in build/mingw32.mingw.cmake the path to MinGW and Qt should be adjusted accordingly to the installation of Qt5.2.0 (i.e. the CROSS and CROSSQT variables).
And in principle, after these changes, the compilation and install should work.
Ciao,
ABL
In reply to Qt5V8 not needed for Qt 5.2.0 compilation by ABL
MAC and Linux builds are apparently using Qt 5.2, so no real reason for Windows not to switch to it too, I guess.
I'll try to have a go at it later (working on something else currently and my PC needs some 2 hours for a clean build :-( ), and if I get it to work would submit a PR.
Unless someone else wants to...
In reply to MAC and Linux are using Qt 5.2 by Jojo-Schmitz
I can confirm that with ABL's 3 listed changes, I can compile the latest MS nightly with Qt 5.2.0. It is available from http://ist.uwaterloo.ca/~schepers/musescore
In reply to I can confirm that with ABL's by schepers
As you have the needed changes ready and tested, could you submit a PR?
In reply to As you have the needed by Jojo-Schmitz
No, I'm not setup to do that. I can test things, but that's as far as I can go right now.
In reply to No, I'm not setup to do that. by schepers
{syntaxhighlighter brush:c}
diff --git a/build/mingw32.mingw.cmake b/build/mingw32.mingw.cmake
index 311bcb6..9f18073 100644
--- a/build/mingw32.mingw.cmake
+++ b/build/mingw32.mingw.cmake
@@ -5,7 +5,7 @@
set (CMAKE_SYSTEM_NAME "Windows")
set (CROSS C:/Qt/Tools/mingw48_32)
-set (CROSSQT C:/Qt/5.1.1/mingw48_32)
+set (CROSSQT C:/Qt/5.2.0/mingw48_32)
set (CMAKE_C_COMPILER ${CROSS}/bin/gcc.exe)
set (CMAKE_CXX_COMPILER ${CROSS}/bin/g++.exe)
@@ -47,7 +47,6 @@ set (QT_mingw_LIBRARIES
Qt5Network
Qt5WebKitWidgets
Qt5WebKit
- Qt5V8
Qt5XmlPatterns
Qt5PrintSupport
Qt5Quick
diff --git a/mscore/CMakeLists.txt b/mscore/CMakeLists.txt
index 1cf29d3..2c7c64d 100644
--- a/mscore/CMakeLists.txt
+++ b/mscore/CMakeLists.txt
@@ -393,7 +393,7 @@ if (MINGW)
${CROSSQT}/bin/Qt5Quick.dll
${CROSSQT}/bin/Qt5Script.dll
${CROSSQT}/bin/Qt5Sql.dll
- ${CROSSQT}/bin/Qt5V8.dll
+ ${CROSSQT}/bin/Qt5Positioning.dll
${CROSSQT}/bin/Qt5PrintSupport.dll
${CROSSQT}/bin/Qt5OpenGL.dll
${CROSSQT}/bin/Qt5Sensors.dll
{/syntaxhighlighter}
In reply to Something like this? by Jojo-Schmitz
I think it should be ok.
I can't directly make a pull directly from my Qt5.2.0 because I didn't setup properly the git folder for this "experimental" build (I just used the pull instruction from musescore/MuseScore).
If you want, I can start a new branch in the folder were I keep the "official" version (from where I make the pull request) and make a pull request, but probably not until tomorrow afternoon.
In reply to I think it should be ok by ABL
By then my attempt to build has probably succeeded and right after that I'd be ready for a PR ;-)
BTW; would it be possible to split off this part of the thread into a new one? Thomas?
In reply to By then my attempt to build by Jojo-Schmitz
Sorry Jojo, I have no easy interface to change the threading.
In reply to Sorry no interface by Thomas
OK, no worries. I just know this from other forums.
Update: the build with the above changes succeeded, PR: https://github.com/musescore/MuseScore/pull/650
In reply to No new nightly build for by Jojo-Schmitz
Seems nightly builds for windows don't get updated again.
In reply to Seems nightly builds for by Jojo-Schmitz
I believe Lasconic is away right now, and he maintains the servers. It should be fixed when he returns.
In reply to I believe Lasconic is away by schepers
Maybe a backup maintainer is needed?
In reply to Seems nightly builds for by Jojo-Schmitz
Possibly the server for the Windows nightly builds is lacking the now required Qt 5.2
In reply to Possibly the server for the by Jojo-Schmitz
My 32bits linux compilations are made with Qt 5.1
(the 64 bits with Qt 5.2)
In reply to just an information by robert leleu
dumb question: why not 5.2 for both?
In reply to dumb question: why not 5.2 by Jojo-Schmitz
that's just an info.
My 32 bits script is older than the 64, which I adjust to more recent system, which «came» with Qt5.2, (if I remember well Mint 16 (=ubuntu 13.10) had problems with Qt5.1). My 32bits is Ubuntu 14.04.
In reply to just an information by robert leleu
If anyone is desperate for a recent version I can make my self-compiled version of commit 77f7d29 available at FileFactory.
Be warned that it has a couple of non standard minor tweaks, such as a powder blue interface :)
Let me know :)
In reply to If anyone is desperate for a by ChurchOrganist
I'm very desperate :D
In reply to I am ;p by Gootector
If you can hold it just a couple of days more, salvation is nearby as lasconic is returning from holidays very soon.
In reply to I am ;p by Gootector
As I said above, my 64-bit Windows build is always available from http://ist.uwaterloo.ca/~schepers/musescore
In reply to As I said above, my 64-bit by schepers
But... I have installed Windows 8.1 32-bit... I have an installation DVD with Win8 64-bit - but my system partition has 20 GB... Win8 64-bit needs more than 20 gigs... and I have installed programs, files on this partition... ...I have a problem... :| Thanks for your good intentions, schepers.
In reply to But... by Gootector
Sorry, more misunderstanding. My Musescore build is 32-bit, my Windows is 64-bit. You're OK to download.
In reply to Sorry, more misunderstanding. by schepers
Wow! Nice splash screen. Thank You very much :D
In reply to Thank You by Gootector
No problem. The splash screen is the default for a home/custom build. The one provided on the Musescore site is a special one. I prefer the custom one.
In reply to No problem. The splash screen by schepers
Nightly builds for Windows are back and now use Qt 5.2.1. Enjoy!
In reply to Nightly builds for Windows by [DELETED] 5
Yeap... Qt - it's an one thing which I don't like in MuseScore. When Avid has introduced Qt to Sibelius (7), I said "goodbye, Siby". Now, prints from Sibelius look awful. Printed staves are terrible... It's named a negative progress :p
In reply to Yeap... Qt - it's an one by Gootector
I understand the feeling, but Qt has been instrumental in MuseScore development and grow. The printing of MuseScore is ok no? Qt is also the foundation of many other open source software from desktop environment (KDE) to creative suite (Krita). So, I have learn to like it :)
In reply to I understand the feeling, but by [DELETED] 5
In MuseScore printing is better than in Sibelius. But small staves are - in my opinion - barely legible. The lines are different thicknesses. Staves of large size are ok. In Sibelius each size of staff is awful. See here: http://www.forte-notensatz.de/ - Qt is ok, here is tragedy in displaying (everything)...
In the topic below is Gonville 2.2 beta. What do you think about that?