This is the mail archive of the
ecos-discuss@sourceware.org
mailing list for the eCos project.
RE: HOW TO compile and include thirdparty libray.
- From: "Ramesh Chandra Satyavaram" <rameshcs at danlawinc dot com>
- To: "'Gary Thomas'" <gary at mlbassoc dot com>
- Cc: <ecos-discuss at ecos dot sourceware dot org>
- Date: Fri, 6 Aug 2010 15:54:26 -0400
- Subject: RE: [ECOS] HOW TO compile and include thirdparty libray.
- References: <1279611958.16807.ezmlm@ecos.sourceware.org><004001cb283a$9da87bf0$aa01a8c0@danlawinc.com> <AANLkTilcHoeaDHy-3nYERbWvHQoEh_k0ew2G-KwgAIJR@mail.gmail.com> <002401cb3599$aacbc320$aa01a8c0@danlawinc.com> <4C5C60AA.5090404@mlbassoc.com>
Hi Thomas,
Thanks for your mail.
I understand the following from your response.
a. Build the ecos.
b. Using the ecos and the compilation tool (arm-elf which is used to build
the ecos ) compile the third party application. This could be a
'.o'
file with out linking.
c. Finally link the customer supplied '.o' file or with the application.
Are these steps correct?
Thank you,
Rmaesh Chandra.
-----Original Message-----
From: Gary Thomas [mailto:gary@mlbassoc.com]
Sent: Friday, August 06, 2010 3:21 PM
To: Ramesh Chandra Satyavaram
Cc: ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] HOW TO compile and include thirdparty libray.
On 08/06/2010 01:00 PM, Ramesh Chandra Satyavaram wrote:
> Hi,
>
> I am working on a project that uses the ECOS. We have a requirement
with
> our customer. The Customer provides the compiled library and that should
> be linked with out application. I want to know the procedure on how to do
> this.
>
>
>
> We are using the ARM Based AT91SAM7XX micro controllers.
>
> We are using the "arm-elf "cross compilation tools.
>
>
>
> Should the customer also use the ECOS for compilation or is it enough to
> compile with arm-elf-gcc?
Yes, they should build using the same toolchain and include tree (from your
eCos kernel build tree) as you use to build the kernel.
> How to include the library with our application?
>
>
> Could any one help on this?
Try looking at this example:
http://www.mlbassoc.com/examples/build_httpd.html
It shows how to build an eCos application using a separate library/module.
This
particular example is self contained, but it should show you how to do it
with
your customer's library.
--
Please keep your replies on the mailing list(s) so that all
may benefit. Private support is available under contract
from various agents, including MLB Associates. Private
email to me without a contract will be ignored.
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss