On Sun, 20 Apr 2014, John D. Baker wrote: > My update (-u) release builds seem always to rebuild freetype and friends > even though nothing has changed. In fact, if I run two identical builds > with no intervening cvs update, freetype and related items will be rebuilt > both times. > > Does anyone else see this? Is it deliberate?
I did not see this; I built a distribution last night and an update distribution this morning, then an update release on top of that and it has not built freetype again.. however, % grep '===>.*freetype' build.log obj ===> external/mit/xorg/lib/freetype obj ===> external/mit/xorg/lib/freetype/freetype obj ===> external/mit/xorg/lib/freetype/freetype/config includes ===> external/mit/xorg/lib/freetype includes ===> external/mit/xorg/lib/freetype/freetype includes ===> external/mit/xorg/lib/freetype/freetype/config dependall ===> external/mit/xorg/lib/freetype dependall ===> external/mit/xorg/lib/freetype/freetype dependall ===> external/mit/xorg/lib/freetype/freetype/config install ===> external/mit/xorg/lib/freetype install ===> external/mit/xorg/lib/freetype/freetype install ===> external/mit/xorg/lib/freetype/freetype/config dependall ===> external/mit/xorg/lib/freetype dependall ===> external/mit/xorg/lib/freetype/freetype dependall ===> external/mit/xorg/lib/freetype/freetype/config install ===> external/mit/xorg/lib/freetype install ===> external/mit/xorg/lib/freetype/freetype install ===> external/mit/xorg/lib/freetype/freetype/config it descends into the freetype directory more than once; this is likely because it builds this first as a lib, then just passes through while building xorg .. regards, iain
