IntenseFinance/gnucash
3
0
Fork 0
mirror of https://github.com/Gnucash/gnucash.git synced 2025-02-25 18:55:30 -06:00
Code Issues Packages Projects Releases Wiki Activity

Remove automatic call to ./configure from ./autogen.sh.

Browse Source 
2005-11-09  Christian Stimming  <stimming@tuhh.de>

        * macros/autogen.sh: Remove the automatic call to ./configure
        * from
        autogen.sh; instead, only print a reminder that from now on,
        ./configure has to be called separately.



git-svn-id: svn+ssh://svn.gnucash.org/repo/gnucash/trunk@11890 57a11ea4-9604-0410-9ed3-97b8803252fd
This commit is contained in:
Christian Stimming 2005-11-09 20:51:03 +00:00
parent abadcede4d
commit 58f361a0c5
4 changed files with 35 additions and 29 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
ChangeLog
View File

@ -1,5 +1,9 @@
2005-11-09 Christian Stimming <stimming@tuhh.de> 2005-11-09 Christian Stimming <stimming@tuhh.de>
* macros/autogen.sh: Remove the automatic call to ./configure from
autogen.sh; instead, only print a reminder that from now on,
./configure has to be called separately.
* po/cs.po, po/glossary/pt_BR.po, po/ca.po, po/tr.po: Merge * po/cs.po, po/glossary/pt_BR.po, po/ca.po, po/tr.po: Merge
language files from branches/1.8 so that all languages are now language files from branches/1.8 so that all languages are now
available in HEAD. available in HEAD.

19
README.svn
View File

@ -4,18 +4,25 @@ Miguel de Icaza who adapted them from guidelines written by
Owen Taylor. Owen Taylor.
+ In order to build GnuCash from SVN, you need to run the autogen.sh + In order to build GnuCash from SVN, you need to run the autogen.sh
command to generate and execute a configure script. When building command to generate a configure script:
from CVS you should ALWAYS pass your configure options directly to
autogen.sh. For example:
./autogen.sh --enable-ofx --enable-opt-style-install --prefix=/opt/gnucash ./autogen.sh
Autogen will automatically generate the configure script and then After the ./configure script has been created, you need to run it
run it. After that, configure can also be run by hand. with all the usual options. See ./configure --help for a
reminder. For example:
./configure --enable-ofx --enable-opt-style-install --prefix=/opt/gnucash
If in doubt, you can run autogen.sh, run ./configure --help, If in doubt, you can run autogen.sh, run ./configure --help,
then re-run ./configure with your options. then re-run ./configure with your options.
(Note: Previously, autogen.sh automatically called configure as
well. This behaviour was dropped in favor of two separate calls
because: Autogen should be an additional step taken by only by
developers using SVN sources. Configure is a step taken by
everyone compiling the sources, be it from svn or a tarball.)
+ Some versions of gettextize don't deal well with re-running themselves. + Some versions of gettextize don't deal well with re-running themselves.
You will see this as an error like: You will see this as an error like:

33
doc/TRANSLATION_HOWTO
View File

@ -48,7 +48,10 @@ The GNU Translation Project is another way to submit translations:
http://www.iro.umontreal.ca/contrib/po/HTML/ http://www.iro.umontreal.ca/contrib/po/HTML/
============================================================================== ==============================================================================
2) Get the source from CVS 2) Get the source from CVS/SVN
FIXME: This section is now outdated since the source is now in SVN
instead of CVS. Please check the website.
The first thing to do is to download the latest STABLE branch of gnucash The first thing to do is to download the latest STABLE branch of gnucash
from CVS and get it to compile. Do not use the HEAD branch, since the text from CVS and get it to compile. Do not use the HEAD branch, since the text
@ -117,14 +120,16 @@ correctly with all the development packages you need. It is a good idea
to actually run gnucash with your new translations because it is quite to actually run gnucash with your new translations because it is quite
helpful to see the phrases in the context of the running program. helpful to see the phrases in the context of the running program.
Enter the gnucash directory and run the autogen.sh script. There are many Enter the gnucash directory. Run the autogen.sh script. Then run the
options available when compiling gnucash, see the README.cvs file for more ./configure script, as described in README.svn. There are many options
information on the options. For now, we will just enable debugging and available when compiling gnucash. For now, we will just enable
change the default prefix because these two changes will be handly later debugging and change the default prefix because these two changes will
for tracking down problems and installing multiple versions. be handly later for tracking down problems and installing multiple
versions.
cd gnucash cd gnucash
./autogen.sh --enable-debug --prefix=/opt/gnucash-1.8 ./autogen.sh
./configure --enable-debug --prefix=/opt/gnucash-1.8
If autogen complains about missing development packages, find them on your If autogen complains about missing development packages, find them on your
favorite OS distribution, install it, and try to re-run the autogen command. favorite OS distribution, install it, and try to re-run the autogen command.
@ -138,12 +143,6 @@ Next, compile gnucash:
make make
Note: when you are configuring and building gnucash, do *not* run the
configure script, aclocal, autoconf, or any other programs. EVEN IF THE
AUTOGEN OUTPUT SUGGESTS THAT THEY DO. This is important, and has caused a
lot of confusion. Unfortunately the auto tools complain and cause bogus
warnings.
To install (assuming "make" completed without any problems) you must be To install (assuming "make" completed without any problems) you must be
root. root.
@ -153,7 +152,8 @@ make install
To compile the documentation, enter the gnucash-doc directory and go To compile the documentation, enter the gnucash-doc directory and go
through the same process: through the same process:
./autogen.sh --prefix=/opt/gnucash-1.8 ./autogen.sh
./configure --prefix=/opt/gnucash-1.8
make make
su - su -
make install make install
@ -310,7 +310,7 @@ that there are no unclosed quotes, etc). To do this, use the msgfmt program
This will report any errors in your .po file if it finds them. This will report any errors in your .po file if it finds them.
If you want to see your translations within a running version of gnucash, If you want to see your translations within a running version of gnucash,
simply place your .po file in you CVS copy of the gnucash source code (which simply place your .po file in you SVN copy of the gnucash source code (which
you have previously installed) and from within the po/ directory type (you you have previously installed) and from within the po/ directory type (you
may nee to be root to do this): may nee to be root to do this):
@ -340,7 +340,7 @@ autoheader: /usr/bin/autom4te failed with exit status: 1
**Error**: autoheader failed. **Error**: autoheader failed.
Reload the configure.in script: Reload the configure.in script:
cvs up -C configure.in svn revert configure.in
--------------------------------- ---------------------------------
If you see any "Gtk-CRITICAL" messages while running gnucash, it is probably If you see any "Gtk-CRITICAL" messages while running gnucash, it is probably
@ -399,6 +399,7 @@ First, you must *have* the gnucash-doc package installed:
1) Checkout the documentation 1) Checkout the documentation
cvs -z3 -d :pserver:cvs@cvs.gnucash.org:/home/cvs/cvsroot checkout \ cvs -z3 -d :pserver:cvs@cvs.gnucash.org:/home/cvs/cvsroot checkout \
gnucash-docs gnucash-docs
FIXME: change the cvs command to svn here
2) Create a new directory (if it doesn't already exist) in guide/<locale> 2) Create a new directory (if it doesn't already exist) in guide/<locale>
where <locale> is something like es, en_GB, or pt_PT. where <locale> is something like es, en_GB, or pt_PT.
3) Copy the files from guide/C into this directory. 3) Copy the files from guide/C into this directory.

8
macros/autogen.sh
View File

@ -257,10 +257,4 @@ done
conf_flags="--enable-error-on-warning --enable-compile-warnings" # --enable-iso-c conf_flags="--enable-error-on-warning --enable-compile-warnings" # --enable-iso-c
if test x$NOCONFIGURE = x; then echo You must now run $srcdir/configure $conf_flags "$@" ...
echo Running $srcdir/configure $conf_flags "$@" ...
$srcdir/configure $conf_flags "$@" \
&& echo Now type \`make\' to compile $PKG_NAME || exit 1
else
echo Skipping configure process.
fi