[ECOS] can drivers and other kernel components be linked to libtarget.a?

[ECOS] can drivers and other kernel components be linked to libtarget.a?

[Adrian Caceres]

I would like to develop a set of drivers (mostly network but other 
devices as well)
for ecos but I would prefer to treat them as an "ecos application".  In 
other words I would like
to develop them in my own source tree, and only link
the objects to libtarget.a in order to form the final executable.

As far as I can tell, there is no difference between a kernel component or
an application in ecos, but thought I would check since I am very new to 
ecos.

Is there some ecos assumption that is going to byte me if I go down this 
path?

- adrian









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

Re: [ECOS] can drivers and other kernel components be linked to libtarget.a?

[Gary Thomas]

On Fri, 2003-10-17 at 17:42, Adrian Caceres wrote:
> I would like to develop a set of drivers (mostly network but other 
> devices as well)
> for ecos but I would prefer to treat them as an "ecos application".  In 
> other words I would like
> to develop them in my own source tree, and only link
> the objects to libtarget.a in order to form the final executable.
> 
> As far as I can tell, there is no difference between a kernel component or
> an application in ecos, but thought I would check since I am very new to 
> ecos.
> 
> Is there some ecos assumption that is going to byte me if I go down this 
> path?
> 

No, you have it correct.  There is no system/user split (like in Linux
for example).  Everything is just the application.  The fact that the
kernel is common and comes from somewhere else (the public CVS sources)
is just a convenience.

-- 
Gary Thomas <gary@mlbassoc.com>
MLB Associates


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