On 2024-05-14 17:02, Bob Friesenhahn wrote:
> Since it is not allowed to wrap a target replacement in an Automake
> condition, I am finding it necessary to write new rules which use
> variables that I define.
I think it works despite the strange warning about multiple targets?
But regardless,
On 5/13/24 20:52, Bruno Haible wrote:
Bob Friesenhahn wrote:
Automake does have a critical bug in that for a target which only optionally
has C++ sources, that target is always linked using C++. Without this issue,
the trick of including an empty optional C++ source file in the build would
Bob Friesenhahn wrote:
> Automake does have a critical bug in that for a target which only optionally
> has C++ sources, that target is always linked using C++. Without this issue,
> the trick of including an empty optional C++ source file in the build would
> work. But I do not want
On 5/13/24 16:37, Karl Berry wrote:
convince Automake to force libtool to link using the C++ compiler
When there are no C++ sources? Why? Just trying to understand ...
There are no C++ sources from my project, but there is a C++ compiler
used for the overall build. As clarification, this
convince Automake to force libtool to link using the C++ compiler
When there are no C++ sources? Why? Just trying to understand ...
I'm sorry Bob, but I just don't know. Maybe the just-released
libtool-2.5.0 alpha offers some new help?
If there is some bug in or feature for Automake that
I have expended quite a few days already (over a 6 month span) with
attempting to convince Automake to force libtool to link using the C++
compiler. I tried optionally adding an empty C++ source file to the
target build but this does not work because then Automake always assumes
C++ linkage,
