Re: Patches and win32 build?

[Cyrille Chepelov <cyrille chepelov org>]

Le Wed, Sep 24, 2003, Ã 07:13:52PM +0000, debacle a Ãcrit:
> On Wed, Sep 24, 2003 at 03:14:03PM +0300, Steffen Macke wrote:
> > Sorry, this is my fault, component_feature.c is included
> > in the DLL - but I missed to copy the new shapes.
>
> OK, thanks for the information.  If I send new patches to
> dia - and I plan to do so - (how) can I help making the
> patch win32-able?

1. Stick to the published glib/gtk APIs
2. Never assume that the path separator is /, use the glib macros
3. when in doubt, assume the linker is dumber than your worst dreams.
4. avoid anything else than pure C compilation and linking (e.g don't
   depend on sed pre-processing, or a large python post-processing)
5. Remember that configure is not used on Win32; rather, there is a
   static config.h file. If what you do causes new tests to be added to
   configure.in, you have to provide the outcome on the win32 platform
   into the static config.h file.
6. Anything that touches Postscript and printing has chances to be
   different.
7. Beware anything approaching advanced interaction with the window
   manager -- the default unreplaceable window manager in Windows won't
   do what you expect it to (or more politely, the flexibility X offers
   and gtk thinly wraps doesn't map very well to the features offered by
   Win32).
8. This list is likely wrong and/or incomplete (especially as there are
   efforts to go to MinGW, which is a different toolchain compared to
   MSVC)
9. Look at the intersection of contributors to gtk-win32 and dia.

If what you are doing is confined to new object types, or straight GUI
work, and you don't do much file or network I/O and you do it carefully,
your odds are good out of the box.

        -- Cyrille

--