On 04/12/2011 11:09 AM, Thomas Wolf wrote: >> Hi Thomas, >> >> I see... copying the MITK sources and using the build-system does not >> work if the sources are not part of a Git repository. We might >> consider fixing this, but this is a rather "exotic" use case. >> >> Instead, I would suggest to use the CMake ExternalProject module to >> clone a specific revision of the official MITK git repository. You can >> also specify a patch step to automatically patch the cloned MITK >> source tree, if you need to. >> >> Best, >> Sascha > Hi Sascha, > > basically you are right, but i have to disagree considering the usage of > a different SCM as exotic... There are numerous systems out there, and > in our case it proved quite advantagous to be able to version also the > patches; Because after you update the externals, you can track your > patches and even recreate them trough the SCM, in our case svn, in which > mitk (together with its own externals) again is just an external... One > of the benefits is that our team just has one SCM in use, not several > (for the different projects that could be pulled in). Versioning the > whole thing under the watch of one SCM is pretty much boosting > homogenity within the project. But i digress.. > > I personally think one should avoid awaiting a certain SCM to be used as > a project foundation. Sure, we cannot pull in the software version, but > that can be written down manually when the sources get synced. On the > other hand, just using svn should not mean that the build aborts with an > error. > > Regards, > Thomas
Hi Thomas, I think you got me wrong, I'm not saying that a different SCM is exotic :-) I was referring to the case of copying source code which is managed with e.g. git into a SVN based repository (for example). If you don't use proper conversion scripts, you will loose the actual history of the external project (which might be fine if you are using a stable release). I also was not criticizing your setup :-) If it works for you, thats perfectly fine. My suggestion was to keep your patches in your SVN repo and to use ExternalProject from CMake (which is quite easy to use) to clone/patch/configure/build MITK. But this would of course require a git installation on all your machines. Patches which fix the MITK git-dependent build system parts are always welcome! Best, Sascha ------------------------------------------------------------------------------ Forrester Wave Report - Recovery time is now measured in hours and minutes not days. Key insights are discussed in the 2010 Forrester Wave Report as part of an in-depth evaluation of disaster recovery service providers. Forrester found the best-in-class provider in terms of services and vision. Read this report now! http://p.sf.net/sfu/ibm-webcastpromo _______________________________________________ mitk-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mitk-users
