Hi,
I've built new Windows installers from current GIT master.
Downloads can be found here: http://download.geany.org/snapshots/
Please note that these are test builds from the current development version, don't expect release quality. You have been warned :).
After you installed the snapshots, you can also use the nightly builds again on Windows (i.e. copy the archive contents over the installation).
Any feedback is welcome.
Regards, Enrico
On Sat, Jun 27, 2015 at 1:09 AM, Enrico Tröger enrico.troeger@uvena.de wrote:
Hi,
I've built new Windows installers from current GIT master.
Downloads can be found here: http://download.geany.org/snapshots/
Please note that these are test builds from the current development version, don't expect release quality. You have been warned :).
After you installed the snapshots, you can also use the nightly builds again on Windows (i.e. copy the archive contents over the installation).
Any feedback is welcome.
Hi Enrico,
seems to be working fine here.
One idea: wouldn't it be good to package the grep binary to the installer (and if possible somehow set the preferences to the location where it was installed) so find in files works out of the box? Right now the message you get when trying to use find in files is:
search_find_in_files: spawn_with_callbacks() failed: CreateProcess() failed: The system cannot find the file specified.
which isn't the most user-friendly message and I guess many people will interpret it as "find in files doesn't work on Windows".
Cheers,
Jiri
Hi Jiří,
I've built new Windows installers from current GIT master.
[..]
Any feedback is welcome.
Hi Enrico,
seems to be working fine here.
One idea: wouldn't it be good to package the grep binary to the installer (and if possible somehow set the preferences to the location where it was installed) so find in files works out of the box? Right now the message you get when trying to use find in files is:
great idea! Will be included in the next installer, it's just 79kB. Luckily, and if I don't miss anything, we don't need to set any paths because the default path for grep is just "grep" and when grep.exe is in the bin/ directory next to Geany.exe, it should work out of the box.
search_find_in_files: spawn_with_callbacks() failed: CreateProcess() failed: The system cannot find the file specified.
which isn't the most user-friendly message and I guess many people will interpret it as "find in files doesn't work on Windows".
True. I guess we can improve the error message but maybe better after 1.25 to not bother the translators too much by breaking the string freeze :).
Regards, Enrico
On Sun, Jun 28, 2015 at 11:53 AM, Enrico Tröger enrico.troeger@uvena.de wrote:
Hi Jiří,
I've built new Windows installers from current GIT master.
[..]
Any feedback is welcome.
Hi Enrico,
seems to be working fine here.
One idea: wouldn't it be good to package the grep binary to the installer (and if possible somehow set the preferences to the location where it was installed) so find in files works out of the box? Right now the message
you
get when trying to use find in files is:
great idea! Will be included in the next installer, it's just 79kB. Luckily, and if I don't miss anything, we don't need to set any paths because the default path for grep is just "grep" and when grep.exe is in the bin/ directory next to Geany.exe, it should work out of the box.
Just tried the latest installer and works great, thanks! Cool it wasn't necessary to modify the config file when installing.
search_find_in_files: spawn_with_callbacks() failed: CreateProcess() failed: The system cannot find the file specified.
which isn't the most user-friendly message and I guess many people will interpret it as "find in files doesn't work on Windows".
True. I guess we can improve the error message but maybe better after 1.25 to not bother the translators too much by breaking the string freeze :).
I have just created a bug report here
https://github.com/geany/geany/issues/541
It can wait for the next release especially as grep works now.
Cheers,
Jiri
On Sat, Jun 27, 2015 at 1:09 AM, Enrico Tröger enrico.troeger@uvena.de wrote:
Hi,
I've built new Windows installers from current GIT master.
Downloads can be found here: http://download.geany.org/snapshots/
Please note that these are test builds from the current development version, don't expect release quality. You have been warned :).
After you installed the snapshots, you can also use the nightly builds again on Windows (i.e. copy the archive contents over the installation).
Any feedback is welcome.
One more minor thing I have noticed is there are some themes included in the installer but some from geany-themes are missing so you might want to update them.
Cheers,
Jiri
On 27/06/15 12:01, Jiří Techet wrote:
On Sat, Jun 27, 2015 at 1:09 AM, Enrico Tröger enrico.troeger@uvena.de wrote:
Hi,
I've built new Windows installers from current GIT master.
Downloads can be found here: http://download.geany.org/snapshots/
Please note that these are test builds from the current development version, don't expect release quality. You have been warned :).
After you installed the snapshots, you can also use the nightly builds again on Windows (i.e. copy the archive contents over the installation).
Any feedback is welcome.
One more minor thing I have noticed is there are some themes included in the installer but some from geany-themes are missing so you might want to update them.
Oops, I completely forgot about this. Themes are updated on my build machine (this is as easy as 'git pull' :D) and I added the command to the release script to not forget it again :).
Thanks.
Regards, Enrico
Am 27.06.2015 um 01:09 schrieb Enrico Tröger:
Hi,
I've built new Windows installers from current GIT master.
Downloads can be found here: http://download.geany.org/snapshots/
Please note that these are test builds from the current development version, don't expect release quality. You have been warned :).
After you installed the snapshots, you can also use the nightly builds again on Windows (i.e. copy the archive contents over the installation).
Any feedback is welcome.
Nice! I'll try to spin GTK3-based installers soon. Though it needs tiny patches to Geany (PR will follow).
Best regards
On 27/06/15 20:53, Thomas Martitz wrote:
Am 27.06.2015 um 01:09 schrieb Enrico Tröger:
Hi,
I've built new Windows installers from current GIT master.
Downloads can be found here: http://download.geany.org/snapshots/
Please note that these are test builds from the current development version, don't expect release quality. You have been warned :).
After you installed the snapshots, you can also use the nightly builds again on Windows (i.e. copy the archive contents over the installation).
Any feedback is welcome.
Nice! I'll try to spin GTK3-based installers soon. Though it needs tiny patches to Geany (PR will follow).
Nice too!
Since this may affect your work too: after Jiří's feedback, I made two changes to the Windows installer:
- include grep.exe - update geany-themes repo in release.py
I added a note about including grep.exe on https://wiki.geany.org/howtos/win32/build#create_a_stripped_down_gtk_runtime.... It'd be cool if you could do something similar in your scripts (grep.exe doesn't need to be in the GTK runtime directory, as long as will result in the Geany bin installation directory at the end).
And I updated the Geany release.py linked in the Wiki with a 'git pull' command in the geany-themes repository.
Regards, Enrico
Am 28.06.2015 um 12:36 schrieb Enrico Tröger:
On 27/06/15 20:53, Thomas Martitz wrote:
Am 27.06.2015 um 01:09 schrieb Enrico Tröger:
Hi,
I've built new Windows installers from current GIT master.
Downloads can be found here: http://download.geany.org/snapshots/
Please note that these are test builds from the current development version, don't expect release quality. You have been warned :).
After you installed the snapshots, you can also use the nightly builds again on Windows (i.e. copy the archive contents over the installation).
Any feedback is welcome.
Nice! I'll try to spin GTK3-based installers soon. Though it needs tiny patches to Geany (PR will follow).
Nice too!
Not sure I'll bother anymore. To me it doesn't look like there is any interest in a GTK3-based windows version seeing how immediately my bug fixes got post-poned. I also feel uneasy with myself releasing a GTK3-1.25 which is actually a 1.25+ because it has patches applied (because my bug fixes aren't accepted in time, and plain git master isn't up to it)
Best regards.
On 28/06/15 15:09, Thomas Martitz wrote:
Am 28.06.2015 um 12:36 schrieb Enrico Tröger:
On 27/06/15 20:53, Thomas Martitz wrote:
Am 27.06.2015 um 01:09 schrieb Enrico Tröger:
Hi,
I've built new Windows installers from current GIT master.
Downloads can be found here: http://download.geany.org/snapshots/
Please note that these are test builds from the current development version, don't expect release quality. You have been warned :).
After you installed the snapshots, you can also use the nightly builds again on Windows (i.e. copy the archive contents over the installation).
Any feedback is welcome.
Nice! I'll try to spin GTK3-based installers soon. Though it needs tiny patches to Geany (PR will follow).
Nice too!
Not sure I'll bother anymore. To me it doesn't look like there is any interest in a GTK3-based windows version seeing how immediately my bug fixes got post-poned. I also feel uneasy with myself releasing a GTK3-1.25 which is actually a 1.25+ because it has patches applied (because my bug fixes aren't accepted in time, and plain git master isn't up to it)
As said in PR #539, the 'immediate post-poning' was not because of lacking interest in GTK3-based Windows version but rather being a bit anxious with changing Windows-stuff before a release. But that's my personal problem not having the balls on Windows changes :).
Regards, Enrico
[...]
Not sure I'll bother anymore. To me it doesn't look like there is any interest in a GTK3-based windows version seeing how immediately my bug fixes got post-poned. I also feel uneasy with myself releasing a GTK3-1.25 which is actually a 1.25+ because it has patches applied (because my bug fixes aren't accepted in time, and plain git master isn't up to it)
As said in PR #539, the 'immediate post-poning' was not because of lacking interest in GTK3-based Windows version but rather being a bit anxious with changing Windows-stuff before a release. But that's my personal problem not having the balls on Windows changes :).
Its more the intelligence to learn from past mistakes :)
Cheers Lex
Regards, Enrico
-- Get my GPG key from http://www.uvena.de/pub.asc
Devel mailing list Devel@lists.geany.org https://lists.geany.org/cgi-bin/mailman/listinfo/devel
On 27/06/15 20:53, Thomas Martitz wrote:
Am 27.06.2015 um 01:09 schrieb Enrico Tröger:
Hi,
I've built new Windows installers from current GIT master.
Downloads can be found here: http://download.geany.org/snapshots/
Please note that these are test builds from the current development version, don't expect release quality. You have been warned :).
After you installed the snapshots, you can also use the nightly builds again on Windows (i.e. copy the archive contents over the installation).
Any feedback is welcome.
Nice! I'll try to spin GTK3-based installers soon. Though it needs tiny patches to Geany (PR will follow).
Thomas, could you do me a favor and check against which libraries your geany.dll is linked? Basically performing a 'ldd' on Windows.
Attached is a short command session to dump object information from the DLL and then grep for "DLL Name" which lists linked libraries. This is somewhat similar to 'ldd' on Linux. You probably need to adjust the paths to the 'objdump' tool and the geany.dll (objdump.exe should be part of the Mingw installation and reside next to gcc.exe).
Background: Frank made me aware that on a clean Windows system, the provided installer won't start because it requires libwinpthread-1.dll which is not distributed by the installer but is part of the Mingw environment. I never noticed this because on my Windows system, the Mingw installation is in $PATH and so this library is always available.
I'm curious whether this happens also with your Mingw setup. I guess it will as it seems this is a change in newer gcc versions on Windows. But I want to get sure instead of just guessing :).
Right now, I'm playing with static linking options, already tried -static -lpthread but so far without success.
If it is just a requirement, we can probably distribute this library as well but if we can avoid it, even better.
Regards, Enrico
Am 01.07.2015 um 21:33 schrieb Enrico Tröger:
On 27/06/15 20:53, Thomas Martitz wrote:
Am 27.06.2015 um 01:09 schrieb Enrico Tröger:
Hi,
I've built new Windows installers from current GIT master.
Downloads can be found here: http://download.geany.org/snapshots/
Please note that these are test builds from the current development version, don't expect release quality. You have been warned :).
After you installed the snapshots, you can also use the nightly builds again on Windows (i.e. copy the archive contents over the installation).
Any feedback is welcome.
Nice! I'll try to spin GTK3-based installers soon. Though it needs tiny patches to Geany (PR will follow).
Thomas, could you do me a favor and check against which libraries your geany.dll is linked? Basically performing a 'ldd' on Windows.
I use EXE Explorer[1] to inspect imports. Actually, I vaguely remember problems with libwinpthread-1.dll during the linkage cleanup effort (I did stumble upon it). But I don't remember the outcome. I do know I didn't use msys2 back then but mingw32. Nevertheless neither geany.exe nor libgeany-0.dll built by msys2 import this library (it exists in the msys2 file system though) so this binaries don't suffer.
Perhaps a bug in the toolchain.
The gcc version is 4.9.2, binutils is 2.25.
Best regards
On 01/07/15 23:01, Thomas Martitz wrote:
Am 01.07.2015 um 21:33 schrieb Enrico Tröger:
On 27/06/15 20:53, Thomas Martitz wrote:
Am 27.06.2015 um 01:09 schrieb Enrico Tröger:
Hi,
I've built new Windows installers from current GIT master.
Downloads can be found here: http://download.geany.org/snapshots/
Please note that these are test builds from the current development version, don't expect release quality. You have been warned :).
After you installed the snapshots, you can also use the nightly builds again on Windows (i.e. copy the archive contents over the installation).
Any feedback is welcome.
Nice! I'll try to spin GTK3-based installers soon. Though it needs tiny patches to Geany (PR will follow).
Thomas, could you do me a favor and check against which libraries your geany.dll is linked? Basically performing a 'ldd' on Windows.
I use EXE Explorer[1] to inspect imports. Actually, I vaguely remember problems with libwinpthread-1.dll during the linkage cleanup effort (I did stumble upon it). But I don't remember the outcome. I do know I didn't use msys2 back then but mingw32. Nevertheless neither geany.exe nor libgeany-0.dll built by msys2 import this library (it exists in the msys2 file system though) so this binaries don't suffer.
Perhaps a bug in the toolchain.
The gcc version is 4.9.2, binutils is 2.25.
Thanks. I upgraded my Mingw environment so it is now also gcc 4.9.2 on my system, but still got the linkage to libwinpthread-1.dll.
In case I won't find a solution in the next days, I guess I will just include it in the 1.25 installer. If it doesn't happen with MSYS2, it's all fine for the future, I guess.
Regards, Enrico
On 2015-07-01 12:33 PM, Enrico Tröger wrote:
On 27/06/15 20:53, Thomas Martitz wrote:
Am 27.06.2015 um 01:09 schrieb Enrico Tröger:
Hi,
I've built new Windows installers from current GIT master.
Downloads can be found here: http://download.geany.org/snapshots/
Please note that these are test builds from the current development version, don't expect release quality. You have been warned :).
After you installed the snapshots, you can also use the nightly builds again on Windows (i.e. copy the archive contents over the installation).
Any feedback is welcome.
Nice! I'll try to spin GTK3-based installers soon. Though it needs tiny patches to Geany (PR will follow).
Thomas, could you do me a favor and check against which libraries your geany.dll is linked? Basically performing a 'ldd' on Windows.
Attached is a short command session to dump object information from the DLL and then grep for "DLL Name" which lists linked libraries. This is somewhat similar to 'ldd' on Linux. You probably need to adjust the paths to the 'objdump' tool and the geany.dll (objdump.exe should be part of the Mingw installation and reside next to gcc.exe).
Background: Frank made me aware that on a clean Windows system, the provided installer won't start because it requires libwinpthread-1.dll which is not distributed by the installer but is part of the Mingw environment. I never noticed this because on my Windows system, the Mingw installation is in $PATH and so this library is always available.
I'm curious whether this happens also with your Mingw setup. I guess it will as it seems this is a change in newer gcc versions on Windows. But I want to get sure instead of just guessing :).
Right now, I'm playing with static linking options, already tried -static -lpthread but so far without success.
If it is just a requirement, we can probably distribute this library as well but if we can avoid it, even better.
For cross-compiling it's sometimes useful to add `-static-libstdc++` and `-static-libgcc` compiler/linker options, if not already there. Maybe they would compile that library into Geany.exe statically along with the std stuff.
Cheers, Matthew Brush
On 2015-07-01 02:45 PM, Matthew Brush wrote:
On 2015-07-01 12:33 PM, Enrico Tröger wrote:
On 27/06/15 20:53, Thomas Martitz wrote:
Am 27.06.2015 um 01:09 schrieb Enrico Tröger:
Hi,
I've built new Windows installers from current GIT master.
Downloads can be found here: http://download.geany.org/snapshots/
Please note that these are test builds from the current development version, don't expect release quality. You have been warned :).
After you installed the snapshots, you can also use the nightly builds again on Windows (i.e. copy the archive contents over the installation).
Any feedback is welcome.
Nice! I'll try to spin GTK3-based installers soon. Though it needs tiny patches to Geany (PR will follow).
Thomas, could you do me a favor and check against which libraries your geany.dll is linked? Basically performing a 'ldd' on Windows.
Attached is a short command session to dump object information from the DLL and then grep for "DLL Name" which lists linked libraries. This is somewhat similar to 'ldd' on Linux. You probably need to adjust the paths to the 'objdump' tool and the geany.dll (objdump.exe should be part of the Mingw installation and reside next to gcc.exe).
Background: Frank made me aware that on a clean Windows system, the provided installer won't start because it requires libwinpthread-1.dll which is not distributed by the installer but is part of the Mingw environment. I never noticed this because on my Windows system, the Mingw installation is in $PATH and so this library is always available.
I'm curious whether this happens also with your Mingw setup. I guess it will as it seems this is a change in newer gcc versions on Windows. But I want to get sure instead of just guessing :).
Right now, I'm playing with static linking options, already tried -static -lpthread but so far without success.
If it is just a requirement, we can probably distribute this library as well but if we can avoid it, even better.
For cross-compiling it's sometimes useful to add `-static-libstdc++` and `-static-libgcc` compiler/linker options, if not already there. Maybe they would compile that library into Geany.exe statically along with the std stuff.
Another alternative might be `-static -lwinpthread-1` with or without the `-1`.
Cheers, Matthew Brush
On 02/07/15 01:17, Matthew Brush wrote:
On 2015-07-01 02:45 PM, Matthew Brush wrote:
On 2015-07-01 12:33 PM, Enrico Tröger wrote:
On 27/06/15 20:53, Thomas Martitz wrote:
Am 27.06.2015 um 01:09 schrieb Enrico Tröger:
Hi,
I've built new Windows installers from current GIT master.
Downloads can be found here: http://download.geany.org/snapshots/
Please note that these are test builds from the current development version, don't expect release quality. You have been warned :).
After you installed the snapshots, you can also use the nightly builds again on Windows (i.e. copy the archive contents over the installation).
Any feedback is welcome.
Nice! I'll try to spin GTK3-based installers soon. Though it needs tiny patches to Geany (PR will follow).
Thomas, could you do me a favor and check against which libraries your geany.dll is linked? Basically performing a 'ldd' on Windows.
Attached is a short command session to dump object information from the DLL and then grep for "DLL Name" which lists linked libraries. This is somewhat similar to 'ldd' on Linux. You probably need to adjust the paths to the 'objdump' tool and the geany.dll (objdump.exe should be part of the Mingw installation and reside next to gcc.exe).
Background: Frank made me aware that on a clean Windows system, the provided installer won't start because it requires libwinpthread-1.dll which is not distributed by the installer but is part of the Mingw environment. I never noticed this because on my Windows system, the Mingw installation is in $PATH and so this library is always available.
I'm curious whether this happens also with your Mingw setup. I guess it will as it seems this is a change in newer gcc versions on Windows. But I want to get sure instead of just guessing :).
Right now, I'm playing with static linking options, already tried -static -lpthread but so far without success.
If it is just a requirement, we can probably distribute this library as well but if we can avoid it, even better.
For cross-compiling it's sometimes useful to add `-static-libstdc++` and `-static-libgcc` compiler/linker options, if not already there. Maybe they would compile that library into Geany.exe statically along with the std stuff.
Those are already used (https://github.com/geany/geany/blob/master/wscript#L271).
Another alternative might be `-static -lwinpthread-1` with or without the `-1`.
Thanks. I already tried static -lpthread and now also your variants but all without success :(. The geany.dll on my system is always linked against libwinpthread-1.dll, even after updating my Mingw environment.
I'll keep testing and trying...
Regards, Enrico
On 2015-07-02 01:36 PM, Enrico Tröger wrote:
On 02/07/15 01:17, Matthew Brush wrote:
On 2015-07-01 02:45 PM, Matthew Brush wrote:
On 2015-07-01 12:33 PM, Enrico Tröger wrote:
On 27/06/15 20:53, Thomas Martitz wrote:
Am 27.06.2015 um 01:09 schrieb Enrico Tröger:
Hi,
I've built new Windows installers from current GIT master.
Downloads can be found here: http://download.geany.org/snapshots/
Please note that these are test builds from the current development version, don't expect release quality. You have been warned :).
After you installed the snapshots, you can also use the nightly builds again on Windows (i.e. copy the archive contents over the installation).
Any feedback is welcome.
Nice! I'll try to spin GTK3-based installers soon. Though it needs tiny patches to Geany (PR will follow).
Thomas, could you do me a favor and check against which libraries your geany.dll is linked? Basically performing a 'ldd' on Windows.
Attached is a short command session to dump object information from the DLL and then grep for "DLL Name" which lists linked libraries. This is somewhat similar to 'ldd' on Linux. You probably need to adjust the paths to the 'objdump' tool and the geany.dll (objdump.exe should be part of the Mingw installation and reside next to gcc.exe).
Background: Frank made me aware that on a clean Windows system, the provided installer won't start because it requires libwinpthread-1.dll which is not distributed by the installer but is part of the Mingw environment. I never noticed this because on my Windows system, the Mingw installation is in $PATH and so this library is always available.
I'm curious whether this happens also with your Mingw setup. I guess it will as it seems this is a change in newer gcc versions on Windows. But I want to get sure instead of just guessing :).
Right now, I'm playing with static linking options, already tried -static -lpthread but so far without success.
If it is just a requirement, we can probably distribute this library as well but if we can avoid it, even better.
For cross-compiling it's sometimes useful to add `-static-libstdc++` and `-static-libgcc` compiler/linker options, if not already there. Maybe they would compile that library into Geany.exe statically along with the std stuff.
Those are already used (https://github.com/geany/geany/blob/master/wscript#L271).
Another alternative might be `-static -lwinpthread-1` with or without the `-1`.
Thanks. I already tried static -lpthread and now also your variants but all without success :(. The geany.dll on my system is always linked against libwinpthread-1.dll, even after updating my Mingw environment.
I'll keep testing and trying...
I remember having this problem before, though I forget how I solved it :(
This looks kind of promising: http://stackoverflow.com/a/28001271
Cheers, Matthew Brush
On 03.7.2015 г. 02:03, Matthew Brush wrote:
On 2015-07-02 01:36 PM, Enrico Tröger wrote:
On 02/07/15 01:17, Matthew Brush wrote:
Another alternative might be `-static -lwinpthread-1` with or without the `-1`.
Thanks. I already tried static -lpthread and now also your variants but all without success :(. The geany.dll on my system is always linked against libwinpthread-1.dll, even after updating my Mingw environment.
I'll keep testing and trying...
I remember having this problem before, though I forget how I solved it :(
This looks kind of promising: http://stackoverflow.com/a/28001271
objdump of my Geany 1.25 "built on or after Apr 25 2015" with WAF, MinGW gcc-4.8.1 and binutils/ld 2.24:
DLL Name: comdlg32.dll DLL Name: kernel32.dll DLL Name: msvcrt.dll DLL Name: msvcrt.dll DLL Name: ole32.dll DLL Name: shell32.dll DLL Name: user32.dll DLL Name: wsock32.dll DLL Name: libcairo-2.dll DLL Name: libgdk-win32-2.0-0.dll DLL Name: libgdk_pixbuf-2.0-0.dll DLL Name: libgio-2.0-0.dll DLL Name: libglib-2.0-0.dll DLL Name: libgmodule-2.0-0.dll DLL Name: libgobject-2.0-0.dll DLL Name: libgthread-2.0-0.dll DLL Name: libgtk-win32-2.0-0.dll DLL Name: intl.dll DLL Name: libpango-1.0-0.dll DLL Name: libpangocairo-1.0-0.dll
Two links to msvcrt, but no winpthread. Hope that helps somehow...
-- E-gards: Jimmy
On 03/07/15 18:27, Dimitar Zhekov wrote:
On 03.7.2015 г. 02:03, Matthew Brush wrote:
On 2015-07-02 01:36 PM, Enrico Tröger wrote:
On 02/07/15 01:17, Matthew Brush wrote:
Another alternative might be `-static -lwinpthread-1` with or without the `-1`.
Thanks. I already tried static -lpthread and now also your variants but all without success :(. The geany.dll on my system is always linked against libwinpthread-1.dll, even after updating my Mingw environment.
I'll keep testing and trying...
I remember having this problem before, though I forget how I solved it :(
This looks kind of promising: http://stackoverflow.com/a/28001271
objdump of my Geany 1.25 "built on or after Apr 25 2015" with WAF, MinGW gcc-4.8.1 and binutils/ld 2.24:
The versions look like those I had until I upgraded my Mingw setup yesterday. Where did you get your Mingw from?
I'm using the one bundled in the Strawberry Perl distribution (http://strawberryperl.com/).
Regards, Enrico
On 03.7.2015 г. 22:55, Enrico Tröger wrote:
On 03/07/15 18:27, Dimitar Zhekov wrote:
objdump of my Geany 1.25 "built on or after Apr 25 2015" with WAF, MinGW gcc-4.8.1 and binutils/ld 2.24: [...]
The versions look like those I had until I upgraded my Mingw setup yesterday. Where did you get your Mingw from?
Got the installer from their official site, and used it to download everything else. No MSYS components, pure MinGW.
Haven't updated it recently. No *winpthread* in the MinGW tree.
-- E-gards: Jimmy
On 06/07/15 18:17, Dimitar Zhekov wrote:
On 03.7.2015 г. 22:55, Enrico Tröger wrote:
On 03/07/15 18:27, Dimitar Zhekov wrote:
objdump of my Geany 1.25 "built on or after Apr 25 2015" with WAF, MinGW gcc-4.8.1 and binutils/ld 2.24: [...]
The versions look like those I had until I upgraded my Mingw setup yesterday. Where did you get your Mingw from?
Got the installer from their official site, and used it to download everything else. No MSYS components, pure MinGW.
Haven't updated it recently. No *winpthread* in the MinGW tree.
Ok, thanks for testing and feedback. Since we want to release tomorrow, I won't start fiddling with my build environment anymore.
And post-1.25, we will hopefully use MSYS2 which also doesn't seem to have this dependency.
Regards, Enrico
On 03/07/15 01:03, Matthew Brush wrote:
On 2015-07-02 01:36 PM, Enrico Tröger wrote:
On 02/07/15 01:17, Matthew Brush wrote:
On 2015-07-01 02:45 PM, Matthew Brush wrote:
On 2015-07-01 12:33 PM, Enrico Tröger wrote:
On 27/06/15 20:53, Thomas Martitz wrote:
Am 27.06.2015 um 01:09 schrieb Enrico Tröger: > Hi, > > I've built new Windows installers from current GIT master. > > > Downloads can be found here: > http://download.geany.org/snapshots/ > > > Please note that these are test builds from the current development > version, don't expect release quality. > You have been warned :). > > After you installed the snapshots, you can also use the nightly > builds again on Windows (i.e. copy the archive contents over the > installation). > > > Any feedback is welcome. >
Nice! I'll try to spin GTK3-based installers soon. Though it needs tiny patches to Geany (PR will follow).
Thomas, could you do me a favor and check against which libraries your geany.dll is linked? Basically performing a 'ldd' on Windows.
Attached is a short command session to dump object information from the DLL and then grep for "DLL Name" which lists linked libraries. This is somewhat similar to 'ldd' on Linux. You probably need to adjust the paths to the 'objdump' tool and the geany.dll (objdump.exe should be part of the Mingw installation and reside next to gcc.exe).
Background: Frank made me aware that on a clean Windows system, the provided installer won't start because it requires libwinpthread-1.dll which is not distributed by the installer but is part of the Mingw environment. I never noticed this because on my Windows system, the Mingw installation is in $PATH and so this library is always available.
I'm curious whether this happens also with your Mingw setup. I guess it will as it seems this is a change in newer gcc versions on Windows. But I want to get sure instead of just guessing :).
Right now, I'm playing with static linking options, already tried -static -lpthread but so far without success.
If it is just a requirement, we can probably distribute this library as well but if we can avoid it, even better.
For cross-compiling it's sometimes useful to add `-static-libstdc++` and `-static-libgcc` compiler/linker options, if not already there. Maybe they would compile that library into Geany.exe statically along with the std stuff.
Those are already used (https://github.com/geany/geany/blob/master/wscript#L271).
Another alternative might be `-static -lwinpthread-1` with or without the `-1`.
Thanks. I already tried static -lpthread and now also your variants but all without success :(. The geany.dll on my system is always linked against libwinpthread-1.dll, even after updating my Mingw environment.
I'll keep testing and trying...
I remember having this problem before, though I forget how I solved it :(
This looks kind of promising: http://stackoverflow.com/a/28001271
Didn't work for me, tested already few days ago. Geany compiled fine but the geany.dll is still linked against libwinpthread-1.dll. I also tried all the other static compilation variants which can be found on the first two search result pages from Google :(.
Then I tried to remove the dll from my system, just hoping it will magically compile somehow without it but again no luck.
If I understand http://sourceforge.net/p/mingw-w64/mailman/message/31213279/ correctly, it is indeed a toolchain issue. If the assumptions in this thread are true, it depends on how gcc is built, whether it uses POSIX threads or Windows threads.
While playing around, I noticed that also Midori and the OwnCloud Windows client comes with the libwinpthread-1.dll distributed. Probably they got the same issue.
Since I can't spend even more time on this, I will include this .dll into the 1.25 installer. And I'm looking forward that the post-1.25 Windows installers are completely created using MSYS2 which seems not to have this dependency.
Regards, Enrico
On 27/06/15 01:09, Enrico Tröger wrote:
Hi,
I've built new Windows installers from current GIT master.
Downloads can be found here: http://download.geany.org/snapshots/
New installers uploaded, download location and installer names are the same.
Changes since last time: - include grep.exe to instantly use Find in Files without any further user interaction - updated included colorschemes from the geany-themes project - whatever happened in GIT master of Geany and Geany-Plugins
Thanks to Jiří.
Regards, Enrico