Ok. I will create a 1.0.4 branch and a tarball and start creating the binaries.
On Jun 8, 2013 12:29 PM, "Richard Shann" <
address@hidden> wrote:
Jeremiah,
I think I have sorted out how to avoid creating links to Denemo's
lilypond on the desktop and start menu
In gub/nsis/denemo.nsi I commented out some lines as follows
in the start menu section I commented out these
;;CreateShortCut "$SMPROGRAMS\Denemo\LilyPond.lnk" \
;;"$INSTDIR\usr\bin\lilypond-windows.exe" "-dgui" \
;;"$INSTDIR\usr\bin\lilypond-windows.exe" 0 SW_SHOWMINIMIZED
;;CreateShortCut "$SMPROGRAMS\Denemo\LilyPond Website.lnk" \
;;"http://lilypond.org/" "" \
;;"firefox.exe" 0
;;CreateShortCut "$SMPROGRAMS\Denemo\Music in Mutopia.lnk" \
;;"http://www.mutopiaproject.org" "" \
;;"$INSTDIR\usr\bin\lilypond-windows.exe" 1
;;CreateShortCut "$SMPROGRAMS\Denemo\Examples.lnk" \
;;"$INSTDIR\usr\share\doc\lilypond\input" "" \
;;"$INSTDIR\usr\bin\lilypond-windows.exe" 1
and in the Desktop section I commented out these
;;CreateShortCut "$DESKTOP\LilyPond.lnk" \
;;"$INSTDIR\usr\bin\lilypond-windows.exe" "-dgui" \
;;"$INSTDIR\usr\bin\lilypond-windows.exe" 0 SW_SHOWMINIMIZED
and this seemed to work ok. I am not sure if the file association with
the .ly extension is affected (or indeed if we may need it inside
Denemo, though I think not).
I attach my denemo.nsi file. The only other change I have which you may
not have if you have not built for mingw recently is a bump to the
version of libtool
> --- a/gub/specs/libtool.py
> +++ b/gub/specs/libtool.py
> @@ -5,7 +5,7 @@ from gub import target
> from gub import tools
>
> class Libtool (target.AutoBuild):
> - source = 'http://ftp.gnu.org/pub/gnu/libtool/libtool-2.2.6a.tar.gz'
> + source = 'http://ftp.gnu.org/pub/gnu/libtool/libtool-2.2.6b.tar.gz'
>
>
Are you able to start the release process now?
Richard
_______________________________________________
Denemo-devel mailing list
address@hidden
https://lists.gnu.org/mailman/listinfo/denemo-devel