On 2021-06-02 00:56, Karl Berry wrote:
Hi Johan,
make --dry-run --always-make
I'm somehow amazed these two options work together at all. They seem
mutually unintelligible. In any case, it's the first time I've heard of
this, so I don't have a best (or any) practice to suggest. Sorry.
Maybe
I stumbled upon an issue when I recently switched to VSCode as editor.
I have several projects that have a full (medium-complex+) autotool
setup and they all work fine. However I discovered that VSCode in order
to initialize starts by running
make --dry-run --always-make
as first time initial
Thanks. I missed that at first pass.
Cheers!
On 2014-08-05 20:38, Russ Allbery wrote:
> Johan Persson writes:
>
>> Thanks for the confident boost that its not only me that stumbled upon this
>
>> However, I fail to see how the files that you have added to the &q
?
Cheers
On 2014-08-05 18:58, Russ Allbery wrote:
> Johan Persson writes:
>
>> The (non) solutions I have thought of (and rejected) are:
>
>> 1. Copy the resources into the staging path (with an extra recipe in the
>> makefile). Not a good idea since this gets comp
In my project I use Docbook t(with XSL stylesheets) o generate a user
manual which works fine. However I found myself in a conundrum when it
comes to handling all the paths so that the build works both when
building in the source tree and using a staged build (needed to have a
clean distcheck)
tell.
(This useful "trick" should really go into the autoconf/automake manual
since it is a generic way of handling absolute installation paths in
conjunction with distcheck)
Cheers!
On 2013-12-30 06:01, Russ Allbery wrote:
> Johan Persson writes:
>
>> As part of th
As part of the installation of a project I'm working on I want to
install a systemd service file which is created as part of the
configuration process (by autoconf).
Now I found myself in the situation where I can choose to have this work
either in real life or when I make "make distcheck" but
