+ B\bB\bB\bBu\bu\bu\bui\bi\bi\bil\bl\bl\bld\bd\bd\bdi\bi\bi\bin\bn\bn\bng\bg\bg\bg f\bf\bf\bfo\bo\bo\bor\br\br\br m\bm\bm\bmu\bu\bu\bul\bl\bl\blt\bt\bt\bti\bi\bi\bip\bp\bp\bpl\bl\bl\ble\be\be\be h\bh\bh\bho\bo\bo\bos\bs\bs\bst\bt\bt\bts\bs\bs\bs
+
+ LilyPond does not follow the GNU standards when it comes
+ to configuring and making Makefiles. In LilyPond, _\bm_\ba_\bk_\be
+ generates _\ba_\bl_\bl output in output directories (called _\bo_\bu_\bt_\b/,
+ by default). You can have multiple compiles from the same
+ source-tree, by overriding the setting for the output
+ directory.
+
+ Example: on my system, I do debugging and lots compiling.
+ For this I use the configuration as follows:
+
+ configure --prefix=~ --enable-debugging --enable-printing --enable-checking
+ make all
+
+ and I want to do profiling. For that I use
+
+ configure --prefix=~ --enable-debugging --disable-printing\
+ --disable-checking --enable-profiling --enable-optimise\
+ --enable-out-dir=out-profile
+
+ make OUTDIR_NAME=out-profile all
+
+ These two commands build two entirely separate versions of
+ LilyPond. In Real Life, you would probably also want to
+ have two different prefixes. On my machine this is no
+ problem; I never do make install. My prefix dirs are
+ linked back to my source directory.
+