public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Gary Thomas <gary@mlbassoc.com>
To: Adrian Caceres <adrian@atheros.com>
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] can drivers and other kernel components be linked to libtarget.a?
Date: Sat, 18 Oct 2003 12:25:00 -0000	[thread overview]
Message-ID: <1066479943.20516.656.camel@hermes> (raw)
In-Reply-To: <3F907E5E.6020104@atheros.com>

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

      reply	other threads:[~2003-10-18 12:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-17 23:42 Adrian Caceres
2003-10-18 12:25 ` Gary Thomas [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1066479943.20516.656.camel@hermes \
    --to=gary@mlbassoc.com \
    --cc=adrian@atheros.com \
    --cc=ecos-discuss@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).