Message-ID: <6861c883@news.ausics.net>
From: not@telling.you.invalid (Computer Nerd Kev)
Subject: Re: Software Building Status. A Growing Annoyance.
Newsgroups: comp.os.linux.misc,comp.os.linux.advocacy
References: <pan$be9fc$809aad21$e409cc51$526fec52@linux.rocks> <685b2f8b@news.ausics.net> <pan$62870$3f1354bc$ea5e799$d7ff5329@linux.rocks>
User-Agent: tin/2.0.1-20111224 ("Achenvoir") (UNIX) (Linux/2.4.31 (i586))
NNTP-Posting-Host: news.ausics.net
Date: 30 Jun 2025 09:13:07 +1000
Organization: Ausics - https://newsgroups.ausics.net
Lines: 35
X-Complaints: abuse@ausics.net
Path: news.eternal-september.org!eternal-september.org!feeder3.eternal-september.org!news.bbs.nz!news.ausics.net!not-for-mail

In comp.os.linux.misc Nux Vomica <nv@linux.rocks> wrote:
> On 25 Jun 2025 09:06:52 +1000, Computer Nerd Kev wrote:
>> The CMake developers ignored requests for an equivalent to
>> "./configure --help" early on, willfully making the transition
>> difficult for software builders.
> 
> Actually, Cmake does have an equivalent.  Here are the steps.
> 
> 1) Unpack a source file.
> 
> 2) Create a "build" directory in the source root and then
> "cd build."
> 
> 3) Execute "cmake -LAH .. "
> 
> This will produce a LONG list of options.  (See the output
> for Pan below.)

That looks similar to what I've been doing which is reading
CMakeCache.txt. Hard to read with none of the sorting between
different types of options like you get with "./configure --help".
More like editing Makefiles manually, and even projects where you
have to do that usually write more detail in the comments before
variables than many of these CMake projects tend to have.

This comment in your example is _really_ descriptive:

> // Path to a program.
> CMAKE_TAPI:FILEPATH=CMAKE_TAPI-NOTFOUND

So it didn't find "a program". Great, thanks...

-- 
__          __
#_ < |\| |< _#