zeek/auxil/spicy/doc/examples/_usage-spicy-config.output
Patrick Kelley 8fd444092b initial
2025-05-07 15:35:15 -04:00

32 lines
2.0 KiB
Plaintext

# Automatically generated; do not edit. -- <HASH> spicy-config -h//False
Usage: spicy-config [options]
Available options:
--bindir Prints the path to the directory where binaries are installed.
--build Prints "debug" or "release", depending on the build configuration.
--cmake-path Prints the path to Spicy-provided CMake modules
--cxx Print the path to the C++ compiler used to build Spicy
--cxx-launcher Print the full path to the compiler launcher used to compile HILTI.
--cxxflags Print flags for C++ compiler when compiling generated code statically
--cxxflags-hlto Print flags for C++ compiler when building precompiled HLTO libraries
--debug Output flags for working with debugging versions.
--distbase Print path of the Spicy source distribution.
--dynamic-loading Adjust --ldflags for host applications that dynamically load precompiled modules
--have-toolchain Prints 'yes' if the Spicy toolchain was built, 'no' otherwise.
--help Print this usage summary
--include-dirs Prints the Spicy runtime's C++ include directories
--include-dirs-toolchain Prints the Spicy compiler's C++ include directories
--ldflags Print flags for linker when compiling generated code statically
--ldflags-hlto Print flags for linker linker when building precompiled HLTO libraries
--libdirs Print standard Spicy library directories.
--libdirs-cxx-runtime Print C++ library directories for runtime.
--libdirs-cxx-toolchain Print C++ library directories for toolchain.
--prefix Print path of installation
--spicy-build Print the path to the spicy-build script.
--spicyc Print the path to the spicyc binary.
--version Print the Spicy version as a string.
--version-number Print the Spicy version as a numerical value.