On Fri, Mar 29, 2019 at 11:29:17AM -0500, Bruce Dubbs via blfs-dev wrote:
> On 3/29/19 9:30 AM, Brendan L via blfs-dev wrote:
> > On Fri, Mar 29, 2019 at 9:20 AM Ken Moffat via blfs-dev
> > <[email protected]> wrote:
> > >
> > > Does cmake have anything equivalent to old-style 'configure --help'
> > > or meson's configure, which would allow a user to see the options
> > > they might wish to set ?
> > >
> > > Googling suggests cmake -LAH, but that *runs* the configuring and
> > > then lists the values of internal variables.
> > >
> >
> > cmake -LAH is all that I have found too. Not very user friendly.
>
> What is wrong with cmake -LAH? It does run the configuring code but does
> not create any files needed for the build. It lists all the variables used
> and their default settings. Usually you can figure out the meaning of the
> setting from the name.
>
> -- Bruce
>
excerpts:
-- Cache values
// Path to a program.
APPSTREAMCLI:FILEPATH=APPSTREAMCLI-NOTFOUND
// Build the project with gcov support
BUILD_COVERAGE:BOOL=OFF
// If enabled, shared libs will be built by default, otherwise static libs
BUILD_SHARED_LIBS:BOOL=TRUE
// Build the testing tree.
BUILD_TESTING:BOOL=ON
// Path to a program.
CMAKE_AR:FILEPATH=/usr/bin/ar
// Choose the type of build, options are: None Debug Release RelWithDebInfo
MinSizeRel ...
CMAKE_BUILD_TYPE:STRING=
// Enable/Disable color output during build.
CMAKE_COLOR_MAKEFILE:BOOL=ON
// CXX compiler
CMAKE_CXX_COMPILER:FILEPATH=/usr/bin/c++
// A wrapper around 'ar' adding the appropriate '--plugin' option for the GCC
compiler
CMAKE_CXX_COMPILER_AR:FILEPATH=/usr/bin/gcc-ar
// A wrapper around 'ranlib' adding the appropriate '--plugin' option for the
GCC compiler
CMAKE_CXX_COMPILER_RANLIB:FILEPATH=/usr/bin/gcc-ranlib
// Flags used by the CXX compiler during all build types.
CMAKE_CXX_FLAGS:STRING=-O2 -march=native
[...]
// The directory containing a CMake configuration file for Qt5.
Qt5_DIR:PATH=/opt/qt5/lib/cmake/Qt5
// Path to a file.
XCB_UTIL_INCLUDE_DIR:PATH=/usr/include
// Path to a library.
XCB_UTIL_LIBRARY:FILEPATH=/usr/lib/libxcb-util.so
// Path to a file.
XCB_XCB_INCLUDE_DIR:PATH=/usr/include
// Path to a library.
XCB_XCB_LIBRARY:FILEPATH=/usr/lib/libxcb.so
// Path to a library.
pkgcfg_lib_PKG_XCB_UTIL_xcb:FILEPATH=/usr/lib/libxcb.so
// Path to a library.
pkgcfg_lib_PKG_XCB_UTIL_xcb-util:FILEPATH=/usr/lib/libxcb-util.so
// Path to a library.
pkgcfg_lib_PKG_XCB_XCB_xcb:FILEPATH=/usr/lib/libxcb.so
// Path to a library.
pkgcfg_lib__OPENSSL_crypto:FILEPATH=/usr/lib/libcrypto.so
// Path to a library.
pkgcfg_lib__OPENSSL_ssl:FILEPATH=/usr/lib/libssl.so
Now I grant you that a *few* of those may be useful, but I regard
it as pretty nasty.
ĸen
--
It is said that there are two great unsolved problems in computer
science: naming, cache invalidation, and off-by-one errors.
-- Ben Bullock
--
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
