From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24573 invoked by alias); 17 Oct 2003 23:42:32 -0000 Mailing-List: contact ecos-discuss-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: ecos-discuss-owner@sources.redhat.com Received: (qmail 24565 invoked from network); 17 Oct 2003 23:42:32 -0000 Received: from unknown (HELO atheros.com) (65.212.155.130) by sources.redhat.com with SMTP; 17 Oct 2003 23:42:32 -0000 Received: from [10.10.16.68] (account adrian HELO atheros.com) by atheros.com (CommuniGate Pro SMTP 4.0.6) with ESMTP id 4348919 for ecos-discuss@sources.redhat.com; Fri, 17 Oct 2003 16:42:31 -0700 Message-ID: <3F907E5E.6020104@atheros.com> Date: Fri, 17 Oct 2003 23:42:00 -0000 From: Adrian Caceres User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax) X-Accept-Language: en-us, en MIME-Version: 1.0 To: ecos-discuss@sources.redhat.com Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: [ECOS] can drivers and other kernel components be linked to libtarget.a? X-SW-Source: 2003-10/txt/msg00333.txt.bz2 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