version control - Including pre-compiled libraries in source tree -


i have cross-platform c++ project. in project, use several third-party, statically-compiled libraries quite huge , not easy build.

currently, our source tree looks this:

| +-3rdparty | +-include   (initially empty) | +-lib       (initially empty) | +-some-library | +-another-library | +-source 

when checking out code, developer first build , install "some-library" , "another-library". install step put right files include , lib folders, , can build our project.

in order make building our project easier, thinking of removing "some-library" , "another-library", , instead put includes , pre-compiled binaries include , lib folders. way, new developper have checkout project, , build straight away.

my questions are:

  1. is bad practice so? (ie: including precompiled libraries source tree).

  2. what potential problems / drawbacks may arise setup?

  3. what folder organization suggest account several platforms (windows, mac osx, , linux)?

additional note: using mercurial.

i have worked version control systems absolutely refused keep old versions of binary files. long time ago, , don't think it's problem current vcs, check before going live idea.

if third-party library gets updated often, repository might pretty big.

aside that, i've seen done, , seen work.


Comments

Popular posts from this blog

ASP.NET/SQL find the element ID and update database -

jquery - appear modal windows bottom -

c++ - Compiling static TagLib 1.6.3 libraries for Windows -