Standardize NO_CCACHE flag and ccache definitions

Martin Tournoij carpetsmoker at rwxrwxrwx.net
Sat Jun 21 15:21:02 UTC 2008


On Sat, Jun 21, 2008 at 01:32:20AM +0100, RW wrote:
> On Wed, 18 Jun 2008 23:27:16 +0200
> Martin Tournoij <carpetsmoker at rwxrwxrwx.net> wrote:
> 
> > There are some ports which refuse to compile with ccache, these all
> > seem to be projects which use scons, unlike make, scons does not copy
> > the user's environment automatically, and the required environment
> > variables for ccache (like CCACHE_DIR) aren't present, which leads to
> > build failure, an example is games/freera.
> > 
> > I'm not that familiar with scons, and what exactly the "proper way" is
> > to handle this sort of stuff in scons, 
> 
> I don't have any experience with scons, but I did used to use cons.
> IIRC cons expects to do the caching itself. Since it already generates a
> hash that can be used to label the correct object file, it pretty much
> comes for free and running ccache would just duplicate the overheads. I
> think it's probable that there isn't a "proper way".

It's not quite the same, scons' cache feature needs to be explicitly
enabled in the SConstruct file, I don't think many projects have it
enabled...
See the scons manual:
http://www.scons.org/doc/0.98.5/HTML/scons-user/c3143.html

A NO_CCACHE might be useful for ports that do have this cache enabled,
but are there any ports at all which use this?

As a sidenote, AFAIK cons and scons are not related...

-- 
Martin Tournoij
carpetsmoker at rwxrwxrwx.net
http://www.daemonforums.org

QOTD:
The fact that Hitler was a political genius unmasks the nature of
politics in general as no other can.
		-- Wilhelm Reich


More information about the freebsd-ports mailing list