hexchat / gtk-win32 Goto Github PK

Right now the powershell script doesn't work for me on x64. It may have been me who broke it, I don't know. Will look into it.

Well right now we are basically taking fan's and changing some variables on where it is going to be build the project and installed. Apart from probably changing something else. Why don't we just pick fan's style and we avoid having to maintain forked versions of the projects?

Hey guys, just wanted to concrete what kind of license the project has. If the same as hexchat I guess we should add the COPYING file to it.

Basically right now what happens is that you either build all the packages or you build one package with all the dependencies.

I'd actually would like to have something like "build.ps1 build gtk" which would basically be the same as "build.ps1 -OnlyOne gtk" but also have another command "build.ps1 buildone gtk" which would take care of only building gtk without the dependencies.

I did not see anything like that already implemented but let me know if I am wrong or if this feature is a WONTFIX.

The binary package for Win64 does not include glibconfig.h, which is mandatory.
Didn't test Win32.

Now that tar.xz/gz/bzip2 is supported I saw the upstream tarballs are used but still storaged on the hexchat web page. Why don't we just use the direct urls to those tarballs?

Now we have Win32 and x64 in gtk, but not in build. Let's fix it sometime.

List last updated: 2017-01-07
Packages last updated: 2016-09-06

* Next to name indicates we mirror the tarballs

Name | Version in gtk-win32 | Latest version

• atk* | 2.20.0 | 2.22.0
• cairo* | 1.14.6 | 1.14.8
• enchant* | 1.6.0 | 1.6.1
• fontconfig* | 2.8.0 | 2.12.1
• freetype* | 2.6.5 | 2.7.1
• gdk-pixbuf* | 2.34.0 | 2.36.3
• gettext* | 0.18 | 0.18 / 0.19.8.1
• glib* | 2.48.2 | 2.50.2
• gobject-introspection* | 1.48.0 | 1.50.0
• gtk* | 2.24.30 | 2.24.31
• harfbuzz* | 1.3.0 | 1.4.1
• lgi* | 0.9.1 | 0.9.1
• libffi* | 3.2.1 | 3.2.1 ftp://sourceware.org/pub/libffi/
• libpng* | 1.6.25 | 1.6.28
• libxml2* | 2.9.4 | 2.9.4 ftp://xmlsoft.org/libxml2/
• luajit* | 2.0.4 | 2.0.4
• openssl* | 1.0.2h | 1.0.2j / 1.1.0c
• pango* | 1.40.2 | 1.40.3
• pixman* | 0.34.0 | 0.34.0
• pkg-config | 0.29.1 | 0.29.1
• win-iconv* | 0.0.8 | 0.0.8
• zlib* | 1.2.8 | 1.2.10
• openssl certdata.txt | 2016-08-30 | 2016-09-23

Note: Ignore odd-numbered minor versions of atk, gdk-pixbuf, glib, gobject-introspection, gtk and pango because these are development releases.

Versions in latest HexChat release (2.12.0)

So I think it is better to have the information you currently have in the webpage also in the README. The reason is that in this way you do not need to open any web page if you have the repository cloned. i.e something like:

wingtk/gvsbuild@91e5f43

Let me know if it makes sense for you to change it and make a pull request.

It'd be great if the MSVC GTK+ bundle included pdbs for the DLLs. It's the main reason why I need to build from source - I need debug symbols.

Thank you for your work building up to date libraries for Win32.

Are the libraries compatible with Windows XP? i.e. were they built with the v140_xp platform toolset?

Scratch all the previous issues I opened before and let's discuss here first whether it would be good to have some kind of collaboration. First thing to point is that my previous issues where kind of proposals to know your opinions on the different topics for my specific use case.

I think this project is quite a good starting point in order to have something like jhbuild for windows where one can build their specific libraries or projects by using this powershell script.

Instead of just forking the project and do some stuff I'd really prefer to have it as a joined project where we would join effords also with upstream gtk people.

My main goals is to be able to easily build gtk3 and maybe some other libraries. Keeping everything in a way so I can build just a library or a library with the specific deps without the need of building everything. Also I would like to convert this in the way of getting some decent GTK binaries for MSVC.

