David, r15013 implies the former.. The plan is to design the build
system so that swig is only required to build from SVN. If you build
from the tarball then all the swig-generated files should already be
distributed so you shouldn't need swig during the build process.
At least, that's the curre
Does the conditionalization of swig (r15013) mean that tarballs will
already contain whatever wrappings will be required? Or just that for
the moment only the svn/svk builds will be accessing that?
I suppose I'm relieved that g-wrap is on the way out, but fink
doesn't have a swig maintainer
Debian's libtool is biting again, now in src/import-export/test.
Here's the fix:
--- src/import-export/test/Makefile.am (revisjon 15006)
+++ src/import-export/test/Makefile.am (arbeidskopi)
@@ -14,6 +14,7 @@
${top_builddir}/src/test-core/libgncmod-test.la \
../libgncmod-generic-import.la
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Derek Atkins schrieb:
> I suspect the swig-redo branch will get merged back into trunk
> in a week or two... I was wondering that myself, but I'm not
> sure we should.
If the merging work is done anyway very soon in the branch -> trunk
direction, the
I recently had a problem pop up on my gentoo linux system. I have eliminated
glib-1.x and gtk+-1.x from my system confgiuration. As a result, I cannot
emerge gnucash-2.x (not sure about 1.x but I suspect the same issue applies).
This is due to gentoo not having a version of g-wrap higher than
Quoting Bob McDonald <[EMAIL PROTECTED]>:
> I recently had a problem pop up on my gentoo linux system. I have
> eliminated glib-1.x and gtk+-1.x from my system confgiuration. As a
> result, I cannot emerge gnucash-2.x (not sure about 1.x but I suspect
> the same issue applies). This is due t
I suspect the swig-redo branch will get merged back into trunk
in a week or two... I was wondering that myself, but I'm not
sure we should.
-derek
Quoting Christian Stimming <[EMAIL PROTECTED]>:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> With all these changes in the Makefiles, I was
I recently had a problem pop up on my gentoo linux system. I have eliminated
glib-1.x and gtk+-1.x from my system confgiuration. As a result, I cannot
emerge gnucash-2.x (not sure about 1.x but I suspect the same issue applies).
This is due to gentoo not having a version of g-wrap higher than
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
With all these changes in the Makefiles, I was wondering whether the
swig-redo branch has already or should merge the changes in trunk that
were related to the g-wrap wrapper generation, i.e. avoiding the need to
symlink generation? That's 14746, 14747
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Thomas Bushnell BSG schrieb:
>> Thanks for the error reports. This bug has been #1 on my hit-list for
>> a while, but I hadn't been able to reproduce it. It turns out that
>> the "unable to delete split" behavior was a big clue, and something I
>> co
Quoting Thomas Bushnell BSG <[EMAIL PROTECTED]>:
> Chris Shoemaker <[EMAIL PROTECTED]> writes:
>
>> Thanks for the error reports. This bug has been #1 on my hit-list for
>> a while, but I hadn't been able to reproduce it. It turns out that
>> the "unable to delete split" behavior was a big clue,
> -Original Message-
> From: Chris Shoemaker [mailto:[EMAIL PROTECTED]
> Sent: Thursday, 12 October 2006 10:42 AM
> To: Steven Wilton
> Cc: gnucash-devel@gnucash.org
> Subject: Re: Budget report improvements
>
> Hi Steven,
> Sorry for the late reply, I'm just getting back to stuff
Chris Shoemaker <[EMAIL PROTECTED]> writes:
> Thanks for the error reports. This bug has been #1 on my hit-list for
> a while, but I hadn't been able to reproduce it. It turns out that
> the "unable to delete split" behavior was a big clue, and something I
> could finally reproduce. I'm hoping
13 matches
Mail list logo
