Incremental compilation cost too much time when network is not stable, is there any way to avoid depending network to build?

[1401459387]

this step use too much time when network is not stable. Usually, it takes me 30 minutes to compile benchmark, This is unacceptable.

[1401459387]

Additionally, i use build.sh to compile benchmark.

[sleeepyjack]

Hi,
Thanks for reaching out.

You can enable local source caching by setting the environment variable CPM_SOURCE_CACHE (see link). You still need to configure the project once to populate the cache but subsequent builds will use the cached source rather than re-downloading them.
Let me know if that solves your problem.

You probably also want to disable downloading the test data for the roaring_bitmap tests. You can do so by specifying the corresponding feature flag to the build.sh call: ci/build.sh -b -- -DCUCO_DOWNLOAD_ROARING_TESTDATA=OFF (anything after -- will be forwarded directly to cmake).

[1401459387]

Thanks, but this method seems to not work. It seems to have made build cache valid, but another question stops my building process. It is likely about nlohmann_json, but ican't solve it.

[sleeepyjack]

I just tested the setup locally following the instructions and it worked for me. This is how my cache looks like:

.cache/cpm
├── cccl
│   ├── a65d
│   ├── a65d.hash
│   ├── a65d.lock
│   └── cmake.lock
├── cpm
│   └── CPM_0.42.0.cmake
├── fmt
│   ├── cmake.lock
│   ├── dbab
│   ├── dbab.hash
│   └── dbab.lock
├── nlohmann_json
│   ├── 0889
│   ├── 0889.hash
│   ├── 0889.lock
│   └── cmake.lock
└── nvbench
    ├── 5a0a
    ├── 5a0a.hash
    ├── 5a0a.lock
    └── cmake.lock

Maybe nlohmann_json didn't download properly?
@robertmaynard any ideas what could cause this?