Mailing List Archive

On Fri, 29 Aug 2003 12:02:54 +0200, Ludovic LANGE said:

> This (attached) patch needs to be applied. it takes care of the following :

> * In random.c, use a gatherer in the Windows case.
> * In rndw32.c, one include missing, two prototypes that weren't renamed.

There is nothing missing - you are not using the right toolkit. There
will be no official support for Window using anything lese then
mingw32/cpd. We might change a few __MINGW32__ defines to _WIN32 to
get it back into sync with gnupg.



Shalom-Salam,

Werner

--
Werner Koch <wk@gnupg.org>
The GnuPG Experts http://g10code.com
Free Software Foundation Europe http://fsfeurope.org

Hello Werner,

It's the first time I hear about MinGW32/CPD, which seems to be a
package of yours (
http://cvs.gnupg.org/cgi-bin/viewcvs.cgi/mingw32-cpd/README?rev=1.5&cvsroot=wk%27s+Stuff&content-type=text/vnd.viewcvs-markup
) for cross-compiling Windows stuff on Linux platform.

( By the way I'm very interested, if there is an official web site
please redirect me to it. What is the relationship with the official
MinGW32 development ? )

I understand that your primary dev platform is Linux, and that's
understandable that you don't want to switch to a Windows box to
compile/test/release. Fine.

However, there may be some users that don't always have access to a
Linux platform when they want to quickly debug/test/compile Windows
stuff, or may be they use the libgcrypt library in another project,
whose development is Windows based.

Therefore I think that also supporting MinGW32 could be a good idea.
From what I understood, MinGW32/CPD 's goal is the same as MinGW32
(win32), so the differences between the two should be minimal, or
inexistant.

Just my 2 cents.

Regards,

Ludovic LANGE

Werner Koch wrote:
> On Fri, 29 Aug 2003 12:02:54 +0200, Ludovic LANGE said:
>
>
>>This (attached) patch needs to be applied. it takes care of the following :
>
>
>>* In random.c, use a gatherer in the Windows case.
>>* In rndw32.c, one include missing, two prototypes that weren't renamed.
>
>
> There is nothing missing - you are not using the right toolkit. There
> will be no official support for Window using anything lese then
> mingw32/cpd. We might change a few __MINGW32__ defines to _WIN32 to
> get it back into sync with gnupg.
>
>
>
> Shalom-Salam,
>
> Werner
>

On Fri, 29 Aug 2003 16:08:25 +0200, Ludovic LANGE said:

> Hello Werner,
> It's the first time I hear about MinGW32/CPD, which seems to be a

I has been used since ever for GnuPG's windows version.

> please redirect me to it. What is the relationship with the official
> MinGW32 development ? )

Mingw32/CPD is much older than mingw.org. It stems directly from
Colin Peter's mingw32. Sadly the mingw.org developers are not
interested in it and never replied to any mail asking to join efforts.

> Therefore I think that also supporting MinGW32 could be a good
> idea. From what I understood, MinGW32/CPD 's goal is the same as
> MinGW32 (win32), so the differences between the two should be minimal,

No they aren't. From time to time I add fixes to the runtime to make
development easier. That is, the primary goal is no build native
Windows programs from POSIX like sources.

If I can help folks to make it run under Windows I usually do so as
long as there are only minimal changes to the code required. Extra
source code branches for another toolkit are not possible. As said,
changing __MINGW21__ to _WIN32 is possible and Moritz or I will do it
eventually. This should make it easier to keep versions/patches in
sync to make it build on mingw.org.


Shalom-Salam,

Werner


--
Werner Koch <wk@gnupg.org>
The GnuPG Experts http://g10code.com
Free Software Foundation Europe http://fsfeurope.org