[Gnucash-changes] r11624 - gnucash/branches/cashutil/cashutil - update for branch usage

[Neil Williams]

Author: codehelp
Date: 2005-10-31 19:09:13 -0500 (Mon, 31 Oct 2005)
New Revision: 11624

Modified:
   gnucash/branches/cashutil/cashutil/HACKING
   gnucash/branches/cashutil/cashutil/NEWS
   gnucash/branches/cashutil/cashutil/README
Log:
update for branch usage

Modified: gnucash/branches/cashutil/cashutil/HACKING
===================================================================
--- gnucash/branches/cashutil/cashutil/HACKING	2005-10-31 23:47:32 UTC (rev 11623)
+++ gnucash/branches/cashutil/cashutil/HACKING	2005-11-01 00:09:13 UTC (rev 11624)
@@ -1,43 +1,29 @@
 Hacking on CashUtil
 ===================
 
-Make and make install:
-=====================
-
-CashUtil relies on installed versions of the QOF, libcashobjects and libgnc-backend-file libraries. 
-If you change any source files for these libraries, 
-ensure you run 'make install' rather than just 'make' 
-or your changes will have no effect. There is no support 
-for loading local or 'test' versions of the libraries. 
-You can usually run cashutil against a freshly installed set of QOF libraries without recompiling cashutil, depending on 
-the level of changes in QOF.
-
 Debug output:
 =============
 
-#define PRINT_DEBUG is set to 0 in src/cashutil.c prior to packaging. Set to non-zero to print lots of debug information.
+Pass the --debug option to create a log file in /tmp/cashutil.trace
 
 IDEs:
 ====
 
-KDevelop has some problems with CashUtil build frameworks when you select the debug build. It tends to continually 
-complain about lack of configure.in - it seems to simply 
-ignore configure.ac and autogen.sh and complains that no Makefiles exist when the files are fine.
+KDevelop has some problems with CashUtil build frameworks when you 
+select the debug build. It tends to continually complain about lack 
+of configure.in - it seems to simply ignore configure.ac and 
+autogen.sh and complains that no Makefiles exist when the files are fine.
 
-Do NOT attempt to run configure (with or without arguments) on the CVS code from within KDevelop - it will completely 
-break your Makefiles and you'll need to run ./autogen.sh with 
-the usual parameters all over again (plus make and then make 
-install).
+Do NOT attempt to run configure (with or without arguments) on the CVS/SVN 
+code from within KDevelop - it will completely break your Makefiles 
+and you'll need to run ./autogen.sh with the usual parameters all over 
+again (plus make and then make install).
 
-Instead, ignore the debug build and select 'default', entering the ./autogen.sh options for --with-qof and 
---prefix as normal.
-
---with-qof=<path to qof> --prefix=<prefix for install>
-
 Check your distribution for the updated KDevelop3 which does support code folding.
 
-CVS support seemed fragile - if KDevelop or Cervisia do not connect to existing repositories, try loading cervisia with a 
-known local working copy directory on the command line:
+CVS support in KDevelop seemed fragile - if KDevelop or Cervisia do not 
+connect to existing repositories, try loading cervisia with a known local 
+working copy directory on the command line:
 $ cervisia <path to checked out project>
 
 If KDevelop also complains about not setting a local working 
@@ -53,63 +39,3 @@
 CVS handling and displays line numbers in the edit window 
 without any special configuration or problems.
 
