bug#54020: Allow user-defined libtool options

Mike Frysinger <[email protected]> Sat, 13 Jan 2024 01:19:30 -0500
Newsgroups gmane.comp.sysutils.automake.bugs,gmane.comp.sysutils.automake.patches
Message-ID <ZaIrcmJQ0dt5CWyg@vapier>
On 15 Mar 2023 17:31, Bogdan wrote:
>   Another patch from my side. This one makes it possible for users to 
> pass additional options to libtool in 'compile' mode. Fixes #54020.
> 
>   Added documentation and a test case including the '-no-suppress' 
> option. All tests with 'lt' or 'libtool' in the name pass.
> 
>   Feel free to rename the variables, I just came up with the names 
> LTCOMPILE_PREFLAGS and LTCOMPILE_POSTFLAGS, reflecting the positions 
> where the variables are put and the mode they're used in.

why do we need LTCOMPILE_POSTFLAGS ?  isn't that just after the compile
command ?  $obj_compile expands into e.g.
	\$(CC) @cpplike_flags \$(AM_CFLAGS) \$(CFLAGS)

so if someone wants to add flags to C/etc..., they already have knobs
to turn.

which means this would simplify by only having one variable right ?
AM_LTCOMPILE_FLAGS
-mike
signature.asc (application/pgp-signature, 833 B)
-----BEGIN PGP SIGNATURE-----

iQIzBAABCAAdFiEEuQK1JxMl+JKsJRrUQWM7n+g39YEFAmWiK3IACgkQQWM7n+g3
9YEUhBAA2ZfMy9CybBRfttHq64lie3fN2v1YTssMqgCJfskZancLsGzXunvSQzyO
U/9BZJK998vq/NhHVwV3NNoMGNLjLgrFknB6MjwBUeTxo+jiH2VeZDGVFI3prwNv
TFKfPOjLdyQz+CV8Bz0QwXJxUGyC1Q9FAQgxN0IteEUDIMXnzjHBwr89bhcPEIeL
80VsJlkFwxlVATF0F/ilenlF2LDNCX12JyhY84oxnFNmQvlaIUPFIJxa7YNcCAqj
6lRtA0zMwZF8B/aRrHBbBqOHTJNdxkDrZ/984rMHzYhKMmYG5pi3lEgCLVMFEqLZ
9zeoDtwReDnVDICthIuxzxC/+RYmAP9mgkhQH7hxNfZ2XAQHfF5Op+F9roAG5V7o
I7+DReFroQ9PrGPq/fv5LjUtyn6GDKCvaSIgUn1+Fv/QzEZdyRSwZRtujEeQQ3xH
EbyYidVkTMdWbBwm/eUtQYxFgCyIlnugtbo3M7yZj9rVQ20dDbOGlK6l0SKxBy0r
l65frzgVGdtyGBufTateeCaPKZD2K5eFo0enHqSfzGUOK/wEPfwCvvcoxroFzwIg
Po+9JnHVwODsj8T15eveOnjgrcrlaz4jcWGo1FWeqr0XZrN/QmVb26wGzhnv1vPK
VdC0adxXWwpyfoWPqIpEonICt0ubfrxbUxEd+4fT7witj9FrzY8=
=6aU3
-----END PGP SIGNATURE-----