[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Best practice sharing autotest macros
From: |
Eric Blake |
Subject: |
Re: Best practice sharing autotest macros |
Date: |
Tue, 03 Dec 2013 10:02:02 -0700 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.1.0 |
On 11/28/2013 08:32 PM, Luke Mewburn wrote:
> Hi folks,
>
> I've got a few autotest macros that are used across various projects,
> and I'm looking for advice regardard the best practice in how to
> share these between the projects. Currently I just cut and paste
> our autotest macros to the project's local.at.
>
> For autoconf macros, common macros are used by storing them in a common
> /path and with ACLOCAL_AMFLAGS = -I/path in the top-level Makefile.am,
> and aclocal automagically finds the macro definition.
>
> I have considered a shared /path and passing -I/path to autom4te,
> which requires an explicit m4_include([foo.m4]) to bring in the
> definition, because autom4te doesn't appear to do the same automagic
> macro finding that aclocal does.
Sounds reasonable to me.
>
> Do people have any advice, better suggestions, etc?
Sorry, none from me - but do feel free to post what works for you, so we
have it in the archives.
>
> Also, is this list a good place to discuss adding more autotest AT_
> macros to autotest?
Yes.
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
signature.asc
Description: OpenPGP digital signature
- Re: Best practice sharing autotest macros,
Eric Blake <=