This is the mail archive of the ecos-discuss@sources.redhat.com mailing list for the eCos project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Including Standard search path problem


On Wed, Feb 18, 2004 at 08:51:18AM +0000, Leo McManus wrote:

> Building for an ARM 720 on an ARM Integrator board.  Am having a
> problem including standard include files in my eCos subdirectories
> into my search path. Have used the '-I-' switch to search the
> directory for the <cyg/kernel/kapi.h> header, but it gives a " No
> such file or directory" error,

> (output below).
> 
> The kapi.h file is in
> /Install/eCos4Usb/build/ecos-integrator/integrator_install/include/cyg/kernel
> which I have put the '-I-' switch on. (NOTE just using '-I' I have the same
> problem) but it connot find it.
> 
> My arm-elf-gcc -v output is:
> 
> Reading specs from /opt/gnutools/lib/gcc-lib/arm-elf/3.2.1/specs
> Configured with: /Install/GnuTools/gcc-3.2.1/configure --target=arm-elf
> --prefix=/opt/gnutools --enable-languages=c,c++ --with-gnu-as --with-gnu-ld
> --with-newlib --with-gxx-include-dir=/gnutools/arm-elf/include -v :
> (reconfigured) /Install/GnuTools/gcc-3.2.1/configure --target=arm-elf
> --prefix=/opt/gnutools --enable-languages=c,c++ --with-gnu-as --with-gnu-ld
> --with-newlib --with-gxx-include-dir=/opt/gnutools/arm-elf/include/ -v
> Thread model: single
> gcc version 3.2.1

This all looks normal.

 
> HOW DO I INCLUDE THE ".../include/cyg" PATH TO SEARCH FOR MY STANDARD HEADER
> FILES?
> 
> SHOULD I PUT THE SEARCH PATH ON THE CONFIGURATION LINE WHEN I BUILD THE GCC?
> SO:

No need to shout!

 
> --with-gxx-include-dir=/opt/gnutools/arm-elf/include/: \
> /Install/eCos4Usb/build/ecos-integrator/integrator_install/include

No. There is no need to do anything special with the compiler.

> Compiler O/P:
> 
> arm-elf-gcc -c -mcpu=arm7tdmi -Wall -nostdinc -DARM_INTEGRATOR -Wpointer-arith
> -Wstrict-prototypes -Winline -Wundef -Woverloaded-virtual -g -O2
> -fno-schedule-insns -ffunction-sections -fdata-sections -fno-rtti
> -fno-exceptions -fvtable-gc -finit-priority-fno-exceptions -fvtable-gc
> -finit-priority 
> -I/Install/eCos4Usb/build/ecos-integrator/UsbOtg/usbStack/source/include
> -I-/Install/eCos4Usb/build/ecos-integrator/integrator_install/include/
> -I/opt/gnutools/arm-elf/include
> -I/opt/gnutools/lib/gcc-lib/arm-elf/3.2.1/include
> /Install/eCos4Usb/build/ecos-integrator/UsbOtg/usbStack/source/arm.c
> 
> /Install/eCos4Usb/build/ecos-integrator/UsbOtg/usbStack/source/arm.c:26:30:
> cyg/kernel/kapi.h: No such file or directory

Its not clear where you are trying to build here. Are you building the
eCos library or your application? When building the eCos library the
build system will make sure the include paths are correct. For you
application code i suggest you look at the example makefiles. This is
part of anoncvs and you can also find at it:

http://ecos.sourceware.org/cgi-bin/cvsweb.cgi/ecos/examples/Makefile?rev=1.4.2.1&content-type=text/x-cvsweb-markup&cvsroot=ecos

        Andrew

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]