Hi Ralf,
On 2011-04-02 10:42 +0200, Ralf Wildenhues wrote:
> * Nick Bowler wrote on Fri, Apr 01, 2011 at 04:04:21PM CEST:
> > I'm working on a project which uses libltdl to load modules, and I've
> > set it up in a manner pretty similar to what's described in the libtool
> > manual (10.3 Linking w
"Too, Justin A." writes:
> Can I define SOME_TEST in only one Makefile.am and make it available to
> all of the others? I have many Makefile.ams that require the SOME_TEST
> variable and I would prefer not having to define it in every Makefile.am
> individually. If I have it in one location, it p
Hi Ben,
Can I define SOME_TEST in only one Makefile.am and make it available to
all of the others? I have many Makefile.ams that require the SOME_TEST
variable and I would prefer not having to define it in every Makefile.am
individually. If I have it in one location, it provides me the flexibility
"Too, Justin A." writes:
> Thanks for the tips. I definitely would like to have the most portable
> solution so I'm leaning toward Dave's suggestion. The reason I wanted the
> PATH solution, however, was to keep things simple and in one location.
> Maybe what I will do is set an AC_SUBST for SOME
Hi,
Thanks for the tips. I definitely would like to have the most portable
solution so I'm leaning toward Dave's suggestion. The reason I wanted the
PATH solution, however, was to keep things simple and in one location.
Maybe what I will do is set an AC_SUBST for SOME_TEST, then in the
"check-loca
On Wed, Apr 6, 2011 at 20:45 UTC, Too, Justin A. wrote:
> Or is there a better way to accomplish this?
Instead of changing $PATH, you could refer to the executable relative
to $(top_builddir) in your check-local targets:
check-local: check-something
check-something:
$(top_builddir)/scrip
