• Cecil Ward (7/7) Jul 07 2023 When you use the —cache= option eg —cache=~/.ldccache/ do you
• whileclove (4/11) Nov 20 2023 specify a cache directory where LDC will store compiled object
• Johan (5/9) Nov 20 2023 Yes it does. Any commandline flag that changes object file output

Cecil Ward <cecil cecilward.com> writes:

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.

whileclove <whileclove gmail.com> writes:

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

Johan <j j.nl> writes:

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