• Simplex Update #1: Extreme modularization with CMake and Git
    1 replies, posted
[url]http://www.altdev.co/2013/08/16/simplex-update-1-extreme-modularization-with-cmake-and-git/[/url]
This is actually a really good idea (if you have an overarching repository that links the changesets together). I ran into a lot of trouble trying this with Git though since it's not easy to pull in dependencies using [I]other[/I] version control systems. I use modular approaches with my C# projects, the overarching repository contains the solution and the (Hg) subrepos with [code]x = ../x[/code] Bitbucket compatible paths each contain either one project or the solution dependencies (-NuGet since I use package restore). It's super smooth, works well when collaborating and means I never have to back-port improvements manually to older solutions. I can't comment on CMake, but I fully agree with separating dependencies, documentation and tests into separate repositories. A few OSS projects don't do this and pulling them in as source code dependencies is a nightmare or plain impossible. (OpenTK contains tons of additional code changes outside the core library that make the repository positively monstrous, Git-Annex's [I]contains [URL="https://github.com/joeyh/git-annex/tree/master/doc/bugs"]the user submitted bug tracker[/URL] (including colons in the file names) and [url=https://github.com/joeyh/git-annex/tree/master/doc/devblog]dev blog including comments[/url][/I]. :suicide:.)
Sorry, you need to Log In to post a reply to this thread.