Okay, thank you! I'll try that.

Hello, first time porter here.

Porting to the Pixel 3 (blueline) has been somewhat confusing as the kernel and whatnot is mixed in with the Pixel 3 XL (crosshatch).

I'm currently stuck on the Halium build step.
I'm not sure how to format my progress, so I'll just dump my progress so that I don't miss anything.

I'm having problem finding the kernel configuration. It should be in the BoardConfig.mk file, but crosshatch and blueline appear to share one under BoardConfig-common.mk (device/google/crosshatch/blueline/BoardConfig.mk has the statement: include device/google/crosshatch/BoardConfig-common.mk)

I've omitted the steps for syncing the repo.
My manifest (google_blueline.xml) is as follows

<?xml version="1.0" encoding="UTF-8"?>
<manifest>
        <project path="device/google/blueline" name="android_device_google_blueline" remote="los" />
        <project path="device/google/crosshatch" name="android_device_google_crosshatch" remote="los" />
        <remote name="los" fetch="https://github.com/LineageOS" />
</manifest>

Do I need to add a line to fetch android_kernel_google_crosshatch? I'm confused.

Running: halium/devices/setup blueline ran with no errors.
Running: hybris-patches/apply-patches.sh --mb ran with no errors.

I extracted the vendor blobs using the extract-files.sh in the crosshatch device folder (blueline's links to that one).
It starts differing after I ran source build/envsetup.sh:

including device/google/crosshatch/vendorsetup.sh
including vendor/lineage/vendorsetup.sh

I'm missing a few lines that are shown in the guide.

Since the BoardConfig for blueline includes BoardConfig-common for crosshatch, I ran grep "TARGET_KERNEL_CONFIG" device/google/crosshatch/BoardConfig-common.mk with no results.
Am I missing something? Sorry if this should be obvious.

Thanks in advance.