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
Currently dependency build order is defined (almost) explicitly by the order they appear in Project.meta file. With the parallel build support the order becomes crucial for total build duration, so it would make sense to release user from this optimization burden by letting bake figure out the optimal order. For example bake could prioritize targets with "sync points" and long running targets (could be hinted with a special keyword?).
Caution is needed to not break backward compatibility, eg. by breaking the include path order. Maybe include path order could still follow the "written" dependency order while the build order could be determined by bake?
The text was updated successfully, but these errors were encountered:
hbragge
changed the title
Let bake determine the dependency build order
Let bake determine optimal build order
Mar 31, 2017
Hi, thanks for info, worth looking at, maybe it removes the need to building "sync point" targets in the beginning.
However for the long running targets it would still be needed, because it's important to start building them early to avoid building them alone in the end with other stuff already finished. This is not very important feature though, because it can already be optimized by writing dependencies in a different order.
Currently dependency build order is defined (almost) explicitly by the order they appear in Project.meta file. With the parallel build support the order becomes crucial for total build duration, so it would make sense to release user from this optimization burden by letting bake figure out the optimal order. For example bake could prioritize targets with "sync points" and long running targets (could be hinted with a special keyword?).
Caution is needed to not break backward compatibility, eg. by breaking the include path order. Maybe include path order could still follow the "written" dependency order while the build order could be determined by bake?
The text was updated successfully, but these errors were encountered: