(no longer active) Reporter
	Description • 11 years ago

If you do a clean build, and then do another one right away, the following files seem to be rebuilt unnecessarily:

 0:46.43 nsChromeRegistry.cpp
 0:51.13 XPCComponents.cpp
 0:51.15 nsXPConnect.cpp
 2:02.54 webapprt.mm
 2:14.72 nsBrowserApp.cpp

The first three cause libxul to be relinked again.

	Gregory Szorc [:gps]
	Comment 1 • 11 years ago

$ mach build -v chrome/src
 0:00.65 /usr/bin/make -C chrome/src -j8
 0:00.99 /usr/bin/make export
 0:00.99 if test -d ../../dist/bin/browser ; then touch ../../dist/bin/browser/.purgecaches ; fi
 0:01.00 if test -d ../../dist/bin/webapprt ; then touch ../../dist/bin/webapprt/.purgecaches ; fi
 0:01.01 make[1]: Nothing to be done for `export'.
 0:01.01 /usr/bin/make libs
 0:01.14 make[1]: Nothing to be done for `libs'.
 0:01.15 /usr/bin/make tools
 0:01.17 make[1]: Nothing to be done for `tools'.

I guess I'll need to build on Windows to find out why the dependencies there are causing it to get rebuilt.

	(no longer active) Reporter
	Comment 2 • 11 years ago

(In reply to comment #1)
> $ mach build -v chrome/src
>  0:00.65 /usr/bin/make -C chrome/src -j8
>  0:00.99 /usr/bin/make export
>  0:00.99 if test -d ../../dist/bin/browser ; then touch
> ../../dist/bin/browser/.purgecaches ; fi
>  0:01.00 if test -d ../../dist/bin/webapprt ; then touch
> ../../dist/bin/webapprt/.purgecaches ; fi
>  0:01.01 make[1]: Nothing to be done for `export'.
>  0:01.01 /usr/bin/make libs
>  0:01.14 make[1]: Nothing to be done for `libs'.
>  0:01.15 /usr/bin/make tools
>  0:01.17 make[1]: Nothing to be done for `tools'.
> 
> I guess I'll need to build on Windows to find out why the dependencies there
> are causing it to get rebuilt.

FWIW I see this on Mac.

	:Ms2ger (he/him; ⌚ UTC+1/+2)
	Comment 3 • 11 years ago

(In reply to Gregory Szorc [:gps] from comment #1)
> $ mach build -v chrome/src

It probably requires a top-level build.

	(no longer active) Reporter
	Comment 4 • 11 years ago

(In reply to comment #3)
> (In reply to Gregory Szorc [:gps] from comment #1)
> > $ mach build -v chrome/src
> 
> It probably requires a top-level build.

Oh, yes.  It does.

	Gregory Szorc [:gps]
	Comment 5 • 11 years ago

It's probably the result of us blowing away parts of dist/ at the beginning of a build and invalidating mtimes when a file is copied (not symlinked) into dist/. That is in turn probably due to some one-off install/copy rule that isn't INSTALL_TARGETS. But this is only speculation.