Drop support for multiple configurations (issue 581630043 by jonas.hahnfeld@gmail.com)

classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

Drop support for multiple configurations (issue 581630043 by jonas.hahnfeld@gmail.com)

Dev mailing list
Reply | Threaded
Open this post in threaded view
|

Re: Drop support for multiple configurations (issue 581630043 by jonas.hahnfeld@gmail.com)

Carl Sorensen
I really like the work.  I just wonder if we should eliminate the
instructions on how to achieve the objective.


https://codereview.appspot.com/581630043/diff/563520043/Documentation/included/compile.itexi
File Documentation/included/compile.itexi (left):

https://codereview.appspot.com/581630043/diff/563520043/Documentation/included/compile.itexi#oldcode895
Documentation/included/compile.itexi:895: @node Compiling for multiple
platforms
I wonder if we should keep the heading "Compiling for multiple
platforms", and just have it say "Use a separate build directory for
each different platform, and run configure in each build directory."
Perhaps even use the same example, and show how to handle this
situation.

https://codereview.appspot.com/581630043/

Reply | Threaded
Open this post in threaded view
|

Re: Drop support for multiple configurations (issue 581630043 by jonas.hahnfeld@gmail.com)

hanwenn
In reply to this post by Dev mailing list
Oh no! I was using this just this week for GUILE2 vs GUILE1.8


(but OK to remove, I agree it is too baroque).

https://codereview.appspot.com/581630043/

Reply | Threaded
Open this post in threaded view
|

Re: Drop support for multiple configurations (issue 581630043 by jonas.hahnfeld@gmail.com)

hanwenn
In reply to this post by Dev mailing list

https://codereview.appspot.com/581630043/diff/563520043/Documentation/included/compile.itexi
File Documentation/included/compile.itexi (left):

https://codereview.appspot.com/581630043/diff/563520043/Documentation/included/compile.itexi#oldcode895
Documentation/included/compile.itexi:895: @node Compiling for multiple
platforms
On 2020/02/12 16:50:30, Carl wrote:
> I wonder if we should keep the heading "Compiling for multiple
platforms", and
> just have it say "Use a separate build directory for each different
platform,
> and run configure in each build directory."  Perhaps even use the same
example,
> and show how to handle this situation.

people that need to do this are probably expert enough to already know
how to achieve it.

https://codereview.appspot.com/581630043/

Reply | Threaded
Open this post in threaded view
|

Re: Drop support for multiple configurations (issue 581630043 by jonas.hahnfeld@gmail.com)

jonas.hahnfeld
In reply to this post by Dev mailing list
Reviewers: lemzwerg, carl.d.sorensen_gmail.com, hanwenn,

Message:
On 2020/02/12 20:45:31, hanwenn wrote:
>
https://codereview.appspot.com/581630043/diff/563520043/Documentation/included/compile.itexi
> File Documentation/included/compile.itexi (left):
>
>
https://codereview.appspot.com/581630043/diff/563520043/Documentation/included/compile.itexi#oldcode895
> Documentation/included/compile.itexi:895: @node Compiling for multiple
platforms
> On 2020/02/12 16:50:30, Carl wrote:
> > I wonder if we should keep the heading "Compiling for multiple
platforms", and
> > just have it say "Use a separate build directory for each different
platform,
> > and run configure in each build directory."  Perhaps even use the
same
> example,
> > and show how to handle this situation.
>
> people that need to do this are probably expert enough to already know
how to
> achieve it.

Right, this is core functionality from Autoconf and described in their
documentation. Additionally I don't think "multiple platforms" is a
thing nowadays - there's x86_64 and that's mostly it what you compile on
a single system.

Description:
Drop support for multiple configurations

Currently configure has the flag --enable-config=CONF which allows to
have multiple configurations in the same directory and choose from them
using `make conf=CONF'. This might have been useful in the last century
(yes, the flag was really added in 1998 with LilyPond 1.0.1!) ...
Nowadays the solution is to just have many build directories, pointing
to
the same source directory. The additional possibility just complicates
the
build system and makes future changes harder than necessary.

Please review this at https://codereview.appspot.com/581630043/

Affected files (+18, -86 lines):
  M Documentation/contributor/build-notes.itexi
  M Documentation/included/compile.itexi
  M aclocal.m4
  M config.make.in
  M configure.ac
  M make/stepmake.make