On 3/14/2016 8:29 AM, Michal Kubecek wrote: > On Mon, Mar 14, 2016 at 11:20:34AM +0000, Lester Caine wrote: >> The fact that git does not handle modular projects at all well was my >> main objection to being forced to use it. CVS had it's faults, but also >> it's good points, and being able to create a release made from cherry >> picked parts of the code tree was one which was blown apart by the git >> requirement that every part has it's own repository. It's only recently >> that the idea that 'sub-modules' are perhaps useful to some projects >> that is concept has started to be developed, > Recently? Git submodules were introduced in 2007. > >
Thanks for pointing this out -- I had no idea this existed. It solves a huge problem for me. I have a set of common base classes that are part of project A but are used in projects B, C, and D where other than wanting to share base classes, the projects are unrelated. It took a bit of trial and error (mostly giving up on externalproject_add in favor of manual "git submodule add ..."), but it works like a champ. The basic idea is that submodule add clones a readonly version of a project into another project's directory tree. Adding "exclude_from_all" to the add_subdirectory of the readonly project prevents the superfluous subprojects from being built, at least built automatically. The combination of cmake and git submodules would let the Firebird project to be decomposed in clean, separate, architecturally independent projects, a win-win all around. ------------------------------------------------------------------------------ Transform Data into Opportunity. Accelerate data analysis in your applications with Intel Data Analytics Acceleration Library. Click to learn more. http://pubads.g.doubleclick.net/gampad/clk?id=278785231&iu=/4140 Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel