This effectively replaces the use of GNUCASH_BUILD_DATE with GNUCASH_SCM_REV_DATE.
The latter is extracted from the current commit if building from some kind of vcs
(currently only works correctly for svn and git). The info extracted while building
from vcs is then also added to the dist tarball so it's available when building
from tarball as well (via the file libgnucash/core-utils/gnc-vcs-info.h).
The same date is also used to set the date in gnucash' man page document.
A practical detail: I have changed the substitution variables in the man page template
from @- -@ to ${} so we could leverage CONFIGURE_FILE in cmake. The necessary
related adjustments have also been made to Makefile.am's substitution rules.
While I myself asked for it to be retained a couple of years back
I now believe it really makes no sense to keep on carrying
a completely outdated rpm spec file around. This should not
be part of the source and properly up to date and maintained
rpm spec files can be found in each rpm based distro that ships
gnucash.
It is split into
- /libgnucash (for the non-gui bits)
- /gnucash (for the gui)
- /common (misc source files used by both)
- /bindings (currently only holds python bindings)
This is the first step in restructuring the code. It will need much
more fine tuning later on.
This is half of the work to align the cmake and autotools generated dist tarballs.
What's missing in the cmake dist tarball on my system are all the files generated
or installed by running autogen.sh. I can't test this because cmake can't run
my version of automake (1.15), or at least our CMake configuration prevents this from happening.
Replace the autogen-sh time configuration which doesn't really work
correctly by making a local interpreter which links whichever library
pkg-config finds.
Also makes Guile-2.0 the default by looking for it first.
for guile 1.8 builds. However if we don't have guile 2.0.10 then don't
allow "make dist" to run. This also means we wont patch the guile
files unless we find swig 2.0.10.
git-svn-id: svn+ssh://svn.gnucash.org/repo/gnucash/trunk@23748 57a11ea4-9604-0410-9ed3-97b8803252fd
These are set automatically via AC_SUBST in configure.ac
git-svn-id: svn+ssh://svn.gnucash.org/repo/gnucash/trunk@23401 57a11ea4-9604-0410-9ed3-97b8803252fd
This code will determine the repo type (git or svn) and use the
appropriate command to generate the ChangeLog file accordingly.
git-svn-id: svn+ssh://svn.gnucash.org/repo/gnucash/trunk@22982 57a11ea4-9604-0410-9ed3-97b8803252fd
They need to be in the skip file to mollify newer intltool versions,
but still need to be handled by guile-strings.c for older versions of
intltool.
git-svn-id: svn+ssh://svn.gnucash.org/repo/gnucash/trunk@22836 57a11ea4-9604-0410-9ed3-97b8803252fd
scm is the modern term. vcs is rather used to refer to archaic systems
such as cvs and older. I wish I remembered this before my previous
commit. Oh well...
git-svn-id: svn+ssh://svn.gnucash.org/repo/gnucash/trunk@22476 57a11ea4-9604-0410-9ed3-97b8803252fd
The code actually has provisions for svn, svk, git and bzr. Only svn and
git are actively used by the core developers though.
This involves changing
- filenames that contained svn while meant for multiple vcs's
- variable and macro names that are relevant for multiple vcs's
- the various locations where the vcs revision info is displayed
to the user, to mention the actual vcs used instead of standard "svn"
While at the last item, I also changed the text printed when gnucash is
called with the --version parameter, to reuse the translatable string
that is also used for the about dialog. This saves us one string to
translate.
git-svn-id: svn+ssh://svn.gnucash.org/repo/gnucash/trunk@22475 57a11ea4-9604-0410-9ed3-97b8803252fd
This was discussed in more detail here:
http://lists.gnucash.org/pipermail/gnucash-devel/2011-June/032066.html
This might change the default location where the documentation is installed to.
git-svn-id: svn+ssh://svn.gnucash.org/repo/gnucash/trunk@20736 57a11ea4-9604-0410-9ed3-97b8803252fd
The "astyle" indent tool unfortunately behaves significantly different
in its different versions (1.22, 1.23, 1.24) even with identical
options. That is, the basic indentation is the same, but in a large
project such as ours, there are just too many special cases which
astyle doesn't get identical due to its bugfixes and new features.
Hence, please use the result of this target with great care, and
if in doubt, just use it for your own amusement but don't commit the
resulting changes. Thanks!
git-svn-id: svn+ssh://svn.gnucash.org/repo/gnucash/trunk@18760 57a11ea4-9604-0410-9ed3-97b8803252fd
- move the gnucash-desktop.in.in from POTFILES.skip to POTFILES.ignore
- only try to make-gnucash-potfiles if $(srcdir) is writable
BP
git-svn-id: svn+ssh://svn.gnucash.org/repo/gnucash/trunk@16868 57a11ea4-9604-0410-9ed3-97b8803252fd
Also, modify build rules so that POTFILES.in is no longer generated
automatically during make dist, but only on explicit "make pot", because
the build rule will now modify POTFILES.in in the srcdir and no longer
in the builddir.
BP
git-svn-id: svn+ssh://svn.gnucash.org/repo/gnucash/trunk@16864 57a11ea4-9604-0410-9ed3-97b8803252fd
