Caching build objects: Waf and ccache

[Thomas Nagy]

Are you looking for general instructions or are you trying to optimize the rtems build?

To wrap the compiler using ccache, override the environment variables during the configuration:
CXX='ccache gxx' CC='ccache gcc' waf configure

The rtems manual does not advertise it, so it this may void your warranty:
CC="ccache /home/user/quick-start/rtems/6/bin/sparc-rtems6-gcc" ./waf configure --prefix=$HOME/quick-start/rtems/6

The wafcache extension is a different system: if the wafcache.py is added to a project (it is not a default option yet), all build results (link, results, manual pages) become shareable using a filesystem directory or over the network. It is probably unnecessary to import it in rtems unless you are addressing a specific performance issue.

Thomas

On Tue, 5 Oct 2021 11:17:26 +0200, Stanislav Pankevich <s.pankevich at gmail.com> wrote:

> Hello everyone,
> 
> I have a very specific question about the Waf build system. I apologize if
> I missed this information somewhere in the documentation.
> 
> From looking at ./waf --help it doesn't look like Waf would have a
> ccache-like functionality built in.
> 
> When using CMake build system, I am used to providing
> 
> -DCMAKE_CXX_COMPILER_LAUNCHER=ccache
> 
> that makes CMake switch to using ccache. Is there an equivalent option for
> Waf or is there a native way in Waf for caching object artifacts?
> 
> Thank you,
> 
> Stanislav
> _______________________________________________
> users mailing list
> users at rtems.org
> http://lists.rtems.org/mailman/listinfo/users