name mode size
.bootstrap 040000
bin 040000
test 040000
.gitignore 100644 62B 100644 5.72kB 100644 381B
LICENSE 100644 1.54kB
Makefile 100644 677B 100644 3.77kB 100644 5.56kB 100755 1.49kB
mulle-bootstrap 100755 4.84kB 100755 32.41kB 100644 2.64kB 100755 19.71kB 100644 8.1kB 100644 2.84kB 100755 5.4kB 100644 3.65kB 100644 9.99kB 100755 4.64kB 100644 3.69kB 100755 10.43kB
mulle-bootstrap.sublime-project 100644 143B
# mulle-bootstrap, yet another dependency manager for developers * downloads [github]( repositories ("dependents") * can deal with [cmake](, [xcodebuild]( and [configure]( projects * instead of installing headers and libraries to `/usr/local`, mulle-bootstrap installs to `./dependencies` * can tag your repository and all dependents. dependents get a vendor tag * installs brew taps and formulae * installs gems and pips * compiles dependents using the output of previous dependents * written in portable shell script, will run eventually also on Linux ## 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/gits`. ```console cat > .bootstrap/gits ``` Now **mulle-bootstrap** can iterate over them and check them out into a common directory `.repos`. Ok the repository **MulleScion** has a local clone in the parent directory. 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 places the headers and the produced libraries into "./dependencies". Your Xcode project can be optionally massaged by **mulle-bootstrap setup-xcode** to have the "./dependencies" folder in its search paths. ## What a project user needs to do ```console brew tap mulle-kybernetik/software brew install mulle-bootstrap ``` Download a project which is mulle-bootstrap enabled. ```console cd <project> mulle-bootstrap ``` And all dependencies should be recreated as they were on your development machine (if you set it up correctly). `mulle-bootstrap` is a 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) ## What a project maintainer needs to do #### 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/gits` 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 your project and all fetched repositories, with a tag. ## Known limitations * only works for libraries so far * not tested too much