Re: [ECOS] Installing source after full build

[Michael Jones <mjones@linear.com>]

John,

I could be wrong, but my observation was the ecos.db was not copied from the build (meaning the ecos and ecos config tool build), and neither was packages. The eCos Configuration tool certainly needs ecos.db, but I assume it needs the package tree. So unless there is some environment variable telling the Configuration tool where to find this, how would copying only the library work?

Perhaps you interpreted my build as the build done within the config tool. I am talking about the build of ecos and the config tool. I am compiling the whole thing rather than using a binary distribution so that I have access to the new Kinetis support.

Mike

On Dec 1, 2012, at 11:29 AM, John Dallaway <john@dallaway.org.uk> wrote:

> Mike
> 
> On 29/11/12 23:23, Michael Jones wrote:
> 
>> But I noticed that it does not copy source files or ecos.db from the
>> source dir to the target dir along with the binary stuff.
>> 
>> Is there a way to get all the code and db copied over via the make
>> process or do I just have to copy it?
>> 
>> Should I instead compile on top of the source tree directly?
> 
> When you build eCos, the eCos library (libtarget.a), linker script
> (target.ld), external header files and a few miscellaneous files are
> placed in the eCos "install" tree. These files are all you need to
> compile application code and link it with eCos to form a self-contained
> application executable. Your application code should not reference
> header files located within the eCos source code repository.
> 
> I hope this helps...
> 
> John Dallaway
> eCos maintainer
> http://www.dallaway.org.uk/john
> 
> -- 
> Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
> and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
> 


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