Improve v++ logging (HAST-280)
sarahelsaig opened this issue · comments
We don't get a lot of useful information if a Vitis build fails during the v++ compilation, particularly in synthesis. This is because the individual steps of the process are logged separately in deep subfolders inside /tmp/hastlayer/. This makes debugging with the docker image particularly inconvenient. We should at least detect when the main log says please look at the run log file '{path}' for more information and copy that file into the ./App_Data/logs directory for easier availability.