Originally the drivers for windows were bundled in the Java IDE, historically the avr core was the one bundled with the IDE, which was responsible for installing them. With the new IDE 2.0 the avr core is downloaded and installed during the first execution.
It makes much more sense to leverage the post-install.bat script to do this task, freeing the IDE from this responsibility.
During the process of porting the drivers I removed CP210x drivers since we do not have anymore boards that require them, and also the Old_Arduino_Drivers.zip since they were unused.
I also reorganized a bit the folders: now all the gemma drivers and libusb (required by the gemma) are under gemma/ folder.
To test my changes I created a fake index located here
and installed it using the java IDE on a PC with win 10.
I added the allow_insecure_packages=true option in the preferences.txt to allow the post-install.bat script to be run and since the fake index does not have signature. The result form my testing are:
Originally the drivers for windows were bundled in the Java IDE, historically the avr core was the one bundled with the IDE, which was responsible for installing them. With the new IDE 2.0 the avr core is downloaded and installed during the first execution. It makes much more sense to leverage the
post-install.bat
script to do this task, freeing the IDE from this responsibility. During the process of porting the drivers I removed CP210x drivers since we do not have anymore boards that require them, and also theOld_Arduino_Drivers.zip
since they were unused. I also reorganized a bit the folders: now all the gemma drivers and libusb (required by the gemma) are undergemma/
folder.To test my changes I created a fake index located here and installed it using the java IDE on a PC with win 10. I added the
allow_insecure_packages=true
option in thepreferences.txt
to allow thepost-install.bat
script to be run and since the fake index does not have signature. The result form my testing are:Before:
After: