Separate Development

Manuel Pedro Coutinho manuelpedrocoutinho at hotmail.com
Wed Dec 29 19:34:49 UTC 2004



>From: "Joel Sherrill <joel at OARcorp.com>" <joel.sherrill at OARcorp.com>
>Reply-To: joel.sherrill at OARcorp.com
>To: Manuel Pedro Coutinho <manuelpedrocoutinho at hotmail.com>
>CC: rtems-users at rtems.com
>Subject: Re: Separate Development
>Date: Wed, 29 Dec 2004 09:36:22 -0600
>
>Manuel Pedro Coutinho wrote:
>>Hi
>>
>>I'm trying to separate the RTEMS development so that a user can have 
>>access to the modified RTEMS version but hasn't a real knowledge of it's 
>>internal details.
>>
>>Presently, I thought of making 3 different types of users:
>>
>>  a RTEMS official version user
>>  a development user that modifies the official version
>>  a "dumb" user that uses the modified RTEMS version
>>
>>the official version would have the cross-compiler and the RTEMS sources
>>
>>the development user would have access to the official version but would 
>>make "small" changes in order to include a new driver, BSP, etc.
>>
>>the "dumb" user would use the compiled version of the development user.
>>
>>The development user would have to be the more complex since it has to 
>>modify at least the Makefile.am in some directories and possibly add new 
>>ones (new driver or BSP). The modification of the original source tree is 
>>out of the question because it may generate inconsistencies if the process 
>>fails and stops at half-way, so an alternative way of building is to have 
>>the copy of the directory structure of the RTEMS source containing only 
>>the Makefiles and in the SUB_DIRS parameter place the correct path (for 
>>example, if a directory and all of its sub-directories were of the 
>>original package, then one only has to refer to that directory and not 
>>copied its sub-directories to the development user because the build 
>>process would continue through the original source)
>>
>>Does anyone have suggestions about this process or have even done a 
>>similar (or different)
>>approach?
>
>Ralf should wade in here but the general development direction for
>RTEMS has been to separate out the "CPU Kit" from the "BSP Kit".
>The CPU Kit could then but pre-compiled and the user would only
>have to build a BSP.  Is this what you are trying for or are you
>trying to ship a custom BSP?
>
>>Many thanks
>>
>>Manuel Coutinho
>>
>>_________________________________________________________________
>>MSN Messenger: converse com os seus amigos online. 
>>http://messenger.msn.com.br
>>
>
>
>--
>Joel Sherrill, Ph.D.             Director of Research & Development
>joel at OARcorp.com                 On-Line Applications Research
>Ask me about RTEMS: a free RTOS  Huntsville AL 35805
>    Support Available             (256) 722-9985
>


Perhaps my explanation wasn't the best... (sorry)
When I said to develop a new driver or BSP I didn't mean only these in 
particular. My goal is to have any (and I mean really any) change in the 
source tree to be transparent to the end user, not just some “minor” changes 
in the BSP or driver or even CPU.


You said that one could pre-compile the CPU kit and the user could just 
build the BSP and link them (with the application). How exactly can this be 
done? (or where could I find some documentation)


Many Thanks
Manuel Coutinho

_________________________________________________________________
MSN Hotmail, o maior webmail do Brasil. http://www.hotmail.com




More information about the users mailing list