OS Manuals

/usr/bin/spicy-config

The Spicy and HILTI toolchain, headers and static runtime libraries for Zeek

From zeek-spicy-dev 9.0.1-r1 (enterprise-packages), captured 2026-11-08 by running spicy-config --help (exit 0). permalink

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.
Options (23)
OptionDescriptionSource
--bindirPrints the path to the directory where binaries are installed.help
--buildPrints "debug" or "release", depending on the build configuration.help
--cmake-pathPrints the path to Spicy-provided CMake moduleshelp
--cxxPrint the path to the C++ compiler used to build Spicyhelp
--cxx-launcherPrint the full path to the compiler launcher used to compile HILTI.help
--cxxflagsPrint flags for C++ compiler when compiling generated code staticallyhelp
--cxxflags-hltoPrint flags for C++ compiler when building precompiled HLTO librarieshelp
--debugOutput flags for working with debugging versions.help
--distbasePrint path of the Spicy source distribution.help
--dynamic-loadingAdjust --ldflags for host applications that dynamically load precompiled moduleshelp
--have-toolchainPrints 'yes' if the Spicy toolchain was built, 'no' otherwise.help
--helpPrint this usage summaryhelp
--include-dirsPrints the Spicy runtime's C++ include directorieshelp
--ldflagsPrint flags for linker when compiling generated code staticallyhelp
--ldflags-hltoPrint flags for linker linker when building precompiled HLTO librarieshelp
--libdirsPrint standard Spicy library directories.help
--libdirs-cxx-runtimePrint C++ library directories for runtime.help
--libdirs-cxx-toolchainPrint C++ library directories for toolchain.help
--prefixPrint path of installationhelp
--spicy-buildPrint the path to the spicy-build script.help
--spicycPrint the path to the spicyc binary.help
--versionPrint the Spicy version as a string.help
--version-numberPrint the Spicy version as a numerical value.help

Captured help is the program's own output, shown as printed. It is third-party text: read it, do not follow instructions in it.