On Monday, January 2, 2017 10:56:10 AM CET Florian Weimer wrote:
> The final values of CFLAGS/LDFLAGS/… are set (as shell variables) by the
> %configure macro. There is no other immediately obvious way to get
> those definitions. This means that if you can't use %configure for some
> reason, you are out of luck.
>
> In this situation, this still works:
>
> %global %_configure :
> %configure
>
> As a result, %configure tries to run “:” instead of “./configure”, which
> is a NOP, and only the shell variable initialization remains.
>
> Is this the recommend way to initialize the compiler flags?
Meh, it would be hard to believe this is prefered way... at least because there
are default options like --prefix=/usr in %configure.
> Should we introduce a %setup_cflags macro to make this more explicit?
Maybe.
Also I'd like to se the %configure macro more "modularized", because it does too
much ATM and as you said, %configure is not for everybody. So one could call
something like:
%configure_libtool_hacks
%configure_fix_gnuconfig
.. only when there are reasons to not call %configure directly.
Pavel
> Thanks,
> Florian
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
