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
When you start a simulation through gradle simulation, it puts the toast folder in run/gradle/simulation instead of just in run as it does when started from Eclipse. It also won't keep changes made to the toast.conf file and just rewrites it to defaults on every run.
The reason Gradle's simulation runs under run/gradle/simulation instead of just run is because of Toast Libraries and Modules. In an IDE, Toast dependencies (both libraries and modules from the user's buildscript) are already linked. In Gradle Simulation, they have to be exported manually to toast/libs and toast/modules. If these were to keep the same simulation directory, the IDE would have 2 conflicting sets of libraries.
The non-persistence issue is fixed in commit c13654e in GradleRIO
When you start a simulation through
gradle simulation
, it puts the toast folder inrun/gradle/simulation
instead of just inrun
as it does when started from Eclipse. It also won't keep changes made to thetoast.conf
file and just rewrites it to defaults on every run.Thanks to @randbrown for noticing this issue.
The text was updated successfully, but these errors were encountered: