5 Libraries and Separate Compilation
The current implementation of separate compilation in Vortex imposes two minor restrictions on how the library objects and methods can be extended by an application. In particular, applications compiled with use_shared_libraries set to true (the default value) may not extend a library by either:
However, since dependencies are not maintained for library code when compiling in library mode, violations of these restrictions will not be automatically caught by Vortex and may result in unexpected behavior. The only safe way to allow an application to extend a library in one of these two forbidden manners is to disable separate compilation for the application (by setting use_shared_libraries to false) and recompiling with make.
Vortex does not provide a way for a programmer to modify some of the library files while still using the rest of the precompiled libraries. If you want to have your own file supercede the file with the same name in the library, you need to disable separate compilation (see Section 5.3).