-Synchronising CashUtil CVS with QOF and GnuCash.
-===============================================
-
-CVS is fine for single trees and branches but it can be hard 
-to keep two or more projects in sync when they use the same 
-files and being developed in both trees. This kind of
-inter-operability between CVS trees tends to become an 
-intensely manual chore.
-
-CashUtil CVS includes a set of MANIFEST files that are intended to help with this problem by using a feature of the 
-makepatch package. By specifying customised MANIFEST files to
-makepatch, only the files mentioned in the manifest are 
-compared. This makes things much easier when dealing with 
-trees that have common files but where those files are not 
-restricted to dedicated directories. e.g. in GnuCash, files 
-in src/engine are a mixture of files from QOF and files from 
-src/objects in CashUtil. By using a manifest file, makepatch 
-can be instructed to only compare the files that are listed 
-in the manifest. Default behaviour is to assume that all
-files in the directory are part of the package (subject to 
-build/CVS exclusion patterns). Making a patch for such a 
-directory would include the missing files in the patch in 
-their entirety and  applying such a patch with applypatch 
-would create the unwanted files in the other tree! Naturally,
-the MANIFEST files need to be kept updated.
-
-Example: To fold changes from GnuCash into CashUtil.
-makepatch -description "cashutil sync" \
--manifest OBJ_MANIFEST_ENG \
-cashutil/src/objects/ gnucash-gnome2/src/engine/ \
-> ../patches/cashutil_g2_sync.patch
-
-#(Reverse the pathnames to fold changes from CashUtil into GnuCash - old files first).
-# gnucash-gnome2/src/engine/ cashutil/src/objects/ \
-
-Output:
-Manifest OBJ_MANIFEST_ENG for src/objects/ contains 54 files.
-Manifest OBJ_MANIFEST_ENG for /opt/working/gnucash-gnome2/src/engine/ contains 54 files.
-Processing the filelists ...
-Collecting patches ...
-  10 files need to be patched.
-
-Paths to use with each MANIFEST
--------------------------------
-
--manifest OBJ_MANIFEST_ENG \
-cashutil/src/objects/ gnucash-gnome2/src/engine/ \
-
--manifest OBJ_MANIFEST_BUS \
-cashutil/src/objects/ gnucash-gnome2/src/business/business-core/ \
-
--manifest BACK_MANIFEST_ENG \
-cashutil/src/backend/ gnucash-gnome2/src/backend/file \
-
--manifest BACK_MANIFEST_BUS \
-cashutil/src/backend/ gnucash-gnome2/src/business/business-core/file/ \
-
-See the makepatch man page for information on generating new manifest files.
-(e.g. QOF_MANIFEST_ENG for qof/qof/ gnucash-gnome2/src/engine/ )
-

Modified: gnucash/branches/cashutil/cashutil/NEWS
===================================================================
--- gnucash/branches/cashutil/cashutil/NEWS	2005-10-31 23:47:32 UTC (rev 11623)
+++ gnucash/branches/cashutil/cashutil/NEWS	2005-11-01 00:09:13 UTC (rev 11624)
@@ -1,11 +1,9 @@
 
-This is very much pre-alpha - it compiles and certain
-basic functions do work but the objects and the interactive
-shell are not complete.
+This is very much pre-alpha - it compiles in it's original
+(out-of-tree) form and certain basic functions do work but 
+the objects and the interactive shell are not complete.
 
 Use the test-cash routine for examples of how each shell function
 can be built and to produce sample content.
 
-The test routine still fails and this is likely to continue until
-commodites can be harnessed.
 

Modified: gnucash/branches/cashutil/cashutil/README
===================================================================
--- gnucash/branches/cashutil/cashutil/README	2005-10-31 23:47:32 UTC (rev 11623)
+++ gnucash/branches/cashutil/cashutil/README	2005-11-01 00:09:13 UTC (rev 11624)
@@ -28,14 +28,9 @@
     backend to read existing user data files as well as
     exported data.
  
-CashUtil needs QOF v0.6.0 (currently available at v0.6.0-pre1 
-and via CVS). For CVS, build QOF first and pass the location 
-to CashUtil using the --with-qof option to ./autogen.sh
+CashUtil needs QOF v0.6.0 (currently available at v0.6.0  
+and via CVS) - it can use the gnucash internal libqof.
 
-./autogen.sh --with-qof=<QOF path> --prefix=<cashutil test install path>
-
-If installed, omit the --with-qof option.
-
 SUPPORT
 -------