Mailing-List: contact stdcxx-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: stdcxx-dev@incubator.apache.org
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C6DBCA.BF1CFBF0"
Subject: wgcc 2.0 RC1 released
Date: Tue, 19 Sep 2006 11:05:25 +0200
Message-ID: <18597F2B47F1394A9B309945EC72411282DB97@servex01.wamas.com>
Thread-Topic: wgcc 2.0 RC1 released
Thread-Index: Acbbyr7QnURV5QqLT2eNY5WrAAVgWA==
From: "Duft Markus" <Markus.Duft@salomon.at>
To: <interix-wgcc-developer@lists.sourceforge.net>
Cc: <libtool@gnu.org>, <stdcxx-dev@incubator.apache.org>,
        <boost@lists.boost.org>

------_=_NextPart_001_01C6DBCA.BF1CFBF0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi again!
=20
For all interested in native Windows binaries built with Autotools and
mnay other interesting things:
=20
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.
=20
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).
=20
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.
=20
The Release Candidate 1 of wgcc has a completely rewritten Configuration
File parser, which allows for faster and safer parsing; now adding the
ability to include empty directives in configuration files. This could
be something like "paths.c++ =3D" to unset all C++ search directories.
=20
Also the ability to automatically generate export definitions and import
trampolines for mixing static and shared libraries with executables has
been reviewed and improved. This did not change the behaviour of wgcc
regarding the 2.0-pre.x versions, but only speeded it up a little.
=20
pxwc, the accompanying library for wgcc allows further abstraction for C
code, allowing use of the ANSI function names (i.e. without the leading
"_"). 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.
=20
Using the patch provided for GNU Libtool, wgcc can be used with many
Open Source packages. After patching and installing Libtool, simply
bootstrap the package in question, configure (set CC, CXX and LD to
"wgcc") and build. The configure Script should tell that the linker in
use is the "Interix to Win32 cross linker (wgcc)".
=20
Since the version jump to 2.x wgcc now resides in the Sourceforge
Subversion Repository. The CVS Repository still continues to contain
previous wgcc versions (0.x).
=20
To continue improving wgcc and pxwc packages, we now need your help in
testing them. Please download wgcc and try to compile you 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.
=20
You can browse the Subversion Repository here:
http://svn.sourceforge.net/viewvc/interix-wgcc/trunks/
=20
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


------_=_NextPart_001_01C6DBCA.BF1CFBF0--