Re: [wgcc-dev] Hey ho....

[Duft M. <Mar...@sa...>]

Hey again!
=20
The thing is, that wgcc should be the _lowest_ tool used in an interix =
environment. means there should be no other requirements, except a =
bootstrap compiler. using gcc is just as fina as using anything else, so =
i'm using gcc to build wgcc. anything else would require mie to hack =
something for the windows build to include interix stuff which i don't =
want it to be. the windows build should be plain windows, and should =
_never_ know anything about interix.
For that reason there is an interix build (using gcc). with cc it would =
be a windows build. Since wgcc was written to _replace_ cc (for me) i =
think it's senseless to build wgcc with cc. this would just bring in =
lots of hacks to make things work that would work anyway, and break =
things which _must_ work (like RTTI ;o))
=20
wgcc supports using third party C++ runtimes (stdcxx was used here, but =
anything else may be subtituted in instead, see .wgccrc (stdcxx.* =
options)).
=20
I repeat wgcc is the build tool, not a package built using some build =
tool, except the "native" compiler (where the interix native compiler is =
gcc/g++, and on win32 cl.exe is the native compiler). Anything else =
would be a cross-compilate, and producing those is definitly the task of =
wgcc.
=20
I'll look into adding a INSTALL file, or adding instructions to the =
docs.
=20
if you still wan't to look into this: to disable libtool you need to =
bootstrap the package. This is done using confix =
(confix.sourceforge.net) which needs python 2.4. you can use a windows =
python. when confix is installed use:
=20
confix.py --boo
=20
inside the wgcc source tree. if you want to enable libtool use:
=20
confix.py --boo --use-libtool
=20
wish you a nice weekend too ;o)
Cheers, Markus

________________________________

Von: Jerker B=E4ck [mailto:jer...@te...]
Gesendet: Fr 22.09.2006 17:03
An: Duft Markus
Betreff: RE: Hey ho....



> Sorry, i forgot to tell you to build wgcc with gcc/g++
OK, I go for a temporarily gcc build

Please write a detailed INSTALL file with instructions how to build in =
the
package.

I suspected that this is necessary in SFU since a MS C++ library is =
missing.
In SUA on the other hand we have a variant of the Dinkum library shipped
with VS 2005. In R2 SUA this is more or less a kind of quick and dirty =
port
but it will hopefully be improved in Vista SUA.

Of course I would not satisfy until I have a working build with the MS
tools. Can you examine my config.log to see where it goes wrong? Is =
there
any way to disable the libtool to let cc find it own libraries?

Note: A posix build in Visual Studio should work as good as any other
builds. Is there any special gcc tweaks (or GNU C++ library tweaks) =
used?

> Using the cc script to build is absolutely _not_ supported,
> since it uses different libraries, and different options...

Maybe a little early to argue about this until I have a working test
application, but here I absolutely disagree. Support for cc is really a =
MUST
HAVE. I also suspect a lot of people have tweaked their own C++ =
libraries
for SFU (based on MS Dinkum, stdcxx or STLport). So in my opinion, in =
any
case the C++ library used should be a matter of choice of the user.

Have a nice weekend
Jerker