janware/jw-pkg
1
mirror of ssh://git.janware.com/srv/git/janware/proj/jw-pkg synced 2026-01-15 12:03:31 +01:00
Code Activity

README.md: Refine notes about its size

Browse source 
Signed-off-by: Jan Lindemann <jan@janware.com>
This commit is contained in:
Jan Lindemann 2019-07-15 07:30:35 +00:00
commit 8e2161dd5d
1 changed files with 14 additions and 13 deletions
Download patch file Download diff file Expand all files Collapse all files

27
README.md
View file

@ -18,21 +18,22 @@ the directory from where its included, compile them, and and add them to a
central shared library. It would also take all header files and copy them to a central shared library. It would also take all header files and copy them to a
central include directory. `js.mk` would by default minify all JavaSript it central include directory. `js.mk` would by default minify all JavaSript it
finds, `java.mk` jar up .java files into classes and jar-files, and so on. finds, `java.mk` jar up .java files into classes and jar-files, and so on.
JW-Build also handles installation and packaging of all of these files, to JW-Build also handles installation and packaging of these files, to
customizable locations with standardish defaults. customizable locations with standardish defaults.
JW-Build is small. It's small enough to be self-documenting. Well, okay, JW-Build is small, its tarball is about 200K. It's small enough to be shipped
somewhat self-documenting. It better be, given its lack of documentation. You with your project, if you choose to do so. And it's small enough to be
have to know GNU Makefile syntax to understand what it does, and dig into its self-documenting. Well, okay, somewhat self-documenting. You have to know GNU
somtimes arcane code, ideally with a working example. You can install it with Makefile syntax to understand what it does, and dig into its somtimes arcane
your distribution's package manager, or you can keep it within your code code, ideally with a working example. You can install it with your
versioning system, alongside your own code. It's also designed to be the distribution's package manager, or you can keep it within your code versioning
lightest possible touch on any given source code package, in terms of code you system, alongside your own code. It's also designed to be the lightest possible
need to add to a package you want to build with it, and also in terms of needed touch on any given source code package, in terms of code needed to add to a
prerequisite software packages. This way, it's easily introduced - and it's given package that should be built with it, and also in terms of needed
also easy to get rid of, should you choose to do so at some point in time. You prerequisite software packages. This way, it's easily added - and it's also
will then have all your settings like file system path definitions and compiler easy to replace, should you choose to do so at some point. You will then have
flags in well-defined places already. all your settings like file system path definitions and compiler flags in
well-defined places already.
JW-Build runs a recursive make, so, with a few exceptions such as submodules, JW-Build runs a recursive make, so, with a few exceptions such as submodules,
you will need a makefile in every directory with source code. Most, if not all you will need a makefile in every directory with source code. Most, if not all