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

README.md: Minor rewording

Browse source 
Signed-off-by: Jan Lindemann <jan@janware.com>
This commit is contained in:
Jan Lindemann 2019-10-28 12:20:48 +00:00
commit 5fbfde4930
1 changed files with 14 additions and 14 deletions
Download patch file Download diff file Expand all files Collapse all files

28
README.md
View file

@ -15,25 +15,25 @@ makefile snippets from your own projects' makefiles, like so:
where `JWBDIR` needs to point to JW-Build's installation directory. In this where `JWBDIR` needs to point to JW-Build's installation directory. In this
example, the snippet `cpp.mk` would by default take all C++ files it finds in example, the snippet `cpp.mk` would by default take all C++ files it finds in
the directory from where its included, compile them, and and add them to a 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 shared project 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 project 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 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, its tarball is about 200K. It's small enough to be shipped JW-Build is small, its tarball is about 200K. It's small enough to be shipped
with your project, if you choose to do so. And it's small enough to be with the source code of your project, if you choose to do so. And it's small
self-documenting. Well, okay, somewhat self-documenting. You have to know GNU enough to be self-documenting. Well, okay, somewhat self-documenting. You have
Makefile syntax to understand what it does, and dig into its somtimes arcane to know GNU Makefile syntax to understand what it does, and dig into its
code, ideally with a working example. You can install it with your somtimes arcane code, ideally with a working example. You can install it with
distribution's package manager, or you can keep it within your code versioning your distribution's package manager, or you can keep it within your code
system, alongside your own code. It's also designed to be the lightest possible versioning system, alongside your own code. It's also designed to be the
touch on any given source code package, in terms of code needed to add to a lightest possible touch on any given source code package, in terms of code you
given package that should be built with it, and also in terms of needed need to add to a given package that should be built with it, and also in terms
prerequisite software packages. This way, it's easily added - and it's also of software packages needed to be installed on your machine. This way, it's
easy to replace, should you choose to do so at some point. You will then have easily added - and it's also easy to replace, should you choose to do so at
all your settings like file system path definitions and compiler flags in some point. You will then have all your settings like file system path
well-defined places already. 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