You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you want make to be efficient, try to make sure that file targets always depend on other file targets
In the build/marman-linux target, we're depending on a pseudo-target, deps which means the go build will always be run again, despite there being nothing to do.
OR we can establish a file target for deps using the temp/tags trick but that's not always feasable.
This isn't an immediate issue, in that building our go apps is pretty fast, but it can balloon out and cause friction when later you decide to add a slower pre-processing action to your builds.
The text was updated successfully, but these errors were encountered:
squeedee
pushed a commit
to cf-platform-eng/mrreport
that referenced
this issue
Jul 10, 2019
- not quite idiomatic because 'packr2 build' should preclude needing 'go build'
- could not make that work
- added 'packr2 build' as file targets
- added documentation to help when working with packr
- made builds a little more efficient, see cf-platform-eng/marman#3
Co-authored-by: Pete Wall <[email protected]>
[#165363463]
marman/Makefile
Line 47 in 6452f7f
Today I learnt (or realised something i knew but haven't been applying):
This is a file target
This is a pseudo-target
If you want make to be efficient, try to make sure that file targets always depend on other file targets
In the
build/marman-linux
target, we're depending on a pseudo-target,deps
which means thego build
will always be run again, despite there being nothing to do.the fix is to move
deps
to the pseudo target:OR we can establish a file target for deps using the
temp/tags
trick but that's not always feasable.This isn't an immediate issue, in that building our go apps is pretty fast, but it can balloon out and cause friction when later you decide to add a slower pre-processing action to your builds.
The text was updated successfully, but these errors were encountered: