[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Auto(conf|make) style questions
From: |
tomas |
Subject: |
Re: Auto(conf|make) style questions |
Date: |
Thu, 20 Mar 2003 09:04:01 +0100 |
User-agent: |
Mutt/1.3.28i |
On Wed, Mar 19, 2003 at 08:26:26PM +0100, Alexandre Duret-Lutz wrote:
> >>> "tomas" == tomas <address@hidden> writes:
>
> [...]
>
> >> libguile_neon_neon_la_LIBADD = $(LIBOBJS)
>
> I think you meant $(LTLIBOBJS)
>
> [...]
>
> tomas> - AC_LIBOBJ passes the extra objects through
> tomas> $(LIBOBJS). That means that I can only do it globally,
> tomas> not for a specific binary. Is there another way?
>
> Sure... don't use LIBOBJS :)
>
> For instance replace
>
> if test "$guile_neon_cv_has_string2str" = "no"; then
> echo "Including scm_c_string2str.c in object files"
> AC_LIBOBJ(scm_c_string2str)
> fi
>
> by something like
>
> if test "$guile_neon_cv_has_string2str" = "no"; then
> echo "Including scm_c_string2str.c in object files"
> NEON_COMPAT="$NEON_COMPAT scm_c_string2str.lo"
^^^^ EEEK! ;-)
> fi
> AC_SUBST([NEON_COMPAT])
>
> and use
>
> libguile_neon_neon_la_LIBADD = $(NEON_COMPAT)
> EXTRA_libguile_neon_neon_la_SOURCES = scm_c_string2str.c
If I understand the configury documentation correctly -- isn't using
explicit dynamic object endings a ``Don't Do That?'' and exactly what
$(LIBOBJS) or $(LTLIBOBJS) is supposed to handle for you? For .lo is
platform specific...
(and no, if I understand... correctly above is no useless rethoric.
I have too often the feeling that those docs are beyond me, really).
But yes, thank you for your idea.
Regards
-- tomas