We are happy to announce TaPaSCo 2019.10 Coming right to you with a number of structural changes. Directory Structure =============== The directory structure has been changed completely. The individual parts of TaPaSCo are now separated into the Toolflow and Runtime directories to avoid confusion. TaPaSCo Setup ============ The novel `tapasco-init` script enables out-of-tree builds to simplify using multiple TaPaSCo builds in parallel. Toolflow Changes ======================= The toolflow is now built by Gradle instead of SBT. Along with these changes, we now provide OS packages for leading Linux distributions. Compilation of TaPaSCo is no longer necessary for a majority of users. Quality of Life =========== A number of quality of life changes targets the usability of TaPaSCo. QoL-Improvements include: * Updated and improved Readme. * TaPaSCo will now also work with symbolic links. This also means, that you do not have to move your HLS-Kernels. Instead just symlink them into the corresponding directory. * The parsing of `.json`-files was reworked. Now, all relevant errors are reported much more clearly. Also, folders and files mentioned by the `.json`-files are checked for existance, to ensure that all required files are actually available. * A lot of unnecessary error-messages have been removed. * The starting Frequency of DSEs can now be overwritten to save time. TaPaSCo Status Core ================= The status core is now based on Protobuf instead of using a custom format. The new format is much more flexible and provides much more indepth information about the bitstream. Bugfixes ======= In total this release closes 34 [Issues](https://github.com/esa-tu-darmstadt/tapasco/issues?q=is%3Aissue+milestone%3A2019.10+is%3Aclosed) in over 270 commits.