gnucash-on-windows master: Multiple changes pushed
John Ralls
jralls at code.gnucash.org
Tue May 5 18:53:56 EDT 2015
Updated via https://github.com/Gnucash/gnucash-on-windows/commit/e3270224 (commit)
via https://github.com/Gnucash/gnucash-on-windows/commit/e5430701 (commit)
from https://github.com/Gnucash/gnucash-on-windows/commit/8abd7ec1 (commit)
commit e32702240160f44bb0833995a59b7b050d30387f
Author: John Ralls <jralls at ceridwen.us>
Date: Tue May 5 15:53:40 2015 -0700
Reflow paragraphs with lines > 80 characters long.
diff --git a/README b/README
index 3bc2925..e369565 100644
--- a/README
+++ b/README
@@ -79,16 +79,17 @@ Note: if you intend to use the buildserver scripts (see separate directory)
there are some restrictions to the paths you can/should alter.
For more detail please check README.txt in the buildserver directory.
-You are now ready to build gnucash for the first time. The build is fully parameterized.
-That means which versions of libraries and tools to install, where to install them,
-which branch to build and so on can all be defined. If not set explicitly some default
-values will be used. If you're already familiar with the Windows build you may want to
-customize some of these parameters. If not sure - don't. The build should run just fine
-without it.
-
-The default values will all be found in 'defaults.sh'. You can override any of these
-in 'custom.sh'. The boostrap script you ran in step b. already created an initial
-version of this file.
+You are now ready to build gnucash for the first time. The build is
+fully parameterized. That means which versions of libraries and tools
+to install, where to install them, which branch to build and so on can
+all be defined. If not set explicitly some default values will be
+used. If you're already familiar with the Windows build you may want
+to customize some of these parameters. If not sure - don't. The build
+should run just fine without it.
+
+The default values will all be found in 'defaults.sh'. You can
+override any of these in 'custom.sh'. The boostrap script you ran in
+step b. already created an initial version of this file.
d. Open an Msys shell window. You do this by running
c:\gcdev\mingw\msys\1.0\msys.bat
@@ -146,14 +147,19 @@ scripts (2014-05-07).
Known Issues/Things to improve
------------------------------
-* It appears that installing html help on Windows systems more recent than
- Windows XP can fail. It looks like the installer triggers a Windows authorization
- dialog. For some reason this dialog can't be displayed when the installer is started
- from an msys shell.
+
+* It appears that installing html help on Windows systems more recent
+ than Windows XP can fail. It looks like the installer triggers a
+ Windows authorization dialog. For some reason this dialog can't be
+ displayed when the installer is started from an msys shell.
+
The workaround is a bit awkward currently and consists of
- 1. install html help directly by double-clicking it. Remember to install it where
- the gnucash build scripts expect it ! That is c:\gcdev\hh by default.
- 2. Inside your msys shell window enter these commands:
+
+ 1. install html help directly by double-clicking it. Remember to
+ install it where the gnucash build scripts expect it ! That is
+ c:\gcdev\hh by default.
+ 2. Inside your msys shell window enter
+ these commands:
pushd /c/gcdev/hh
_HHCTRL_OCX=$(which hhctrl.ocx || true)
@@ -165,7 +171,8 @@ Known Issues/Things to improve
popd
popd
- 3. You can now rerun install.sh which should get past the html help installation step
+ 3. You can now rerun install.sh which should get past the html help
+ installation step
(Reference: http://lists.gnucash.org/pipermail/gnucash-devel/2014-May/037561.html
and following messages)
@@ -177,8 +184,11 @@ Known Issues/Things to improve
64-bit integers.
To work around this you can add a line in custom.sh:
EXTRA_CFLAGS=" -D__USE_MINGW_ANSI_STDIO"
- The same list message mentioned a couple of additional flags to set but these were
- not explained. For completeness the complete line was:
+
+ The same list message mentioned a couple of additional flags to set
+ but these were not explained. For completeness the complete line
+ was:
+
EXTRA_CFLAGS=" -Wall -Werror -fno-builtin-dgettext -fno-builtin-towupper -fno-builtin-iswlower -ggdb3 -D__USE_MINGW_ANSI_STDIO"
Adjust as you see fit.
@@ -208,7 +218,7 @@ These steps need to be performed:
on your Linux installation.
(It is strongly recommended to choose a prefix different
from your normal compiler tool chain in order to distinguish
- your native vs. cross compiler more easily.)
+ your native vs. cross compiler more easily.)
2. Then run the script create_cross_mingw.sh - it will
download, compile, and install a mingw32 tool chain.
@@ -221,7 +231,7 @@ These steps need to be performed:
4. Call install.sh, which will read the directory settings from
defaults.sh/custom.sh. It should download, compile, and install everything
automatically. Eventually the windows gnucash is installed into
- $GNUCASH_DIR.
+ $GNUCASH_DIR.
5. The content of $GNUCASH_DIR (as well as all the other binary
packages) should then be copied to a windows machine. The paths
commit e5430701af83bf1cf82d21702454c5bb832abc97
Author: John Ralls <jralls at ceridwen.us>
Date: Tue May 5 15:53:12 2015 -0700
Add as a first step to install either Strawberry Perl or ActivePerl.
diff --git a/README b/README
index 71fb0ab..3bc2925 100644
--- a/README
+++ b/README
@@ -51,11 +51,15 @@ The steps
On to building GnuCash now. The scripts have been set up to require as little
manual actions as possible. The following should get you going:
-a. Download bootstrap_win_dev.vbs from the gnucash-on-windows
+a. Download and install either Strawberry Perl
+ (http://strawberryperl.com/) or AcivePerl
+ (http://www.activestate.com/activeperl/downloads).
+
+b. Download bootstrap_win_dev.vbs from the gnucash-on-windows
repository on Github. Direct url:
https://raw.githubusercontent.com/Gnucash/gnucash-on-windows/master/bootstrap_win_dev.vbs
-b. Run this script by double-clicking it and follow the instructions.
+c. Run this script by double-clicking it and follow the instructions.
If the script's output window closes before you get to a "Happy hacking"
message then something went wrong. To figure out what you can instead
open a Windows command prompt (cmd.exe) and run the script as
@@ -86,7 +90,7 @@ The default values will all be found in 'defaults.sh'. You can override any of t
in 'custom.sh'. The boostrap script you ran in step b. already created an initial
version of this file.
-c. Open an Msys shell window. You do this by running
+d. Open an Msys shell window. You do this by running
c:\gcdev\mingw\msys\1.0\msys.bat
Unless you chose to install mingw/msys in another directory of course.
Let the automated build begin by:
@@ -97,7 +101,7 @@ c. Open an Msys shell window. You do this by running
If you chose to set up the build environment in a different location adjust
the path accordingly.
-d. To generate a self-installing setup.exe file that contains *everything* run
+e. To generate a self-installing setup.exe file that contains *everything* run
the following command after install.sh has completed:
./dist.sh
Summary of changes:
README | 64 +++++++++++++++++++++++++++++++++++++++-------------------------
1 file changed, 39 insertions(+), 25 deletions(-)
More information about the gnucash-changes
mailing list