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
{{ message }}
Repository navigation
Simulation through gradle uses different toast dir and resets config #19
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
Activity
JaciBrunning commentedon Feb 11, 2016
The reason Gradle's simulation runs under
run/gradle/simulationinstead of justrunis 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 totoast/libsandtoast/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
c13654ein GradleRIO