Jordan Santell [:jsantell] [@jsantell] Reporter
	Description • 9 years ago

When adding a module to moz.build, a `./mach build devtools/client/TOOL` does not build the module, resulting in things like:

Error: Module `resource://devtools/client/memory/components/frame.js` is not found at resource://devtools/client/memory/components/frame.js

It requires a top level `./mach build` to handle this. Seems similar to bug 1219077, not intuitive that this is needed when adding modules.

	J. Ryan Stinnett [:jryans] (Use needinfo, replies may be slow) Assignee
	Comment 1 • 9 years ago

I'll take a look.

	J. Ryan Stinnett [:jryans] (Use needinfo, replies may be slow) Assignee
	Comment 2 • 9 years ago

Looks like this is a regression from our move to resource://devtools in bug 1203159.  By using switching to FINAL_TARGET_FILES, we lost per-directory build dependencies.

	J. Ryan Stinnett [:jryans] (Use needinfo, replies may be slow) Assignee
	Comment 3 • 9 years ago

In bug 1203159, we changed DevTools to package all resources as a flattened
add-on via FINAL_TARGET_FILES.  However, this build variable did not emit
per-directory dependency data, so we lost the ability to build only one targeted
directory.  By changing FINAL_TARGET_FILES to emit similar info to other build
variables, we get the dependency tracking back.

Still needs tests, but does this seem reasonable?

	Mike Hommey [:glandium]
	Comment 4 • 9 years ago

Comment on attachment 8680328 [details] [diff] [review]
final-target-deps

Review of attachment 8680328 [details] [diff] [review]:
-----------------------------------------------------------------

This would be a clear regression. Please just stop using `mach build foo/bar` and expect things to keep working. Use `mach build faster`.

	Nick Fitzgerald [:fitzgen] [⏰PST; UTC-8]
	Comment 5 • 9 years ago

(In reply to Mike Hommey [:glandium] from comment #4)
> Comment on attachment 8680328 [details] [diff] [review]
> final-target-deps
> 
> Review of attachment 8680328 [details] [diff] [review]:
> -----------------------------------------------------------------
> 
> This would be a clear regression. Please just stop using `mach build
> foo/bar` and expect things to keep working. Use `mach build faster`.

What about directories that have both cpp and js changes, eg devtools/shared/heapsnapshot?

	Mike Hommey [:glandium]
	Comment 6 • 9 years ago

`mach build faster` then `mach build binaries` ; or `mach build faster binaries`