I’ve noticed in 4.12 a new menu item ‘Cook Content for Windows’, i.e. for debugging.
It’s nice, but… it uses same intermediate dir (Saved/Cooked/WindowsNoEditor) as shipping cooking does.
So, when I run debug or shipping cooking this dir is cleaned and both processes starts at very beginning each time.
Maybe it possible to introduce a difference in dir names? E.g. ‘Saved/Cooked/WindowsNoEditor_Debug’ or ‘Saved/Cooked/WindowsNoEditor_Development’ and ‘Saved/Cooked/WindowsNoEditor_Shipping’.
This will take more space on disk but saves a lot of time when re-cooking few assets both for debug and shipping. (I hope determenistic cooking was improved in 4.12.)
Upd.: I’m saying about temp or intermediate dirs (in Saved/), not about target dirs if applicable.
I may not quite understand your request, but can’t you do what you are asking by simply designating one directory for debugging and one for shipping as shown here (note: deselecting “Full rebuild” will result in only building modified files):
I’ve checked this options. This is a target dir. But I mean intermediate dir in ‘Saved/Cooking’. Also this option does not change its value for each configuration. It stays constant.
Full rebuild is not related to this question.
I understand cooking as: 1) cook files to intermediate dir (somewhere in ‘Saved/Cooking’; 2) copy files to target dir.
Thanks for elaborating on your idea. I have entered the following feature request to have separate intermediate folders for debugging, development and shipping packaging: UE-31633.
