3: what would it take to compile existing GTK program tarballs (with configure scripts etc.)? The main problem I ran in to, is that the configuration of Linux tarballs usually works with dynamic linked .so files whereas Win32 dll's are handled a little different.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Answer to your questions. Sorry it's taken so long. If you want quicker answers, e-mail me (b.drake@ntlworld.com) or Ishan, the creator of the project. We haven't got into the habit of looking at this area regularly.
1) The entire project is built around mingw
2) The Glade port is recent - BUT it is modified a fair bit to take into account Windows limitations. It looks the same as the latest Glade release though.
3) For the most part, it's a straight port from the source tarballs. All libraries are provided with .a stubs which handle the dll's so you don't have to. Just link to the stubs just like you do when you work in Linux. The bits that won't work though are any calls to Gnome widgets that are not in GTK+
We don't at this time have an implementation that mimics ./configure - you have to get your makefile up and running yourself. If that's a problem, you might want to consider our add-on package DevEx that installs over Dev-C++ and allows full GTK compilation with a ready made template.
The Alpha file of DevEx is not complete but works. Beta out in the next two or three days.
Regards,
Barry Drake
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi there,
I have some questions considering the project and its comparison to other Win32 ports of GTK:
1: what compiler is included in the winGTK package? Is it the cygwin or mingw port of gcc, or something different?
2: what version of Glade is the wGlade binary? (On http://hb2.seikyou.ne.jp/home/northriv/Glade/
gtkapp.html there is a 0.5.9 version available)
3: what would it take to compile existing GTK program tarballs (with configure scripts etc.)? The main problem I ran in to, is that the configuration of Linux tarballs usually works with dynamic linked .so files whereas Win32 dll's are handled a little different.
Answer to your questions. Sorry it's taken so long. If you want quicker answers, e-mail me (b.drake@ntlworld.com) or Ishan, the creator of the project. We haven't got into the habit of looking at this area regularly.
1) The entire project is built around mingw
2) The Glade port is recent - BUT it is modified a fair bit to take into account Windows limitations. It looks the same as the latest Glade release though.
3) For the most part, it's a straight port from the source tarballs. All libraries are provided with .a stubs which handle the dll's so you don't have to. Just link to the stubs just like you do when you work in Linux. The bits that won't work though are any calls to Gnome widgets that are not in GTK+
We don't at this time have an implementation that mimics ./configure - you have to get your makefile up and running yourself. If that's a problem, you might want to consider our add-on package DevEx that installs over Dev-C++ and allows full GTK compilation with a ready made template.
The Alpha file of DevEx is not complete but works. Beta out in the next two or three days.
Regards,
Barry Drake