Rob Browning, in an immanent manifestation of deity, wrote:
>If SWIG does a good job, then yes, but if it's not going to provide a
>good solution, then I'd rather just see each interested group create
>and maintain bindings for that language until/if/unless there's a
>unified solution that actuall
Rob Browning, in an immanent manifestation of deity, wrote:
>On Wed, 01 Nov 2000 16:20:05 Clinton Popetz wrote:
> | One key advantage of doing it in SWIG is that SWIG can spew out Python
> | interfaces as well, and I hear there are people who actually like
> | programming in Python. :)
>
>Pyth
Dave Peticolas, in an immanent manifestation of deity, wrote:
>Ok. The engine is changing a lot these days, so I would hold off on
>doing any work on it right now. When it's starts to stabilize, anyone
>who is interested should feel free to update the swig API work. This
>will require a fair bit o
Dave Peticolas, in an immanent manifestation of deity, wrote:
>Who uses the Perl API?
I do. But I suspect that I'm one of the few. I just don't have the
time to (re-)learn scheme. I used lisp in the 80s but these days, I
only use it for (X)Emacs.
>The reason I ask is that the Perl API is rapi
Matthew Vanecek, in an immanent manifestation of deity, wrote:
>me2v@reliant me2v $ locate LWP/UserAgent
>/usr/lib/perl5/site_perl/5.005/LWP/UserAgent.pm
>
>from a RH system. I've got the same problem with a different module in
>1.4.2:
>
>me2v@reliant account $ gnc-prices myaccts.xac
>Can't loca
-BEGIN PGP SIGNED MESSAGE-
Rob Browning, in an immanent manifestation of deity, wrote:
>Swig will be going away as a "normally compiled" bit. It'll still be
>available as an --enable-swig option, at least for the time being, and
>pretty soon, there'll be an easy way to do this with the t
So, I wanted to have all the accounts set up without waiting for the
text-import feature to become available. I figure that importing a text
file of just accounts is much quicker than a general facility.
I was debating whether to do it in scheme or Perl. I finally chose Perl
because I program i
-BEGIN PGP SIGNED MESSAGE-
So, if I want to use the latest and greatest gnucash updated to now with
CVS, I should just use gnucash rather than gnucash-1-4-branch, right?
The reason that I ask is that VERSION is set to 1.3.100 on gnucash but
set to 1.4.1 on gnucash-1-4-branch.
I do notic
-BEGIN PGP SIGNED MESSAGE-
To compile gnucash with debugging turned on, specifically with a
configure line of:
./configure --with-opt-style-install --prefix=/usr/local/gnucash --enable-debug
one needs to patch the top-level.c in the motif and gnome directories
and define the the module d
-BEGIN PGP SIGNED MESSAGE-
teri, in an immanent manifestation of deity, wrote:
>This is on a Caldera 1.2 system. Most of the RH 5.x RPMS out there
>don't work here because of incompatible libraries, that's why I had to
>compile most of the accessory packages from source. I noticed that
-BEGIN PGP SIGNED MESSAGE-
Well, I was trying out gnucash. I thought I'd try importing the quicken
data from my bank. This caused a crash. But I don't know how to tell
what version of quicken data, my bank gave me. It's Well's Fargo.
Anyone know if there are identifiers for versions?
11 matches
Mail list logo