I have a rhapsody project in which i have different configurations for building libraries and executables that use those libraries. Is there a way to automize the build process so that first the libraries are built and then the executable is built using the newly created libraries?

Thanks in advance

Presumably you have defined the dependencies to the libs via a dependency with <<Usage>> between components?

Recent versions of Rhapsody provide a Build with Dependencies option. Which version are you using?

Currently I'm using Rhapsody 4.01 but I will start using Rhapsody7.2 very shortly. I am not using dependencies with the keyword "Usage". What I am doing is as follows. For example assume I hava a library called a.lib and in that library I have interface and implementation classes. I am interested in using the services provided by the interfaces but not how these services are provided through implementation classes. In my executable project, I make use of the interface classes of the library. Therefore I define those interface classes in my executable project and make the "Use as External" property true and specify the filename to use. I add the a.lib library to the libraries of the project and the interface classes to the included files. There are occasions where I change both the library code and the executable code. In those occasions, I want to be able to rebuild the library project automatically while building the executable project so that I don't have to do two separate builds, one for the library and one for the executable.

Rhapsody didn't support the sort of control you want over your build back in the days of 4.01 (must be about 6 years ago).

It now comes as standard and I think it was introduced by 7.2. Why not use 7.4?