Next: , Previous: , Up: Top   [Contents]


7 Make targets

The following make targets are available in ~/.emacs.d/Makefile. To use them you have to be in ~/.emacs.d in a shell.

Command: make help

This target prints information about the following targets.

Command: make build

This target builds all drones.

It also builds init.el and USER-REAL-LOGIN-NAME.el, if that exists. Also see make build-init below.

Command: make quick

This target builds most drones. Excluded are all drones for which the Git variable submodule.DRONE.build-step is set, assuming that those are the drones that take longer to build.

It also builds init.el and USER-REAL-LOGIN-NAME.el, if that exists. Also see make build-init below.

Command: make lib/DRONE

This target builds the drone named DRONE.

Command: make build-init

This target builds init.el and USER-REAL-LOGIN-NAME.el, if that exists.

If you publish your ~/.emacs.d repository but would like to keep some settings private, then you can do so by putting these in a file ~/.emacs.d/FILE-NAME.el. If FILE-NAME matches the value of the variable user-real-login-name, then the init.el of the emacs.g collective automatically loads it. The downside of this approach is that you will have to somehow synchronize that file between your machines without checking it into Git.

Command: make bootstrap

This target attempts to bootstrap the drones. To do so it runs git submodule init, borg.sh (which see), and make build.

If an error occurs during the borg.sh phase, then you can just run that command again to process the remaining drones. The drone that have already been bootstrapped or that have previously failed will be skipped. If a drone cannot be cloned from any of the known remotes, then you should temporarily remove it using git submodule deinit lib/DRONE. When done with borg.sh also manually run make build again.


Next: , Previous: , Up: Top   [Contents]