On 14/06/15 15:50, Thomas Martitz wrote:
Am 14.06.2015 um 14:48 schrieb Enrico Tröger:
On 14/06/15 14:21, Thomas Martitz wrote:
Why do you say self-compiled GTK? It is readily packaged for msys, I think we should be able to use that.
Oops, scratch the self-compiled. But we still need to create a distributable GTK runtime environment. This is probably doable from the installed GTK package, I guess.
Regards, Enrico
I'm experimenting at this moment. The gtk/glib/etc package files can be found under /var/cache/pacman/pkg/$pkg-$ver.tar.xz. They can be extracted with tar to a working directory. But what to do afterwards? The wiki says to move the files under $geanydir/gtk, but how is the installer file created? The nsis gui is giving me an error:
Now that you have the release.py (see below), you can easily see it is just:
makensis /V2 /DINCLUDE_GTK geany.nsi
Error in macro MUI_PAGEDECLARATION_LICENSE on macroline 17 Error in macro MUI_PAGE_LICENSE on macroline 6 Error in script "C:\msys64\home\kugel\geany.git\geany.nsi" on line 87
(geany.nsi:87 reads "!insertmacro MUI_PAGE_LICENSE "${RESOURCEDIR}\Copying.txt")
the Copying.txt is expected to be copied when installing Geany. 'waf install' does this. We cannot use a plain 'make install' on Windows as it is done on Linux, the Geany wscript has some logic, yes and magic, to do things different on Windows (like renaming AUTHORS, COPYING, README and so on to *.txt).
The wiki mentions release.py which I cannot find in geany git.
They are not meant to exist in the repository, at least so far. It seems I forgot to attach them to the wiki page, done now.
-> https://wiki.geany.org/howtos/win32/build#release_geany_and_geany-plugins
The scripts contain commands to digitally sign the binary files. These won't work on your system except you have my cerificate :). For testing, just comment this out. I still need to document the signcode.exe magic.
Regards, Enrico