Wrap patching code in conditional in most cases to only run patch if
there actually is a patch file available.
git-svn-id: svn+ssh://svn.gnucash.org/repo/gnucash/trunk@22715 57a11ea4-9604-0410-9ed3-97b8803252fd
This way they will be checked in/out in proper line ending style on all
supported platforms.
git-svn-id: svn+ssh://svn.gnucash.org/repo/gnucash/trunk@22714 57a11ea4-9604-0410-9ed3-97b8803252fd
The code used to apply the patches if present still remains to cater for
possible future patches.
git-svn-id: svn+ssh://svn.gnucash.org/repo/gnucash/trunk@22713 57a11ea4-9604-0410-9ed3-97b8803252fd
The goal of this script is to make is extremely easy to start gnucash
development on Windows. After downloading and running this script, the
user should be ready to start coding.
Note that this is not the case yet. The bootstrap script is only the
first step in that direction.
git-svn-id: svn+ssh://svn.gnucash.org/repo/gnucash/trunk@22707 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
The previous commit broke the build. Hopefully this one fixes it again.
git-svn-id: svn+ssh://svn.gnucash.org/repo/gnucash/trunk@22381 57a11ea4-9604-0410-9ed3-97b8803252fd
- start from the proper base directory (daily_build.bat)
- don't build daily/weekly unless there are new commits since the last
build
git-svn-id: svn+ssh://svn.gnucash.org/repo/gnucash/trunk@22327 57a11ea4-9604-0410-9ed3-97b8803252fd
The parameter has been obsoleted recently, but older
tags may still depend on its availability and the tag script is
supposed to be capable of building older tags as well.
git-svn-id: svn+ssh://svn.gnucash.org/repo/gnucash/trunk@22319 57a11ea4-9604-0410-9ed3-97b8803252fd
files that are in use in every file that can be affected.
git-svn-id: svn+ssh://svn.gnucash.org/repo/gnucash/trunk@22317 57a11ea4-9604-0410-9ed3-97b8803252fd
This was temporarily changed to daily during the 2.4.10 release
timeframe to stomp out some release bugs. That should no longer be
necessary.
git-svn-id: svn+ssh://svn.gnucash.org/repo/gnucash/trunk@22314 57a11ea4-9604-0410-9ed3-97b8803252fd
Additionally, update the README file to explain how the start from
scratch with a git repository.
git-svn-id: svn+ssh://svn.gnucash.org/repo/gnucash/trunk@22309 57a11ea4-9604-0410-9ed3-97b8803252fd
Developers should manually choose when and how to update their checked
out repository. Automated builders can simply write a short wrapper
script around the install the does the update for them. The
daily_build_git.sh and daily_build.sh scripts are fine examples.
git-svn-id: svn+ssh://svn.gnucash.org/repo/gnucash/trunk@22308 57a11ea4-9604-0410-9ed3-97b8803252fd
- use consistent naming for the final installer executable
- Default to no for UPDATE_SOURCES
git-svn-id: svn+ssh://svn.gnucash.org/repo/gnucash/trunk@22306 57a11ea4-9604-0410-9ed3-97b8803252fd
IMPORTANT: the update mechanism from git has been kept deliberately
simple because svn updates don't really match well to
git's distributed repository concept.
It assumes you are working as a non-committer (see
http://wiki.gnucash.org/wiki/Git for what that means) and will
simply try to pull the current branch from the upstream
repository. I don't know of any currently active committer that works
from Windows, so to start that should be sufficient.
Setting up git-update instead of git pull requires more thorough
changes in the Windows build system:
- it requires at least perl 5.8 (our default msys-dtk only install perl
5.6)
- the environment variable GITPERLLIB should be set to the perl library
that comes with the installed git.
- git-update should be installed somewhere
git-svn-id: svn+ssh://svn.gnucash.org/repo/gnucash/trunk@22303 57a11ea4-9604-0410-9ed3-97b8803252fd
Configure gets confused by some gcc builtins on Win7: Disable them so that configure finds the right settings.
[BP]
git-svn-id: svn+ssh://svn.gnucash.org/repo/gnucash/trunk@22197 57a11ea4-9604-0410-9ed3-97b8803252fd
With these changes install-fq-mods.cmd will automatically download and install
Strawberry perl if now perl version if found on the system.
Patches by Dave Roberts
git-svn-id: svn+ssh://svn.gnucash.org/repo/gnucash/trunk@22169 57a11ea4-9604-0410-9ed3-97b8803252fd
Patch alters packaging/win32/libbonoboui-2.24.2.patch to not look for glade and not
build libbonoboui-2.24.2/glade
Patch by Mark Jenkins.
git-svn-id: svn+ssh://svn.gnucash.org/repo/gnucash/trunk@22156 57a11ea4-9604-0410-9ed3-97b8803252fd
The last contributors here, Josh Sled and Chris Lyttle, have put their
code under "GPLv2 and GPLv3" license, see r22063, but I'm too lazy to
look up the copyright holders on the file as a whole so I'd rather remove it.
If someone wants to add a similar packaging file again, feel free to do
so, but please don't use GPLv2-only code to do so.
git-svn-id: svn+ssh://svn.gnucash.org/repo/gnucash/trunk@22067 57a11ea4-9604-0410-9ed3-97b8803252fd
This avoids problems when libraries or reports have been moved around in newer versions.
git-svn-id: svn+ssh://svn.gnucash.org/repo/gnucash/trunk@21894 57a11ea4-9604-0410-9ed3-97b8803252fd
Geert Janssens
Christian Stimming
John Ralls