Correct cmake variable for install prefix is "CMAKE_INSTALL_PREFIX", not "CMAKE_PREFIX_PATH".

CMAKE_PREFIX_PATH is for searching for other programs, not for the place
to install this one.  Based on acprep's --help, I think the intention was
to use CMAKE_INSTALL_PREFIX here.
FAQ entry on how build your own Boost and/or CMake for use with Ledger.

Debian squeeze, which is currently the stable distribution at the time of
this commit, has both a Boost and a CMake that is too old for Ledger.
This FAQ entry explains how to build your own Boost and CMake for use with
Ledger, and the exact commands to type to build and install each, and then
configure, build and install Ledger against those new versions.
Merge pull request #78 from bkuhn/README-FAQ-on-building-own-boost-cmake

FAQ entry on how build your own Boost and/or CMake for use with Ledger.
Merge pull request #77 from bkuhn/acprep-wrong-cmake-install-prefix

Correct cmake variable for install prefix is "CMAKE_INSTALL_PREFIX", not "CMAKE_PREFIX_PATH".
doc/ledger3.info should be ignored.

doc/ledger3.info was probably missing from the .gitignore because
ledger3.info isn't build automatically yet, but might as well add it to
.gitignore for those who are building it by hand at the moment.
Merge pull request #79 from bkuhn/gitignore-ledger3-info

doc/ledger3.info should be ignored.
Merge pull request #80 from bkuhn/contrib-non-profit-annual-audit-reports

Contrib: non-profit annual audit reports
Document "Data File Parsing Information" format strings.

Based on my reading of src/format.cc and inspection of output on some test
data, I believe this is adequate documentation for these format strings.
Fixed typo: removed extra @tab.
Merge pull request #81 from bkuhn/doc-small-improvements

Document "Data File Parsing Information" format strings.
Created Fixated prices node.

There was a Fixated prices section, but no Fixated prices node.
This of course required an update of nodes and menus throughout chapter.
Documentation for the fixed directive.

Based on conversation with johnw on IRC, I believe this text properly
documents the intended feature of the fixed directive.
Make reference and link to Bug Report #789 in fixed directive documentation.

Due to weirdness that's currently true with the existing next branch of
ledger, I believe it's important to tell users in the documentation that
there are some discrepancies in the 'fixed' directive behavior.

The documentation from my previous commit is written to explain what
'fixed' *should* do; adding the bug report link here is a placeholder to
tell users that it may not do what they think it does.

Obviously, if someone closes #789, they should remove this paragraph added
herein.  But, if the bug report is closed, but the documentation lags
behind, the worst that happens is some users have to click through to see
the bug is closed.
Merge pull request #82 from bkuhn/doc-fixed-directive

Documentation for the fixed directive.
Changes for CMake
Changes to support using homebrew and ninja
Don't use the ninja build command by default
Added -N/--ninja option to acprep
Running totals on a report including automated transactions are computed with extra precision,
resulting in balances differing from the sum of their components.
Rounding is different for balance totals vs. postings when using posting costs.

test/regress/CAE63F5C-b.test and test/regress/CAE63F5C-c.test should both
pass, but test/regress/CAE63F5C-c.test does not, because the total line of
$6.46 is rounded wrong; it should be $6.45.

There seems to be different rounding occurring for totals vs. postings.

This seems to be related to Bug #492.