gcrypt windows build is done on linux, uses wine to run test suite

[Dan Kegel]

Here's an interesting tidbit.  gcrypt's windows version's only
supported build environment is mingw on unix/linux, and
it relies on wine to run its test suite.
- Dan

---------- Forwarded message ----------
From: Simon Josefsson <simon(a)josefsson.org>
Date: Thu, Dec 17, 2009 at 12:57 PM
Subject: Re: gcrypt windows build
To: "Hoyt, David" <hoyt6(a)llnl.gov>
Cc: Werner Koch <wk(a)gnupg.org>, "gcrypt-devel(a)gnupg.org"
<gcrypt-devel(a)gnupg.org>


"Hoyt, David" <hoyt6(a)llnl.gov> writes:
> > We only support cross-builds from a POSIX platform.  If you try to build it on the traget platform it may or may not work.
>
> How do you test a cross-compiled library? How do you run your test
> programs to validate your cross-compiled libraries are working
> correctly? Do you have any tips on how I could get the test programs
> working?

Use wine.  Just install MinGW and Wine under Linux, and then build
libgcrypt like this:

./configure --host=i586-mingw32msvc --build=i686-pc-linux-gnu

It will invoke the self-tests automatically, if you have the
binfmt-support package installed.

If you want a makefile that does everything, check out
<http://josefsson.org/gnutls4win/Makefile>.

/Simon

_______________________________________________
Gcrypt-devel mailing list
Gcrypt-devel(a)gnupg.org
http://lists.gnupg.org/mailman/listinfo/gcrypt-devel

gcrypt windows build is done on linux, uses wine to run test suite

[Jeff Zaroyko]

On Fri, Dec 18, 2009 at 8:34 PM, Dan Kegel <dank(a)kegel.com> wrote:
> Here's an interesting tidbit.  gcrypt's windows version's only
> supported build environment is mingw on unix/linux, and
> it relies on wine to run its test suite.
> - Dan

Similar case for libsndfile, the maintainer has also contributed to
Wine in the past.

"...I release a binary windows installer for
libsndfile. The binaries are generated using a Linux to Windows
cross-compiler and for the win32 version I run the testsuite under
Wine (windows API emulator). I then run INNO Setup under wine to
generate the installer executable."

http://www.mail-archive.com/haskell-cafe(a)haskell.org/msg68403.html

Jeff