Output path to .so

[pboling]

I just installed a bunch of parsers and am not sure where they were placed, but they didn't go to the paths setup as, e.g.: TREE_SITTER_BASH_PATH, TREE_SITTER_JSON_PATH, etc.

I need to set these paths for tools to work... If I can find it in the source I'll submit a PR. Thanks for this tool!

[pboling]

The solution, until there is output telling people where the .so went is:

➜  tsdl config current
build-dir = "tmp"
force = false
fresh = false
jobs = 22
out-dir = "parsers"
prefix = "libtree-sitter-"
show-config = false
target = "native"
unlock = false

[tree-sitter]
version = "0.26.5"
platform = "linux-x64"
repo = "https://github.com/tree-sitter/tree-sitter"

And then finding the out-dir, which is in parsers in the PWD. :)

[stackmystack]

Hi @pboling,

$ tsdl build --help
Build one or many parsers

Usage: tsdl build [OPTIONS] [LANGUAGES]...

Arguments:
  [LANGUAGES]...  Parsers to compile.

Options:
  -b, --build-dir <BUILD_DIR>
          Build Directory [env: TSDL_BUILD_DIR=] [default: tmp]
      --force
          Force clone the repository and rebuild, bypassing cache checks. Overwrites existing binaries
  -f, --fresh
          Clears the `build-dir` and starts a fresh build
  -c, --config <CONFIG>
          Path to the config file (TOML) [env: TSDL_CONFIG=] [default: parsers.toml]
  -j, --jobs <JOBS>
          Number of threads; defaults to the number of available CPUs [env: TSDL_NCPUS=] [default: 8]
  -l, --log <LOG>
          Path to the logging file. If unspecified, it will go to `build-dir/log` [env: TSDL_LOG=]
  -o, --out-dir <OUT_DIR>
          Output Directory [env: TSDL_OUT_DIR=] [default: parsers]
      --log-color <LOG_COLOR>
          Whether to emit colored logs [default: auto] [possible values: auto, no, yes]
  -p, --prefix <PREFIX>
          Prefix parser names [env: TSDL_PREFIX=] [default: libtree-sitter-]
      --progress <PROGRESS>
          Progress style [default: auto] [possible values: auto, fancy, plain]
      --show-config
          Show Config
  -t, --target <TARGET>
          Build target [default: native] [possible values: native, wasm, all]
  -v, --verbose...
          Increase logging verbosity
  -q, --quiet...
          Decrease logging verbosity
  -V, --tree-sitter-version <VERSION>
          Tree-sitter version [default: 0.26.5]
      --tree-sitter-platform <PLATFORM>
          Tree-sitter platform to build. Change at your own risk [default: linux-x64]
  -R, --tree-sitter-repo <REPO>
          Tree-sitter repo [default: https://github.com/tree-sitter/tree-sitter]
      --unlock
          Force unlock the build directory
  -h, --help

You can either pass an argument directly, or use the configuration file. tsdl config can show you the default or the currently active config (mix of the config file + defaults + command-line param):

$ tsdl config --help
Configuration helpers

Usage: tsdl config [OPTIONS] <COMMAND>

Commands:
  current
  default
  help     Print this message or the help of the given subcommand(s)

Options:
  -c, --config <CONFIG>        Path to the config file (TOML) [env: TSDL_CONFIG=] [default: parsers.toml]
  -l, --log <LOG>              Path to the logging file. If unspecified, it will go to `build-dir/log` [env: TSDL_LOG=]
      --log-color <LOG_COLOR>  Whether to emit colored logs [default: auto] [possible values: auto, no, yes]
      --progress <PROGRESS>    Progress style [default: auto] [possible values: auto, fancy, plain]
  -v, --verbose...             Increase logging verbosity
  -q, --quiet...               Decrease logging verbosity
  -h, --help                   Print help

[pboling]

Yeah, those are great helps if someone runs them. I was going at it from the perspective of someone who didn't use a config, or any arguments, and ran a build command for the first time and then wondered where the .so went (because that's what I did!). It could be helpful to have that in the output of the task.