Re: Making MKDIR_P Directory Rule like Emacs using ${trgdir}
Heime <[email protected]>
| Newsgroups | gmane.emacs.help |
|---|---|
| Message-ID | <J29T5dqB7V-w0ao5HTjz1EFeiC-p6lR2JPyx5RXCXa0Wq7T75kfAaOgPz8lNYg3wzgntda-qDcsmyWEs8ePW8Fx6ang4z9anefzc7yPaXYg=@protonmail.com> |
On Tuesday, April 28th, 2026 at 2:22 AM, [email protected] <[email protected]> wrote: > Heime <[email protected]> writes: > > > On Tuesday, April 28th, 2026 at 1:06 AM, Eli Zaretskii <[email protected]> wrote: > > > >> > Date: Mon, 27 Apr 2026 11:14:50 +0000 > >> > From: Heime <[email protected]> > >> > > >> > In the Emacs documentation makefile, this makes the directory > >> > where the resulting emacs.info file is placed > >> > > >> > MKDIR_P = @MKDIR_P@ > >> > ${buildinfodir}: > >> > ${MKDIR_P} $@ > >> > > >> > In my case, I want the info file to exist in the build directory > >> > target stored in trgdir. What recipe shall I use to make > >> > trgdir if it does not exist? > >> > > >> > ${trgdir}: > >> > ${MKDIR_P} $@ > >> > >> Yes. > > > > What is ${MKDIR_P} and what command is it? > > > > 1. It is set by autoconf. There is a mailing list for > questions about it here: > > https://lists.gnu.org/mailman/listinfo/autoconf/ > > "The list can be used to discuss the Autoconf build > system. The discussion can range from simple "how-to" > questions up to future directions for this tool." > > [email protected] I do not plan to use Autoconf because the documentation has no specific operating system settings. > 2. An alternative is not to use the Emacs files because they > are large and complex. Instead, use the ‘make’ user > manual (Info or man) and write simple recipes, asking > questions as needed at the ‘make’ mailing list. Yes, but I am using to help me, but without using Autoconf. Would a standard mkdir command do what is needed? > -- > The lyf so short, the craft so long to lerne. > - Geoffrey Chaucer, The Parliament of Birds. > >