Compiling source with new code. (Doug Zain)
Doug Zain
dzain at yahoo.com
Tue Sep 6 12:54:59 EDT 2005
Derek, Thanks for the help that worked...
Were can I find more information on the postgres
rewrite?
Thanks again
--- gnucash-devel-request at gnucash.org wrote:
> Send gnucash-devel mailing list submissions to
> gnucash-devel at gnucash.org
>
> To subscribe or unsubscribe via the World Wide Web,
> visit
>
>
https://lists.gnucash.org/mailman/listinfo/gnucash-devel
> or, via email, send a message with subject or body
> 'help' to
> gnucash-devel-request at gnucash.org
>
> You can reach the person managing the list at
> gnucash-devel-owner at gnucash.org
>
> When replying, please edit your Subject line so it
> is more specific
> than "Re: Contents of gnucash-devel digest..."
>
>
> Today's Topics:
>
> 1. Compiling source with new code. (Doug Zain)
> 2. Re: [Gnucash-changes] check_data_type,
> backend configuration
> and gettext (Neil Williams)
> 3. Re: [Gnucash-changes] check_data_type,
> backend configuration
> and gettext (Neil Williams)
> 4. Re: Please do not commit any more code until
> you can compile
> with -Werror (Neil Williams)
> 5. Re: [Gnucash-changes] check_data_type,
> backend configuration
> and gettext (Derek Atkins)
> 6. Re: [Gnucash-changes] check_data_type,
> backend configuration
> and gettext (Derek Atkins)
> 7. Re: Compiling source with new code. (Derek
> Atkins)
> 8. Re: Please do not commit any more code until
> you can compile
> with -Werror (Derek Atkins)
> 9. Re: [Gnucash-changes] check_data_type,
> backend configuration
> and gettext (Neil Williams)
> 10. Re: Please do not commit any more code until
> you can compile
> with -Werror (Anthony Juckel)
>
>
>
----------------------------------------------------------------------
>
> Message: 1
> Date: Mon, 5 Sep 2005 14:39:37 -0700 (PDT)
> From: Doug Zain <dzain at yahoo.com>
> Subject: Compiling source with new code.
> To: gnucash-devel at gnucash.org
> Message-ID:
>
<20050905213937.92495.qmail at web30004.mail.mud.yahoo.com>
> Content-Type: text/plain; charset=iso-8859-1
>
> How can I add my own code to the backend/postgres
> directory and get it to compile and link using make.
>
> I am just trying to learn what types of querys are
> being sent to the postgres backend and how they are
> processed.
> The code created will write the querys to a file for
> further investigation.
>
> Yes - I am a new hacker...
>
>
>
>
>
______________________________________________________
> Click here to donate to the Hurricane Katrina relief
> effort.
> http://store.yahoo.com/redcross-donate3/
>
>
> ------------------------------
>
> Message: 2
> Date: Tue, 6 Sep 2005 11:32:16 +0100
> From: Neil Williams <linux at codehelp.co.uk>
> Subject: Re: [Gnucash-changes] check_data_type,
> backend configuration
> and gettext
> To: gnucash-devel at gnucash.org
> Message-ID:
> <200509061132.19408.linux at codehelp.co.uk>
> Content-Type: text/plain; charset="iso-8859-1"
>
> On Monday 05 September 2005 3:16 pm, Derek Atkins
> wrote:
> > Why are you replacing gnc_{un,}setenv() with
> {un,}setenv() when NOT
> > ALL SYSTEMS HAVE SETENV?
>
> Ah. B****er.
>
> OK, I've implemented the gnc_ - it's just a question
> of how it will eventually
> be defined. I can't let gnc-backend-file use files
> from src/core-utils so I'm
> currently using a cashutil-only header and added
> setenv to AC_CHECK_FUNC in
> cashutil. In the final libgnc-backend-file.la,
> there'll be no included files
> from src/core-utils or other parts of the gnucash
> tree (like src/gnome) so
> it'll be safe to define it within src/backend/file.
>
> > Bad Neil! No Biscuit!
>
> I understand.
>
> --
>
> Neil Williams
> =============
> http://www.data-freedom.org/
> http://www.nosoftwarepatents.com/
> http://www.linux.codehelp.co.uk/
>
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: not available
> Type: application/pgp-signature
> Size: 189 bytes
> Desc: not available
> Url :
>
http://lists.gnucash.org/pipermail/gnucash-devel/attachments/20050906/311deed3/attachment-0001.bin
>
> ------------------------------
>
> Message: 3
> Date: Tue, 6 Sep 2005 11:44:27 +0100
> From: Neil Williams <linux at codehelp.co.uk>
> Subject: Re: [Gnucash-changes] check_data_type,
> backend configuration
> and gettext
> To: gnucash-devel at gnucash.org
> Message-ID:
> <200509061144.30627.linux at codehelp.co.uk>
> Content-Type: text/plain; charset="iso-8859-1"
>
> On Monday 05 September 2005 3:28 pm, Derek Atkins
> wrote:
> > Umm, I don't think you can necessarily guarantee
> that the .la is
> > installed.
>
> ? I thought it was the recommended method for GNU
> systems ?
>
>
http://www.gnu.org/software/libtool/manual.html#Finding-the-dlname
>
> > Indeed, most places do NOT install the .la, just
> the .so
> > (or .dynlib) in the packaging system.
>
> Is there a problem in requiring that it *is*
> installed? All packaging systems
> that I know will *allow* it to be installed, it may
> not be common practice
> but it can be done - why else would GNU recommend
> it?
>
> Isn't this a case of the packaging dictating to the
> source? If there is a
> standard and recommended GNU method that is declared
> as "[t]he most
> straightforward and flexible implementation" why
> should the source be forced
> to support a less straightforward and less flexible
> method?
>
> What if a new system starts supporting GNU libtool
> and adds yet another suffix
> to the possible list?
>
> You've asked me to put the demands of the source
> above those of the packaging
> and now I'm confused.
> :-(
>
> > Also, I'm not sure I like the new API, unless
> "directory" is a "hint"
> > -- the ldopen() should have a set of directories
> it can search. A
> > "search path".
>
> I'll double-check, I thought it did this already
> (internally). If not, I'll
> add it - as recommended on the libtool page above.
>
> --
>
> Neil Williams
>
=== message truncated ===
______________________________________________________
Click here to donate to the Hurricane Katrina relief effort.
http://store.yahoo.com/redcross-donate3/
More information about the gnucash-devel
mailing list