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-local" rules I can simply use:
configure.ac:
AC_SUBST(SOME_TEST, [$(top_builddir)/scripts/test/install/bin/something])
check-local: check-something
check-something:
@SOME_TEST@ --or --other
What do you think? My main goal is portability, the next is
maintainability.
Thanks,
Justin
On 4/7/11 6:28 AM, "Dave Hart" <[email protected]> wrote:
>On Wed, Apr 6, 2011 at 20:45 UTC, Too, Justin A. <[email protected]> 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)/scripts/test/install/bin/something --or --other
>
>That may be more straightforward than portably modifying the
>environment for submakes.
>
>Cheers,
>Dave Hart
