Thread overview
Using the LDC code cache with debug and release
Jul 07, 2023
Cecil Ward
Nov 20
Johan
July 07, 2023
When you use the —cache=  option eg —cache=~/.ldccache/  do you need to differentiate with distinct paths for release and debug-build object files, or does LDC just do the right thing somehow? I thought about making the path to the cache directory different for release and debug builds. I already keep the object files in different directories to prevent debug and release builds from overwriting each other.
November 20

On Friday, 7 July 2023 at 19:00:05 UTC, Cecil Ward wrote:

>

When you use the —cache= option eg —cache=~/.ldccache/ do you need to differentiate with distinct paths for release and debug-build object files, or does LDC just do the right thing somehow? I thought about making the path to the cache directory different for release and debug builds. I already keep the object files in different directories to prevent debug and release builds from overwriting each other.

specify a cache directory where LDC will store compiled object files for faster compilation times in subsequent builds.
https://spacebarclicker.co

November 20
On Friday, 7 July 2023 at 19:00:05 UTC, Cecil Ward wrote:
> When you use the —cache=  option eg —cache=~/.ldccache/  do you need to differentiate with distinct paths for release and debug-build object files

No, you can use the same cache.

> , or does LDC just do the right thing somehow?

Yes it does. Any commandline flag that changes object file output results in a different cache entry.

-Johan