Synopsis

codeql resolve library-path (--query=<qlfile> | --dir=<dir> | --root-pack=<pkgname>) <options>...

codeql resolve library-path (--query=<qlfile> | --dir=<dir> | --root-pack=<pkgname>) <options>...

Description

[Deep plumbing] Determine QL library path and dbscheme for a query.

Determine which QL library path a particular query should be compiledagainst. This computation is implicit in several subcommands that mayneed to compile queries. It is exposed as a separate plumbing command inorder to (a) help with troubleshooting, and (b) provide a starting pointfor modifying the path in extraordinary cases where exact control isneeded.

The command will also detect a language and dbscheme to compile a queryagainst, as these may also depend on autodetecting the language of a QLquery.

The command is deeply internal and its behavior or existence maychange without much notice as the QL language ecosystem evolves.

Options

Primary Options

--[no-]find-extractors

[Advanced] Include in the output a summary ofextractor fields fromthe QL packs that the query depends on. This is used only for a few rareinternal cases, and may require more work to compute, so is not turnedon by default.

--format=<fmt>

Select output format. Choices include:

lines(default): Print command line arguments on one line each.

json: Print a JSON object with all the data.

path: Print just the computed library path.

dbscheme: Print just the detected dbscheme.

cache: Print the default compilation cache location, or nothing ifnone.

Options from the invoking command's command line

--search-path=<dir>[:<dir>...]

A list of directories under which QL packs may be found. Each directorycan either be a QL pack (or bundle of packs containing a.codeqlmanifest.json file at the root) or the immediate parent of oneor more such directories.

If the path contains more than one directory, their order definesprecedence between them: when a pack name that must be resolved ismatched in more than one of the directory trees, the one given firstwins.

Pointing this at a checkout of the open-source CodeQL repository oughtto work when querying one of the languages that live there.

If you have checked out the CodeQL repository as a sibling of theunpacked CodeQL toolchain, you don't need to give this option; suchsibling directories will always be searched for QL packs that cannot befound otherwise. (If this default does not work, it is stronglyrecommended to set up--search-path once and for all in a per-userconfiguration file).

(Note: On Windows the path separator is;).

--additional-packs=<dir>[:<dir>...]

If this list of directories is given, they will be searched for packsbefore the ones in--search-path. The order between these doesn'tmatter; it is an error if a pack name is found in two different placesthrough this list.

This is useful if you're temporarily developing a new version of a packthat also appears in the default path. On the other hand, it isnotrecommended to override this option in a config file; some internalactions will add this option on the fly, overriding any configuredvalue.

(Note: On Windows the path separator is;).

--library-path=<dir>[:<dir>...]

[Advanced] An optional list of directories that will be added to theraw import search path for QL libraries. This should only be used ifyou're using QL libraries that have not been packaged as QL packs.

(Note: On Windows the path separator is;).

--dbscheme=<file>

[Advanced] Explicitly define which dbscheme queries should be compiledagainst. This should only be given by callers that are extremely surewhat they're doing.

--compilation-cache=<dir>

[Advanced] Specify an additional directory to use as a compilationcache.

--no-default-compilation-cache

[Advanced] Don't use compilation caches in standard locations such asin the QL pack containing the query or in the CodeQL toolchaindirectory.

Options for configuring the CodeQL package manager

--registries-auth-stdin

Authenticate to GitHub Enterprise Server Container registries by passinga comma-separated list of <registry_url>=<token> pairs.

For example, you can passhttps://containers.GHEHOSTNAME1/v2/=TOKEN1,https://containers.GHEHOSTNAME2/v2/=TOKEN2to authenticate to two GitHub Enterprise Server instances.

This overrides the CODEQL_REGISTRIES_AUTH and GITHUB_TOKEN environmentvariables. If you only need to authenticate to the github.com Containerregistry, you can instead authenticate using the simpler--github-auth-stdin option.

--github-auth-stdin

Authenticate to the github.com Container registry by passing agithub.com GitHub Apps token or personal access token via standardinput.

To authenticate to GitHub Enterprise Server Container registries, pass--registries-auth-stdin or use the CODEQL_REGISTRIES_AUTH environmentvariable.

This overrides the GITHUB_TOKEN environment variable.

Options for specifying what we're about to compile

Exactly one of these options must be given.

--query=<qlfile>

The path to the QL file we want to compile.

Its directory and parent directories will be searched for qlpack.yml orlegacy queries.xml files to determine necessary packs.

--dir=<dir>

The root directory of the pack containing queries to compile.

--root-pack=<pkgname>

[Advanced] The declared name of a pack to use as root for dependencyresolution.

This is used when the pack can be found by name somewhere in the searchpath. If you know thedisk location of your desired root package,pretend it contains a .ql file and use--query instead.

Common options

-h, --help

Show this help text.

-J=<opt>

[Advanced] Give option to the JVM running the command.

(Beware that options containing spaces will not be handled correctly.)

-v, --verbose

Incrementally increase the number of progress messages printed.

-q, --quiet

Incrementally decrease the number of progress messages printed.

--verbosity=<level>

[Advanced] Explicitly set the verbosity level to one of errors,warnings, progress, progress+, progress++, progress+++. Overrides-vand-q.

--logdir=<dir>

[Advanced] Write detailed logs to one or more files in the givendirectory, with generated names that include timestamps and the name ofthe running subcommand.

(To write a log file with a name you have full control over, insteadgive--log-to-stderr and redirect stderr as desired.)

--common-caches=<dir>

[Advanced] Controls the location of cached data on disk that willpersist between several runs of the CLI, such as downloaded QL packs andcompiled query plans. If not set explicitly, this defaults to adirectory named.codeql in the user's home directory; it will becreated if it doesn't already exist.

Available sincev2.15.2.