Best practise for aclocal paths in cross builds

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

I’m trying to clean up our autoconf invocation and want to do things the “right” way.

We’re in a cross environment with split native/target sysroots which makes things interesting, as this means there are two places which I consider the “system ac directories”, the target and the native.

Unfortunately you can’t pass a colon-separated list for —system-acdir so right now we’re effectively doing:

$ ACLOCAL="aclocal --system-acdir=/sysroot-target/usr/share/aclocal” autoreconf --include /sysroot-native/usr/share/aclocal

That is quite ugly. Now aclocal actually knows where the native aclocal directory is already so I could simplify that to:

$ ACLOCAL="aclocal --aclocal-path=/sysroot-target/usr/share/aclocal” autoreconf

But that still feels a little icky.  Does anyone have any better suggestions?  I’ll even try remembering how to write perl if there’s a neat solution that just needs a little coding.

Cheers,
Ross
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.




[Index of Archives]     [GCC Help]     [Kernel Discussion]     [RPM Discussion]     [Red Hat Development]     [Yosemite News]     [Linux USB]     [Samba]

  Powered by Linux