name mode size
.bootstrap 040000
bin 040000
demo 040000
dox 040000
tests 040000
tutorial 040000
.gitignore 100644 161B 100644 5.93kB 100644 477B
LICENSE 100644 1.54kB
Makefile 100644 1.15kB 100644 3.91kB 100644 11.95kB 100644 11.35kB 100644 305B 100755 1.35kB 100755 1.78kB
mulle-bootstrap 100755 8.47kB 100755 6.15kB 100644 3.31kB 100755 48.63kB 100755 6.51kB 100755 29.15kB 100755 16.51kB 100755 2.9kB 100755 5.97kB 100644 7.42kB 100755 4.64kB 100644 3.07kB 100755 12.68kB 100644 5.37kB 100755 5.09kB 100755 14.18kB 100755 5.15kB 100755 4.12kB 100755 11.49kB
mulle-bootstrap.sublime-project 100644 143B 100755 761B
# mulle-bootstrap, cross platform dependency manager * fetches [git](// repositories (called here the "dependents"). In times of need, it can also checkout [svn](// * builds [cmake](//, [xcodebuild](// and [configure](// projects * compiles dependents using the output of previous dependents * written in portable shell script, runs on OS X, FreeBSD, Linux ## Tell me more * [How to install]( * [What has changed ?]( * [mulle-bootstrap: A dependency management tool]( * [mulle-bootstrap: Understanding mulle-bootstrap (I)]( * [mulle-bootstrap: Understanding mulle-bootstrap (II), Recursion]( ## What mulle-bootstrap can do for you So you need a bunch of first and third party repositories to build your own project ? **mulle-bootstrap init** does the initial setup of the `.bootstrap` folder. Lets put the git repository URLs in a file called `.bootstrap/repositories`. ```console cat > .bootstrap/repositories ``` **mulle-bootstrap** will check them out into a common directory `.repos`. If there is a local clone of the repository **MulleScion** in the parent directory of the project, then mulle-bootstrap can clone (or even symlink) from there, if you want. After cloning **mulle-bootstrap** does a simple security check with respect to `.bootstrap` shell scripts and Xcode script phases. Finally it looks for a `.bootstrap` folder in the freshly checked out repositories! They might have dependencies too, if they do, those dependencies are added to the source repositories dependencies. Everything you need should be present at this time. so **mulle-bootstrap** will now build a **Debug** and a **Release** version for each library, and place the headers and the produced libraries into the "./dependencies" folder. Your Xcode project can be optionally massaged by **mulle-bootstrap xcode add** to have the "./dependencies" folder in its search paths. ## Commands for a project user #### mulle-bootstrap Download a project which is mulle-bootstrap enabled. Execute mulle-bootstrap in it and you are all set: ```console mulle-bootstrap ``` `mulle-bootstrap` is a the shortened command of `mulle-bootstrap bootstrap`, which in turn executes: #### mulle-bootstrap fetch Downloads all required libraries into a `.repos` folder. #### mulle-bootstrap build Compiles the required libraries contained in the `.repos` folder into `./dependencies`. It compiles each project once for Release and once for Debug (and given a file `.bootstrap/sdks` multiplied by the number of sdks needed) ## Commands for a project maintainer #### mulle-bootstrap init This is the first action. It sets up a `.bootstrap` folder in your project directory root (e.g. alongside .git). At this point you should edit `.bootstrap/repositories` to add git projects dependencies. For each repository add a line like ```console ``` In the file `.bootstrap/brews` you can specify homebrew projects that need to be installed. These will be installed into `/usr/local` as usual though. ```console zlib openssl ``` #### mulle-bootstrap setup-xcode Prepares a Xcode project to use the libraries that are compiled into the `./dependencies` folder. You still need to add the libraries to your targets though. #### mulle-bootstrap tag Tag all fetched repositories.