Separate Development

Manuel Pedro Coutinho manuelpedrocoutinho at hotmail.com
Wed Dec 29 15:12:58 UTC 2004


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?

Many thanks

Manuel Coutinho

_________________________________________________________________
MSN Messenger: converse com os seus amigos online. 
http://messenger.msn.com.br




More information about the users mailing list