Daniel J Sebald writes, proposing a new
"configure" option:
> it might be something like:
>
> --builddir=DIR object and libraries
>
> which is essentially the same as doing:
>
> mkdir ../DIR
> cd ../DIR
> ..//configure OTHER_OPTS
> cd ../
Following the "configure", the next step will be
Hi Eric and all,
Your idea may make sense, but I'd first like to have an opinion from the
folks that maintain the GNU Coding Standards
rms is the only "maintainer" of the coding standards, in the sense of
being empowered to make nontrivial changes. (I get to make trivial
changes. :)
On 08/13/2012 12:07 PM, Eric Blake wrote:
On 08/13/2012 10:57 AM, Daniel J Sebald wrote:
it might be something like:
--builddir=DIR object and libraries
which is essentially the same as doing:
mkdir ../DIR
cd ../DIR
..//configure OTHER_OPTS
cd ../
I'm reading up on VPATH build
On 08/13/2012 12:07 PM, Eric Blake wrote:
On 08/13/2012 10:57 AM, Daniel J Sebald wrote:
it might be something like:
--builddir=DIR object and libraries
which is essentially the same as doing:
mkdir ../DIR
cd ../DIR
..//configure OTHER_OPTS
cd ../
I'm reading up on VPATH build
On 08/13/2012 10:57 AM, Daniel J Sebald wrote:
>>> it might be something like:
>>>
>>> --builddir=DIR object and libraries
>>>
>>> which is essentially the same as doing:
>>>
>>> mkdir ../DIR
>>> cd ../DIR
>>> ..//configure OTHER_OPTS
>>> cd ../
>>
>
> I'm reading up on VPATH builds. I
On 08/13/2012 09:04 AM, Eric Blake wrote:
[adding bug-standards]
On 08/12/2012 08:12 PM, Daniel J Sebald wrote:
Hello Autoconf,
The Octave maintainers had a discussion about adding an option to
"configure" for a build directory. The reason is that a lot of people
like running configure from a
[adding bug-standards]
On 08/12/2012 08:12 PM, Daniel J Sebald wrote:
> Hello Autoconf,
>
> The Octave maintainers had a discussion about adding an option to
> "configure" for a build directory. The reason is that a lot of people
> like running configure from a directory other than the source tr
