This is the mail archive of the
ecos-discuss@sourceware.org
mailing list for the eCos project.
RE: User libraries
- From: "Steven Clugston" <steven dot clugston at newcastle dot ac dot uk>
- To: <ecos-discuss at ecos dot sourceware dot org>
- Date: Wed, 16 Apr 2008 12:16:58 +0100
- Subject: RE: [ECOS] User libraries
>-----Original Message-----
>From: Davies, Greg [mailto:Greg.Davies@Ultra-UEMS.com]
>Sent: 16 April 2008 11:40
>To: Steven Clugston
>Subject: RE: [ECOS] User libraries
>
>
>> From: Steven Clugston
>> I would like to be able to create and link in some of my own
>> generic library code into an eCos app.
>> I am slightly phased by this due to the custom linker script
>> that is used by eCos.
>Don't worry about the linker script. You have to use it, but
>linking in regular static libraries is just a matter of using
>-l (and maybe -L), or at least that's been my experience. I
>don't have a readable makefile since I let eclipse take care
>of all that for me. You seem to have covered everything, no
>startup files, no standard libs, link whatever.
>
Thanks Gary and Greg.
As it happens, the libraries I want to use I've got already as eclipse
managed projects so it would be convienient if I could just create
another build profile for them for eCos as well as the standard Linux
Release/Debug ones.
I'm just curious how you've (Greg) setup the build with eclipse, do you
have all of your libraries as managed make project then the application
object as a standard make project for which you provide a makefile, or
are you able to set up a managed project to use the eCos linker script?
Steven
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss