On Sun, Apr 26, 2015 at 3:16 PM, Noel O'Boyle <baoille...@gmail.com> wrote: > Hi there, > > I propose moving the MSVC-specific 3rd party libs, dlls and include > files to a separate git submodule. Or perhaps just a separate repo (to > avoid needless downloading for Linux/Mac users). > > One motivating factor is that I see in the future the need to check in > multiple versions of C++ libraries for each MSVC version; this is not > an issue with libxml and friends as these are C (not C++) libraries, > but jsoncpp.lib will need this. Additionally, if I want Appveyor to > automatically build the GUI, I'll need a compiler specific build of > wxWidgets and it just seems too much to have these in the current > repo. > > Any thoughts? > I think this is the way to go, and for the Avogadro development (along with several other projects) we use a similar approach. Open Babel is an inner project, a larger outer project will build the dependencies and Open Babel. This is actually used for packaging on most platforms.
Keeping binaries in source repositories is generally not ideal, but if you need to do it I think a separate repository for that purpose would be best. Marcus ------------------------------------------------------------------------------ One dashboard for servers and applications across Physical-Virtual-Cloud Widest out-of-the-box monitoring support with 50+ applications Performance metrics, stats and reports that give you Actionable Insights Deep dive visibility with transaction tracing using APM Insight. http://ad.doubleclick.net/ddm/clk/290420510;117567292;y _______________________________________________ OpenBabel-Devel mailing list OpenBabel-Devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openbabel-devel
