Fellow developers --
So, a question to the other developers: as the gnc-plugin files are
solely on the g2 branch, is it better to just move the ,v files in the
repository and save the file history, or should we just cvs add/remove
the files to move them from src/gnome to src/gnome-utils? I'm open
Actually, the problem is the change to to gnc-mdi-utils that jsled did
on Sunday, May 30, which makes it depends on src/gnome/gnc-window.
-derek
Derek Atkins <[EMAIL PROTECTED]> writes:
> The problem is that with recent changes to src/gnome/gnc-window.c the
> app-file code now depends on src/gno
The problem is that with recent changes to src/gnome/gnc-window.c the
app-file code now depends on src/gnome, which is Bad. Currently
app-file can depend on gnome-utils, but not gnome (due to the build
order). This means that the gnc-plugin code NEEDS to move to
src/gnome-utils (as does gnc-windo
[EMAIL PROTECTED] (Linas Vepstas) writes:
> ? There are currently four back-ends, two operational and two in
> disrepair. The ones that work are xml and sql, the rpc and the http
> backends are not used and no longer work. As far as I know, the front
> end doesn't suffer from limitations in the
Hi John,
On Sat, May 29, 2004 at 11:26:09PM -0700, John Arrowwood was heard to remark:
> You've got to be careful here. Some things to ponder:
>
> In a multi-user environment, you don't want user A to be blocked because
> user B is trying to do something. If they are blocked, it should be for
Hello,
I get this kind of problem:
Making all in test
make[5]: Entering directory `/home/amd/code/gnucash/src/app-file/test'
/bin/sh ../../../libtool --mode=link gcc -g -O2 -Wall -Wunused -
Werror -o test-link test-link.o ../libgncmod-app-file.la -lpopt -lm
-lm
gcc -g -O2 -Wall -Wunused -We
