From: Duft Markus (Markus.Duft_at_[hidden])
Date: 2006-09-19 11:11:48
Hm, really i started out porting from unix to windows using cccl, but it took not too long to realize that cccl is far to less powerfull. Cccl is capable of translating some command line options, not really much more. This doesn't mean cccl is bad. If one doesn't need more than this, its perfect. Wgcc is just _more_ and more powerfull.
Cccl has, i don't know, say 200 lines of shell script code?
Wgcc has about 10.000 lines of c++ code (9305).
It does a little more than just wrapping around the command line. It has many benefits over comparable wrappers like cccl, c89 (interix) and wcc (interix, see interopsystems.com) which are all shell scripts just wrapping some arguments.
You may want to take a look at the docs for rc.1. there is a section about building libraries with wgcc which may be of interest regarding this question...
Von: Albert Chin [mailto:libtool_at_[hidden]]
Gesendet: Dienstag, 19. September 2006 17:03
An: Duft Markus
Betreff: Re: wgcc 2.0 RC1 released
On Tue, Sep 19, 2006 at 11:05:25AM +0200, Duft Markus wrote:
> For all interested in native Windows binaries built with Autotools and
> mnay other interesting things:
> 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.
So, with this tool, someone doesn't need the cccl Visual C++ wrapper:
-- albert chin (china_at_[hidden])
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk