OS Manuals

/usr/bin/hilti-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 hilti-config --help (exit 0). permalink

Usage: hilti-config [options]

Available options:

    --build                  Prints "debug" or "release", depending on the build configuration.
    --cxx                    Print the full path to the compiler used to compile HILTI.
    --cxx-launcher           Print the full path to the compiler launcher used to compile HILTI.
    --cxxflags               Print C++ flags when compiling generated code statically
    --cxxflags-hlto          Print C++ flags when building precompiled HLTO libraries
    --debug                  Output flags for working with debugging versions.
    --distbase               Print path of the HILTI source distribution.
    --dynamic-loading        Adjust --ldflags for host applications that dynamically load precompiled modules
    --help                   Print this usage summary
    --hiltic                 Print the full path to the hiltic binary.
    --include-dirs           Prints the HILTI runtime's C++ include directories
    --include-dirs-toolchain Prints the Spicy compiler's C++ include directories
    --ldflags                Print linker flags when compiling generated code statically
    --ldflags-hlto           Print linker flags when building precompiled HLTO libraries
    --libdirs                Print standard HILTI 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.
    --have-toolchain         Prints 'yes' if the HILTI toolchain was built, 'no' otherwise.
    --version                Print HILTI version.

    --using-build-dir        Returns true when hilti-config's output is referring to the build directory;
                             and false when referring to the installation
Options (20)
OptionDescriptionSource
--buildPrints "debug" or "release", depending on the build configuration.help
--cxxPrint the full path to the compiler used to compile HILTI.help
--cxx-launcherPrint the full path to the compiler launcher used to compile HILTI.help
--cxxflagsPrint C++ flags when compiling generated code staticallyhelp
--cxxflags-hltoPrint C++ flags when building precompiled HLTO librarieshelp
--debugOutput flags for working with debugging versions.help
--distbasePrint path of the HILTI source distribution.help
--dynamic-loadingAdjust --ldflags for host applications that dynamically load precompiled moduleshelp
--helpPrint this usage summaryhelp
--hilticPrint the full path to the hiltic binary.help
--include-dirsPrints the HILTI runtime's C++ include directorieshelp
--ldflagsPrint linker flags when compiling generated code staticallyhelp
--ldflags-hltoPrint linker flags when building precompiled HLTO librarieshelp
--libdirsPrint standard HILTI library directories.help
--libdirs-cxx-runtimePrint C++ library directories for runtime.help
--libdirs-cxx-toolchainPrint C++ library directories for toolchain.help
--prefixPrint path of installation.help
--have-toolchainPrints 'yes' if the HILTI toolchain was built, 'no' otherwise.help
--versionPrint HILTI version.help
--using-build-dirReturns true when hilti-config's output is referring to the build directory;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.