Re: arm-wince-pe configure

[Phil Edwards <phil at jaj dot com>]

On Mon, Jun 30, 2003 at 10:29:39AM -0600, Shaun Jackman wrote:
> I'm configuring libstdc++ directly at the command line.

This is what highly technical computer scientists call a Bad Thing.
(It was supported, and for a time was actually the only way to do things,
but has not been possible for quite a while.)

> It's not being
> configured with the rest of the compiler, though I would like it to. My
> gcc configure line is this:
> 
> ../gcc-3.2/configure --target=arm-wince-pe --prefix=/tools/wince
> --enable-languages="c,c++" --with-cpu=strongarm --disable-shared
> --with-newlib --enable-multilib=no

My cross-compiler fu is weak, but I would write that as

  ../gcc-3.2/configure --target=arm-wince-pe --prefix=/tools/wince
  --enable-languages=c++ --with-cpu=strongarm --disable-shared
  --with-newlib --disable-multilib

The C compiler is always built.

Depending on what else you already have installed, and how much you plan
to build, you might need to also get sources of ld, as, newlib, etc,
combine them into a single source tree, and go the whole thing at once.
(This actually makes cross-compilers easier, in my limited experience.)

Making a unified source tree is basically, "unpack all the sources
on top of one another, GCC goes last".  It's also described at
http://gcc.gnu.org/simtest-howto.html.


> Alternatively, is it
> possible to build libstdc++ in a separate tree?

Nope.


Phil

-- 
If ye love wealth greater than liberty, the tranquility of servitude greater
than the animating contest for freedom, go home and leave us in peace.  We seek
not your counsel, nor your arms.  Crouch down and lick the hand that feeds you;
and may posterity forget that ye were our countrymen.            - Samuel Adams