Timeline for Is it possible to ship libraries with code?
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 27, 2017 at 8:05 | comment | added | Brandin | You could include the source code of the libraries with your project. For example, if your project uses SDL, and you don't want your users to need to install that separately, just include it internally in your project as a subproject. | |
| Aug 26, 2017 at 16:50 | comment | added | Emerson Cardoso | I think so. Other possibility is to have your repository to point to other repository that contain you third-party lib`s source, and when you build your project you also build all of your dependencies before. Open-source projects like chromium do this. | |
| Aug 25, 2017 at 20:51 | comment | added | AndyM | I see.. so although it wouldn't be a good idea to store any binary/object/library files on git, for the reason you have just mentioned, it may still be beneficial to keep these libraries stored in a centralised place (such as Artifactory) and ship them with the code - rather than have the user's linker try find them somewhere in their own root directory? | |
| Aug 25, 2017 at 20:49 | answer | added | Arseni Mourzenko | timeline score: 1 | |
| Aug 25, 2017 at 20:40 | review | Close votes | |||
| Sep 18, 2017 at 3:01 | |||||
| Aug 25, 2017 at 20:40 | comment | added | Emerson Cardoso | I guess the best approach would be to use some package manager, like the one you mentioned (Conan). Then, you create and host your repository with your libraries (they could be publicly available or not). Versioning .a or .o is not feasiable, since GIT relies on text files to perform diffs. | |
| Aug 25, 2017 at 20:22 | history | asked | AndyM | CC BY-SA 3.0 |