I am adding @fanc999 since he is the current maintainer of the GTK mvsc projects, in case he wants to add something to this.

When using the GTK build provided by this project, I get a following compiler error:

7>d:\program files\microsoft visual studio 12.0\vc\include\xkeycheck.h(203): warning C4005: 'inline' : macro redefinition
7>          c:\gtk\include\libintl.h(23) : see previous definition of 'inline'
7>d:\program files\microsoft visual studio 12.0\vc\include\xkeycheck.h(250): fatal error C1189: #error :  The C++ Standard Library forbids macroizing keywords. Enable warning C4005 to find the forbidden macro.

The solution is to remove/comment following lines at the top of the libintl.h file:

#ifdef _MSC_VER
#define inline __inline
#endif

The compiler I use is VS 2013 Community edition.

Now they generate makefiles during a GTK+ build. Generate solutions instead, modify them according to our build practices and add them to the repo.

This also means CMake won't be required for a GTK+ rebuild, only for win-iconv and gettext-runtime bumps (very rare).

I'd like very much to have 2 additional engines: Clearlooks and Aurora.

Clearlooks theme using Clearlooks engine:

Aurora theme:

Only thing left is to use the prepared property in those 2 instances (@call ...).

See wingtk/gvsbuild@438ac86
and wingtk/gvsbuild@50f6ba5

Although I guess we would need to first fix the build/buildone topic first in order to not pull this requirement for hexchat and also for my case to not pull gtk2 if I just want gtk3

• Add pkg-config files to more projects, at least for gtk but ideally everything we can (lua, python, openssl)
• Build all of gettext such as xgettext
• Find best way to install Meson (simply a python module, pip.exe install meson is enough)

Hi,

I'am following steps for Building from Source on Windows 8.1 64 Bit with Visual Studio 2013 Community Edition and glib always fails. Due to this glib dependent libraries also fails.

Steps to reproduce bug :

• Follow instructions given for Building from Source

Screenshot of shell log :

getgettext-runtime = 0.18.2.1
HarfBuzz = 0.9.18

in our gtk3 fork of the gtk-win32 script I updated harfbuzz to the latest version and switched to use Fan's nmake files. This also removes the need to manually install ragel.exe which is a nice side effect.

wingtk/gvsbuild@37c573e

I think the patch should more or less apply to the upstream version of the script (I guess you may prefer to host the tarball yourselves for consistency with the rest). You may also need yto update to the latest pango which has the MSVC project fixed to look for the harfbuzz headers in the right place (patch is also available in the fork, but that is pretty mechanic to redo)

Hi,

I'am trying to build libraries with /MT flag. Is there a way to build with this type of specific settings? I tried to do it manually with text search&replace to cloned hexchat/gtk-win32 repo didn't help. If there is im happy to update readme instructions to include such a route.

So the new stable released was just released. I guess it is a good time to start checking if it builds fine and whether we need some patch upstream

	if (access ((char *) test_dir, W_OK|X_OK) == 0)
	{
	    cache_dir = test_dir;
	    break;
	}

W_OK|X_OK=3

but this is invalid on WIndows: https://msdn.microsoft.com/en-us/library/1w06ktdy.aspx?f=255&MSPPError=-2147217396

Can you apply the patch from https://bugzilla.gnome.org/show_bug.cgi?id=649390? I don't know if it applies to hexchat, but it definitely applies to other software using your binaries.

If possible, please add support to build gtksourceview 2.x in this project,

I assume it is not so much work for you and a lot of people would benefit from this, so you would get more exposure and testing of the GTK stack you provide.
Perhaps in the future, even hexchat could benefit by using this widget (autocompletion, line numbers, syntax highlighting, ...)

Being done in gi branch.

• gobject-introspection
• luajit and lgi
• pkg-config files for cairo, gdk-pixbuf, atk, pango
• introspection files for pango, atk, gdk-pixbuf
• introspection files for gtk (requires backporting work from gtk3)

It used to crash, thanks to ZLIB_WINAPI.

Just wanted to thank all you of you that are involved in this project. It is a miracle that this even exists.

Right now I think we use mozilla-build just for a few things that it provides. mozilla-build also uses msys which is kind of deprecated right now. Instead we should probably use msys2