Hello,
On Sat, 30 Nov 2019 12:00:19 -0500, Dan Eble wrote:
> On Nov 28, 2019, at 03:13, Werner LEMBERG wrote:
> >
> > This is very, very non-standard and completely undocumented.
>
> Not completely undocumented. The CG has said to run configure with
> --disable-optimising for as long as I c
>> This is very, very non-standard and completely undocumented.
>
> Not completely undocumented. The CG has said to run configure with
> --disable-optimising for as long as I can remember.
I don't mean this option but the fact that CXXFLAGS as set by the user
gets almost completely overwritten
On Nov 28, 2019, at 03:13, Werner LEMBERG wrote:
>
> This is very, very non-standard and completely undocumented.
Not completely undocumented. The CG has said to run configure with
--disable-optimising for as long as I can remember.
> Any idea how this could be improved?
A good start would b
Most developers expect that you can easily adjust C++ compiler flags
in a GNU package using CXXFLAGS. With LilyPond, however, this is
quite problematic. Reason is that it internally uses the following
variables to compute the final list of compiler flags (see files
`c++-vars.make` and `aclocal.
