Re: Digest Number 600

James Michael DuPont writes:
 > OK, if tor would just clean and zip the packages that he
 > has with all the source code, including the glib 

GLib on Windows uses absolutely the same sources as on Unix. Just grab
the glib 2.0.6 distribution from
ftp://ftp.gtk.org/pub/gtk/v2.0/gtk+-2.0.6.tar.gz, unpack it, and
follow the instructions in README.win32. For GLib, there are
ready-to-use makefiles for gcc and MSVC, called makefile.mingw and
makefile.msvc. These should require minimal changes. (I.e., no auto*
necessary unless you really want to.)

 > and iconv

If I recall correctly, I compiled libiconv with MSVC, using the
Makefile.msvc file included in the sources. If you want to recompile
it with gcc, you will have to write a makefile. But that shouldn't be
hard. Libiconv is built from one single object file.

 > implementations, when the dlls are released then at least I can just
 > download the source packages and know that they are the same that are
 > build.

Why do thye have to be *exactly* the same? (I mean, the latest GLib I
provide at this moment seems to be GLib 2.0.4, but you should be able
to build 2.0.6 the same way.

 > Just a link to the compiler saying : you need this compiler, this
 > cross compiler etc., is fine.

Which is what README.win32 tries to do.

 > If you use the mingw32 compiler, I would say that you dont need to
 > deliver that, but basically all the libs..

Which is why I distribute prebuilt versions of libintl and libiconv.

 > I just dont want to spend another night or two getting all the parts
 > togeather and fighting with all the settings. 

But why do you want to do everything at the same time? Why not start
out with using the prebuilt libintl and libiconv, for instance, when
compiling GLib? Then, later, look at libintl, then on libiconv, for
instance? Then, later, tackle GTK+.