I have a set of external .cpp and .c files (created outside of Rhapsody) that need to be included in builds, i.e. they need to appear in the makefile. The simplistic way of doing this is to list the files in the "Additional sources" line of a component, but this is a nuisance because a) there are quite a few of these files, so most of them are not visible in the "Additional sources" line, and b) there are a number of components that will use these external files. The combination of these means that when the set of files changes (not under my control!) there is a rigmarole of updating that needs to be done and the process is error-prone.

The Simulink integration somehow pulls in a load of external files into the makefile when they are listed in a tag under the Simulink block, so they are automatically included in any component that uses the Simulink block. But I'm not using the Simulink integration because it has problems.

I've submitted an enhancement request to IBM for an expansion of the code generation from dependencies between components: this is currently limited to the binary level (i.e. an executable build using a library), but if it could be expanded to build external source files in a depended-on component that would probably solve the problem. But as an enhancement I won't see that for a while yet and the problem is now.

Can anyone think of a neat way of avoiding the Additional Sources way of listing the source files?

One year later...

Did you fix your problem in the meanwhile, or has the requested enhancement been productized?

If not... would it be possible to put the list of your external files into a kind of "extFiles.list", which could then be included into the makefile generation template within the environment specific properties (property MakeFileContent)?
I think about an approach like in {RhpInstDir}\Share\LangCpp\oxf\ where all adapter specific makefiles like linuxoxf.mak and msoxf.mak include the (generated) generic list of oxf files, named "oxfFiles.list" in order to add them to any platform specific build process.
You could create a kind of "EnvWithExt" named environment, which adds such a file to the MakeFileContent and so uses it during the build process.

-Luke.