Geert Janssens writes:
>> The one that matters most, I believe, is the "gnucash.bat". Luckily
>> that one doesn't update frequently, so I think we can manually update
>> that as necessary. But yes, I do believe we have hit this issue before.
>
> It's not "gnucash.bat". It's in the scripts that
On 15-08-12 15:19, Derek Atkins wrote:
Christian Stimming writes:
Am Samstag, 11. August 2012, 18:23:35 schrieb Geert Janssens:
I suspect there's only one automated builder in existence for GnuCash on
Windows, and that's our own build server. So I'll focus on this one only.
For this builder
Christian Stimming writes:
> Am Samstag, 11. August 2012, 18:23:35 schrieb Geert Janssens:
>> I suspect there's only one automated builder in existence for GnuCash on
>> Windows, and that's our own build server. So I'll focus on this one only.
>>
>> For this builder we have a set of scripts that
Am Samstag, 11. August 2012, 18:23:35 schrieb Geert Janssens:
> I suspect there's only one automated builder in existence for GnuCash on
> Windows, and that's our own build server. So I'll focus on this one only.
>
> For this builder we have a set of scripts that wrap around the actual
> install s
Geert Janssens writes:
> So suppose we drop the separate packaging directory requirement, then
> the svn update would in one go update the build scripts and the source
> to build, still automatically at each run. There would be no need
> anymore for an UPDATE_SOURCES in the install.sh script.
Ye
On Aug 11, 2012, at 8:29 AM, Geert Janssens wrote:
> I have just added some scripts to run an automated build from git instead of
> svn.
>
> I copied the svn behaviour as closely as possible. While doing so I got to
> question parts of the general setup we promote [1]. The guidelines state th
On 11-08-12 17:54, Derek Atkins wrote:
Geert,
I think there are two different types of builders: the automated builder,
and a developer.
The automated builder is always going to want to build the most recent
changeset on any particular branch, and it's going to want to be able to
update the bu
Geert,
I think there are two different types of builders: the automated builder,
and a developer.
The automated builder is always going to want to build the most recent
changeset on any particular branch, and it's going to want to be able to
update the build scripts while doing so.
Developers p
I have just added some scripts to run an automated build from git
instead of svn.
I copied the svn behaviour as closely as possible. While doing so I got
to question parts of the general setup we promote [1]. The guidelines
state that the contents of packaging/win32 should be copied locally, a
