[Mono-dev] Running autogen.sh from outside of source tree?
chmorgan at gmail.com
Wed May 21 19:54:01 UTC 2014
So I'm just trying to find out if it seems feasible, at which point
I'll go to it for a few and see if I can do so.
On Wed, May 21, 2014 at 3:39 PM, Chris Morgan <chmorgan at gmail.com> wrote:
> Hi Zoltan.
> No, I get that. The question is whether its possible to improve
> autogen.sh to support running out of tree by adding some more $srcdir
> entries, or whatever, at the appropriate locations.
> On Wed, May 21, 2014 at 3:37 PM, Zoltan Varga <vargaz at gmail.com> wrote:
>> autogen.sh needs to be run from the tree, its configure+make which can be
>> run out-of-tree.
>> On Wed, May 21, 2014 at 9:32 PM, Chris Morgan <chmorgan at gmail.com> wrote:
>>> I'm trying to build mono under Yocto. Recently (so I've heard) there
>>> were some changes such that the autotools scripts are being run from
>>> outside of the source tree.
>>> I presume this is something like:
>>> cd mono
>>> mkdir monobuild
>>> cd monobuild
>>> [cmorgan at localhost monobuild]$ ../autogen.sh
>>> grep: configure.in: No such file or directory
>>> ../autogen.sh: line 125: mono/mini/Makefile.am: No such file or directory
>>> ../autogen.sh: line 126: mono/metadata/Makefile.am: No such file or
>>> Running aclocal -I m4 -I . ...
>>> aclocal: error: 'configure.ac' is required
>>> **Error**: aclocal failed. This may mean that you have not
>>> installed all of the packages you need, or you may need to
>>> set ACLOCAL_FLAGS to include "-I $prefix/share/aclocal"
>>> for the prefix where you installed the packages whose
>>> macros were not found
>>> This doesn't appear to work because several things in autogen.sh
>>> assume that the files are present in the current working directory.
>>> Some other steps however do use $srcdir.
>>> My question is whether it seems like a reasonable idea to correct
>>> autogen.sh to remove the assumption that builddir == sourcedir. If so
>>> then I'll go down this route and send a patch. If not then I'll use a
>>> Yocto work around for projects that don't/can't support doing that.
>>> I'm not big on papering over issues so I do prefer the first option
>>> but I didn't want to start work if it turns out that it may be a
>>> nearly impossible task.
>>> Mono-devel-list mailing list
>>> Mono-devel-list at lists.ximian.com
More information about the Mono-devel-list