4 commits
| Author | SHA1 | Date | |
|---|---|---|---|
| 7f85a5f2d6 | |||
| df9a4e6a40 | |||
| bc883deed4 | |||
| df4a295d79 |
| Author | SHA1 | Message | Date | |
|---|---|---|---|---|
| 7f85a5f2d6 |
projects+project.mk: Add file
Multiple variables are redundantly defined both for a project and for the multiple-projects toplevel directory. Add a place to maintain them centrally, and add PGIT_SH as a first variable. Signed-off-by: Jan Lindemann <jan@janware.com> |
|||
| df9a4e6a40 |
projects-dir-*.mk: Re-add files necessary for building projects directory
Re-add everything necessary for recursively building all repos in a directory, e.g. as a build controlled by janware.com/Makefile or any other installation. This adds 489 lines of code which can (and should) be massively reduced, notably removing code supporting CVS. Signed-off-by: Jan Lindemann <jan@janware.com> |
|||
| bc883deed4 |
Everywhere: Remove everything non-essential for "make clean all"
This commit removes everything not strictly necessary for running "make clean all" inside jw-build. packaging jw-devtest. This cuts the repo down from 24077 to 4725 lines of code. The idea is to 1) Further remove bloat from the remaining bits 2) Re-add what's necessary to build and package other essential repos. The decision should be based on whether or not jw-build can also be useful in a non-janware context. Signed-off-by: Jan Lindemann <jan@janware.com> |
|||
| df4a295d79 |
Add git-projects-dir-[include|minimal].mk
In the attempt to move both jw-build and the janware toplevel Makefile from CVS to Git, add two new makefile snippets to make/*.mk: - projects-dir-minimal.mk A new toplevel-Makefile for building all projects in one go. It
should be suitable to be downloaded from janware.com/Makefile and
then be used to bootstrap all repos hosted on janware.com, that a
user has access to, just like the current toplevel Makefile is. It is as small as possible: Little code means few assumptions on
what the world outside of it looks like, notably jw-build. This
is desirable, because it lives outside of version control, albeit
for a short while, and as long as it does, there's no mechanism
in place to keep it current. That said, on first use, it replaces itself with a symbolic link
into jw-build and is then version controlled with jw-build. - projects-dir-include.mk This is essentially the existing projects-dir.mk /
toplevel-Makefile, which it includes. It's meant as a place for
adaptations to the next-generation implementation. This might
prove handy to have while both implementations coexist during the
transition phase. Signed-off-by: Jan Lindemann <jan@janware.com> |
