LGTM新手求助：自定义Package在构建配置中的配置方法问询

Hey there! I’ve helped set up similar custom dependency builds for LGTM before, so let’s walk through how to map your package_a workflow to LGTM’s build stages properly.

First, let’s recap LGTM’s key build phases to understand where each step fits:

• Prepare: This phase is for fetching dependencies, downloading source code, or extracting archives—perfect for your curl and tar steps.
• Configure: Use this phase to set up build configurations for dependencies or your main project, which matches your ./waf configure step.
• Index: LGTM handles this automatically to analyze your code; you just need to make sure built artifacts are accessible to the main project.

Now, let’s translate your package_a build steps into a working .lgtm.yml configuration. Here’s the full setup:

extraction:
  cpp:
    prepare:
      - curl -L https://github.com/developer/package_a/archive/package_a_v0.1.1.tar.gz --output package_a_v0.1.1.tar.gz
      - mkdir -p package_a
      - tar -xvzf package_a_v0.1.1.tar.gz -C package_a --strip-components=1
    configure:
      - cd package_a && ./waf configure --prefix=$LGTM_WORKSPACE/install
      - cd package_a && ./waf build install
    index:
      environment:
        # Tell your main project where to find package_a's headers and libraries
        CFLAGS: "-I$LGTM_WORKSPACE/install/include"
        LDFLAGS: "-L$LGTM_WORKSPACE/install/lib"
        PKG_CONFIG_PATH: "$LGTM_WORKSPACE/install/lib/pkgconfig:$PKG_CONFIG_PATH"

Let’s break down each part:

1. Prepare Phase:

   • We download the tarball, create the target directory, and extract the source into package_a (using --strip-components=1 to avoid nesting the source in a versioned subfolder, which keeps the build path cleaner).

2. Configure Phase:

   • We run ./waf configure with a --prefix pointing to a directory inside LGTM’s workspace ($LGTM_WORKSPACE is a built-in variable for the project root). This ensures the installed files stay within the build environment and are accessible later.
   • Then we run ./waf build install—no sudo needed here! LGTM runs builds in an isolated, non-privileged container, so system-wide installs aren’t allowed (and aren’t necessary, since we’re using a local prefix).

3. Index Phase Environment Variables:

   • We set CFLAGS, LDFLAGS, and PKG_CONFIG_PATH to point to the local install directory of package_a. This tells your main project’s build system exactly where to find the headers and libraries it needs to link against.

A few extra tips:

• If your main project uses waf as well, you might need to adjust its configure step to explicitly look for package_a in the local install path.
• Test the configuration locally first if you can—simulate the LGTM environment using an isolated container (like Docker) and run the steps in order to catch any issues early.
• If package_a requires additional system dependencies, add apt install commands in the prepare phase (e.g., - apt-get update && apt-get install -y libfoo-dev).

内容的提问来源于stack exchange，提问作者Szpak