gnustep/tools-make
0
0
Fork 0
mirror of https://github.com/gnustep/tools-make.git synced 2025-04-23 22:33:28 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

Tidied up release notes on parallel building of tools

Browse source 
git-svn-id: svn+ssh://svn.gna.org/svn/gnustep/tools/make/trunk@29546 72102866-910b-0410-8b05-ffd578937521
This commit is contained in:
Nicola Pero 2010-02-11 12:46:14 +00:00
parent 4a6bd22750
commit 7d96c65131
2 changed files with 24 additions and 20 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

22
Documentation/releasenotes.texi
View file

@ -21,16 +21,18 @@ GNUmakefiles should be unaffected because rarely people rely on the
order in which tools are built. If your GNUmakefile does depend on
the order in which tools are built, you have a few options. The
preferred option is to identify the code or steps that need to be
executed before some of the tools are built (for example, you may be
generating a customized header in before-ToolA-all::, but the header
is actually used when building not only ToolA, but ToolB as well, so
the build breaks if ToolB is not built after ToolA) and put them into
a before-all:: rule, which is guaranteed to be executed before
everything else. In this way your serialized code is executed first,
and the build can continue in a complete parallel fashion afterwards.
If all else fails, you can still disable parallel building in your
GNUmakefile by adding GNUSTEP_MAKE_PARALLEL_BUILDING=no just after
including common.make.
executed before some of the tools are built and put them into a
before-all:: rule, which is guaranteed to be executed before anything
else. In this way your serialized code is executed first, and the
build can continue in a completely parallel fashion afterwards.
If you just want to force a specific tool (say, ToolA) to be
built before the others, you can always add a 'before-all:: ToolA'
rule which will make sure ToolA is built before the other ones.
If you want to complete disable parallel building, you can add
GNUSTEP_MAKE_PARALLEL_BUILDING=no just after including common.make, or
pass it on the command-line.
@item support for having source files in subdirectories
Starting with version 2.2.1, it is possible to put source files in

22
RELEASENOTES
View file

@ -23,16 +23,18 @@ using a newer version of the make system.
are built. If your GNUmakefile does depend on the order in which
tools are built, you have a few options. The preferred option is
to identify the code or steps that need to be executed before some
of the tools are built (for example, you may be generating a
customized header in before-ToolA-all::, but the header is
actually used when building not only ToolA, but ToolB as well, so
the build breaks if ToolB is not built after ToolA) and put them
into a before-all:: rule, which is guaranteed to be executed before
everything else. In this way your serialized code is executed
first, and the build can continue in a complete parallel fashion
afterwards. If all else fails, you can still disable parallel
building in your GNUmakefile by adding
GNUSTEP_MAKE_PARALLEL_BUILDING=no just after including common.make.
of the tools are built and put them into a before-all:: rule,
which is guaranteed to be executed before anything else. In this
way your serialized code is executed first, and the build can
continue in a completely parallel fashion afterwards.
If you just want to force a specific tool (say, ToolA) to be built
before the others, you can always add a 'before-all:: ToolA' rule
which will make sure ToolA is built before the other ones.
If you want to complete disable parallel building, you can add
GNUSTEP_MAKE_PARALLEL_BUILDING=no just after including
common.make, or pass it on the command-line.
`support for having source files in subdirectories'
Starting with version 2.2.1, it is possible to put source files in