Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>You've asked a general question but also asked specifically about a few instances. I'm going to lean towards being more general. The short answer: this is a build system concern, not a version control system concern.</p> <p>In the case of Java, there are a few different dependency management/resolution tools that you can use. The build system should understand how to fetch those dependencies <em>at build time</em> and make them available. They are, however, transient - you don't check them in to version control. Furthermore, Maven - for example - uses a <code>/target</code> folder that both contains your output (e.g. output.zip - which I'd also recommend because it makes cleaning output easier. What if you have more than one output file? What about variants? etc.) as well as other items such as static analysis output - and it also uses an external directory to locally cache dependencies, but this could be ephemeral and it wouldn't care. Bottom line: it's not persisted in to a version control.</p> <p>This is not nearly as easy in C++ as far as I know. CMake <a href="http://www.kitware.com/media/html/BuildingExternalProjectsWithCMake2.8.html" rel="nofollow">seems to support</a> building external projects. I've only recently started to play around with this to see what is possible, so I don't want to mislead you by saying "it can easily be done", but it stands to reason that it can be done, the question is only how much work you have to put in to it. So whether or not you call the folder <code>/libs</code>, you should make the build treat dependencies as transitive (and then good luck with transitive dependencies).</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload