You could add the library to your product modules and build them all at once. However, I find that a better method is to subject the libraries to the same kind of control as the rest of the product (with regular builds, tagging sources, defect tracking and change control, etc.) and provide a set of well-known interfaces that can be used and tracked by the product builds. The references themselves should be versioned in some way, via source-controlled build scripts or environment settings, or by sampling the build environment and checking it in.
A method that I've used with great success on many projects is the buildref method. You can find an implementation at the following URL: http://www.wakawaka.com/source.html --- Forwarded mail from [EMAIL PROTECTED] I have some projects that share some libraries. Does CVS allow to have a common set of libraries that will be used by different projects?, in other words, I need one copy of these libraries and a reference to them in each of the other projects. --- End of forwarded message from [EMAIL PROTECTED] _______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/info-cvs
