Werner and I build several time daily from the command line. Werner on
Linux and I, on MacOSX.
Also for every commit on the 2.2 and master branch, Travis runs on the
command line on Ubuntu 14.04
https://travis-ci.org/musescore/MuseScore/jobs/265942105
So there is something very particular in your setting.
lasconic
2017-08-18 19:08 GMT+02:00 Tommaso Cucinotta <[email protected]>:
> On 18/08/2017 17:41, Ralf Mattes wrote:
>
>> Where did you get your sources from and how exactly did you try to build.
>>
>
> Hi,
>
> so I guess from answers to your post that the problem we're facing is that
> core devels build from some IDE, so the command-line is not used that often.
>
> Hmm - that allmost sounds like you did run cmake in the toplevel source
>> directory. This, as you
>> have seen doesn't work since cmake does (at least with the default
>> settings) create a Makefile
>> (after all, that's the whole purpose of cmake) which would overwrite the
>> checked-in Makefile.
>>
>
> sure, I tried also the standard cmake workflow (that you mention below):
>
> git clone
> cd build.mine
> cmake ..
> make
>
> but, unfortunately, the cmake ../ doesn't create any Makefile in the
> build.mine/, so the last step 'make' can't do much :(.
>
> However, I simply did what I did for any open-source software ever:
> 1) download sources or git clone
> 2) find some compile instructions in a README or COMPILE or similar
> 3) just follow them
>
> As the instructions you find the easiest and quickest in 2) are the ones
> at:
>
> https://musescore.org/en/developers-handbook/compilation/
> compile-instructions-linux-bsd-git
>
> those tell you very precisely to:
>
> 1) git clone ...
> 2) cd MuseScore
> 3) make revision
>
> I have a system-wide musescore, so I choose to follow up as:
> 4)make SUFFIX="-self" LABEL="Self Build"
> 5) sudo make SUFFIX="-self" LABEL="Self Build" install
>
> I guess that as soon as pchs do work you'll see an incredible speedup
>> during compilation ;-)
>>
>
> yeah, I have some bare memory of that pch stuff when I was using Vistual
> Studio back in another life..., don't know what's the status of pch with
> gcc et al., though.
>
> Alternatively, instructions from the README need the sources tarball, but
> they are along the lines of:
> 1) untar
> 2) cd untarred folder
> 3) make release
> 4) sudo make install
> optional
> 5) cd build
> 6) make doxy
>
> The instructions as reported above don't tell me to configure anything,
> nor where to change configuration if any (tweak build folders,
> configuration flags, debug vs non-debug version, optimization flags,
> whether to use pch or not, how to specify Qt version as we're used to have
> at least Qt4 and Qt5 around, whether to enable/disable optional features if
> any, etc....); they don't tell me to build out of the sources dir, rather
> these instructions tell me to 'make' from the root folder. Trying the
> standard cmake workflow simply fails.
>
> Guess there should be revised instructions about the command-line
> compilation workflow, I suspect the changes needed to the above steps are
> very minimal...
>
> Thanks,
>
> T.
> --
> Tommaso Cucinotta
> Home Page: http://retis.sssup.it/~tommaso
> LinkedIn: http://www.linkedin.com/in/tommasocucinotta
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Mscore-developer mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/mscore-developer
>
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Mscore-developer mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mscore-developer
