Hi,
Glad you manage to compile!
Regarding the packaging everything needed is in SVN, you just need to
uncomment the following in Makefile.mingw.
cd win32build & $(MAKE) package
Of course, NSIS have to be installed.
In my experience, Cmake does not generate NSIS script perfectly right.
So I need to run make once for compiling as in SVN, then comment
everything except this line. Correct a path for an image and run the
package step. The path is CPACK_PACKAGE_ICON and I had to change the /
to \. I tried to find if it's a cmake or a nsis bug but I couldn't
find reference.
Regarding the prerelease, I can make them more often. It's just that I
don't think it's good. I tend to wait until some crashes are solved or
until some issues I consider as critical are solved before doing a
prerelease. I try to make one every 20/30 commits and do it at the
beginning of the week. Doing it more often, testing users might be
overwhelmed by versions with not so many difference. But if several
people think we have to increase the number of prereleases, or even
doing it with a fix period, I can setup a nightly build or do it once
a week even if I don't think is good. Any opinion?
On other hand, even if compiling on windows is possible, I always
compile on Ubuntu and I try to do it with the same gcc version, qt
version etc... than Werner. I believe it's easier to track bugs due to
dependencies this way.
Last point, installer and uninstaller definatly need work, so it's
great if you know NSIS! I'm pretty sure association can be done, same
for removing MuseScore (Is it no removed??). Maybe I can help here as
well. Maybe we should fill issues in the issue tracker?
Lasconic
2009/4/12 David Bolton <
[hidden email]>
>
> Lasconic,
>
> Thank you for writing up these instructions. I was able to build r.1749
> successfully. The errors I got yesterday were because I skipped a step
> by accident (forgot to add one of the directories to the path).
>
> I am also interested in creating the install packages if possible. The
> first reason is it would be nice to offer the Windows prereleases more
> frequently (maybe once a week). I believe this might help catch any
> regressions more quickly. The second reason is I am interested in
> looking at ways to improve the installer such as adding support for the
> mscz and mscx file extensions, seeing if I can make the uninstaller
> fully removing MuseScore, etc.
>
> Do you have NSIS scripts that are needed to create the install package?
> Could you share the instructions for this step?
>
> Thanks,
>
> David
>
>
>
> Lasconic wrote:
> > It's a mispelling. Sorry... It's corrected.
> >
> > 2009/4/11 David Bolton <
[hidden email]
> > <mailto:
[hidden email]>>
> >
> > This evening I have been setting up my computer to build MuseScore.
> > The instructions (for Windows from SVN) suggest the following:
> >
> > mingw32make -f Makefile.mingw win32
> >
> > On my computer the command "mingw32make" was not recognized but the
> > command "mingw32-make" seemed to work (although I got some compilation
> > errors I'll sort through another day). Is this a mistake in the
> > instructions or does the name of the file vary from computer to
> > computer?
> >
> > --
> > David Bolton
> >
http://davidbolton.info/> >
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by:
> High Quality Requirements in a Collaborative Environment.
> Download a free trial of Rational Requirements Composer Now!
>
http://p.sf.net/sfu/www-ibm-com> _______________________________________________
> Mscore-developer mailing list
>
[hidden email]
>
https://lists.sourceforge.net/lists/listinfo/mscore-developer------------------------------------------------------------------------------
This SF.net email is sponsored by:
High Quality Requirements in a Collaborative Environment.
Download a free trial of Rational Requirements Composer Now!
http://p.sf.net/sfu/www-ibm-com_______________________________________________
Mscore-developer mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/mscore-developer
