Found the answer. I checked "do not search standard library's", so the
compiler would not search in the "include" directory. Works like a
champ now.
Onward to bigger and better problems....
Rich
--- In wrote:
>
> I think the key to use Eclipse in a cross-platform environment is to
use
> "Standard Make" rather than "Managed Make."
>
> With the standard makes you are pretty much just doing what the make
file
> says; with the managed make Eclipse is doing a lot more. It
probably is
> possible to cross compile using the managed make but I haven't found
a way
> to do it.
>
> My guess on the original issue is you are somehow including two
differenet
> stdio.h files.
>
> wrote on 08/21/2007 06:59:51 AM:
>
> >
> > Hi,
> >
> > I use Eclipse 3.2 with Windows and Cygwin. But I try to help you.
> > I use this method to compile an executable :
> > 1. File -> new -> Standart Make C Projet
> > 2. next
> > 3. Discovery tabs
> >
> -> Compiler Invocation Command -> point on your cross compiler path
-> use arm-
> > linux-gcc
> > 4. Binary parser tabs -> check GNU Elf parser (maybe is diffrent
> > because I use Windows OS)
> > 5. finish
> > The next step is your own make file.
> > You
> >
> must notified the Make Target tabs (Windows -> show view -> Make
Target) : all, clean ....
> >
> > To compile, just use your Make Target rules.
> >
> >
> > Regards
> > Romain
> >
> >
> > --- In "mrjbradski" <rich@> wrote:
> > >
> > > I have been trying to use Eclispe/Ubuntu as a cross development
> > > platform for the arm. Im no pro in the linux world. Anyway, I
created
> a
> > > new profile in eclipse named arm-debug, and pointed to the
following
> > > inlcude directory:
..../crostool/arm-linux/gcc-3.3.4-glibc-2.3.2/arm-
> > > linux/include, library path of
> ..../crostool/arm-linux/gcc-3.3.4-glibc-
> > > 2.3.2/arm-linux/lib. I also used the bin's located in
> > > the ..../crostool/arm-linux/gcc-3.3.4-glibc-2.3.2/arm-linux/bin
> > > directory.
> > >
> > > Next, I created a basic hello world app, using the include of
> > > <stdio.h>. Press build, then got 28 errors parsing the stdio.h
file.
> > >
> > > For the heck of it, I deleted the include statememt, build, and
I got
> a
> > > executable that really worked on my arm platform!
> > >
> > > SO... what is wrong with the stdio.h file... or should I put it,
what
> > > is wrong with what I did?
> > >
> > > Thanks
> > >
> > > Rich
> > >
>
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/ts-7000/
<*> Your email settings:
Individual Email | Traditional
<*> To change settings online go to:
http://groups.yahoo.com/group/ts-7000/join
(Yahoo! ID required)
<*> To change settings via email:
<*> To unsubscribe from this group, send an email to:
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
|