From: tomas@fabula.de
Cc: tomas@fabula.de
Subject: Re: Auto(conf|make) style questions
Date: Thu, 20 Mar 2003 08:56:01 +0100 [thread overview]
Message-ID: <20030320075600.GA8975@www> (raw)
In-Reply-To: <878yvb1cjj.fsf@raven.i.defaultvalue.org>
On Wed, Mar 19, 2003 at 11:39:12AM -0600, Rob Browning wrote:
> tomas@fabula.de writes:
>
> > - AC_LIBOBJ passes the extra objects through $(LIBOBJS). That
> > means that I can only do it globally, not for a specific
> > binary. Is there another way?
>
> Offhand, I don't think so. [...]
Thanks, Rob. Your answera are always very helpful.
> I ran in to a similar problem with the config.h fixes [...]
Yuck. I keep asking myself wyh those things have to be so messy.
> Unless you can't, or there's some limitation I'm not thinking of, I
> probably still be more likely to use #if guile version testing:
>
> #if GUILE_MAJOR_VERSION >= ... && GUILE_MINOR_VERSION ...
>
> though if I wanted more specific, per-function testing, I guess I
> might test for the features in configure.in and then stick a "#define
> GNEON_NEEDS_SCM_C_STRING2STR 1" into a public config header (but not
> config.h, unless you don't need the symbol publically).
>
> Alternately, you could centralize the version info in a header, but
> still have per-issue defines:
>
> #if GUILE_MAJOR_VERSION >= ... && GUILE_MINOR_VERSION ...
> # define GNEON_NEEDS_SCM_C_STRING2STR 1
> # define GNEON_HAS_TO_CORRECT_FOR_GUILE_CRUFT_BAR 1
> #endif
Yup. It's the old ``version test versus feature test'' issue. I'll
prepare another post on that.
Thanks for your suggestions.
Regards
-- tomas
next prev parent reply other threads:[~2003-03-20 7:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-19 17:21 Auto(conf|make) style questions tomas
2003-03-19 17:39 ` Rob Browning
2003-03-20 7:56 ` tomas [this message]
2003-03-19 17:46 ` Mikael Djurfeldt
2003-03-19 19:26 ` Alexandre Duret-Lutz
2003-03-20 8:04 ` tomas
2003-03-21 20:17 ` Alexandre Duret-Lutz
2003-03-22 8:32 ` tomas
[not found] ` <878yvbi6ih.fsf@alice.rotty.yi.org>
2003-03-20 10:48 ` tomas
2003-04-26 8:17 ` Neil Jerram
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030320075600.GA8975@www \
--to=tomas@fabula.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).