Mailing-List: contact stdcxx-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: stdcxx-dev@incubator.apache.org
Received-SPF: error (idunn.apache.osuosl.org: domain salomon.at from
 193.186.16.13 cause and error)
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: Wgcc 2.0 RC2 released.
Date: Fri, 22 Sep 2006 08:40:21 +0200
Message-ID: <18597F2B47F1394A9B309945EC724112864B9B@servex01.wamas.com>
Thread-Topic: Wgcc 2.0 RC2 released.
Thread-Index: AcbeEfoQwJeeGPPtS7+SFa/1PhYodQ==
From: "Duft Markus" <Markus.Duft@salomon.at>
To: <interix-wgcc-developer@lists.sourceforge.net>
Cc: <stdcxx-dev@incubator.apache.org>, <libtool@gnu.org>,
        "David Abrahams" <dave@boost-consulting.com>

wgcc is a cross-compiler tool primarily written for Microsoft's Interix.
Its primary purpose is to produce native Windows binaries (internally
using the Microsoft Tool chain), and to mimic the behaviour of the GNU
compiler collection. This means that wgcc understands many of GCC's
command line arguments, and in most cases delivers the same results as
expected, sometimes manipulating the underlying tool's input and output.

Even though wgcc was written for Interix only, it can be used on native
Windows (without Interix), and other Systems, like Cygwin. The only
restriction is that on Platforms other than Interix, only Windows style
paths are understood. This will change in the future for Cygwin, and/or
others. On Interix wgcc automatically converts UNIX style paths to
Windows style ones (i.e. /wgcc to C:\SFU\wgcc).

wgcc abstracts away lots of inconveniences that are introduced by
building static libraries, shared libraries (DLL's) and executables with
any possible combination of those three. When using wgcc both static and
shared libraries behave exactly the same on Windows, and this makes tons
of defines unnecessary. The only thing that still has to be done is to
give all Data symbols (i.e. Variables) an import attribute
(__declspec(dllimport)) when using them (i.e. in the library header
files) in an executable. For a simple example take a look at the file
tests/shared.test inside the wgcc distribution.

The Release Candidate 2 of wgcc is more or less a bug fix release
compared to RC1. There is not too much new. Bug fixes include a nearly
complete rewrite of the Import Trampoline gererator and the Export
Definition generator, since those two worked very bad for C, but only
for C++.

pxwc has been reviewed and changed a little, to not include that many
defines, where inlined static functions are possible. Still pxwc
currently includes only a small set of functions, so your help is needed
to find out which others to include. Just open a Feature Request at
http://sourceforge.net/tracker/?group_id=3D158081&atid=3D806407 and we =
will
try to add functionality as soon as possible.

To continue improving wgcc and pxwc packages, we now need your help in
testing them. Please download wgcc and try to compile your software
using it. If something goes wrong please contact mduft or open an issue
using the Sourceforge Tracker at
http://sourceforge.net/tracker/?group_id=3D158081&atid=3D806404, or ask =
your
questions at the forums at
http://sourceforge.net/forum/?group_id=3D158081.

You can browse the Subversion Repository here:
http://svn.sourceforge.net/viewvc/interix-wgcc/trunks/

Documentation can be found here:
http://sourceforge.net/project/showfiles.php?group_id=3D158081&package_id=
=3D
203917&release_id=3D446943
Source Packages can be found here:
http://sourceforge.net/project/showfiles.php?group_id=3D158081&package_id=
=3D
177049&release_id=3D445894
The Patch for Libtool can be found here:
http://sourceforge.net/project/showfiles.php?group_id=3D158081&package_id=
=3D
196163&release_id=3D446510

Cheers, Markus