Thanks for your feedback.
It’s true that there are no “big” installer.
Can we give a try to the mirroring solution, in order to address your use case?
What you’ll need:
- a mirror for DS repository
- a mirror for packages repository
- a mirror for external installers (drivers, Boot2Docker (if you’re interested in Legato on Windows))
Concerning external installers, they are downloaded by our DS installer in the target directory before being executed, so if you run the full install at least one time, you have already got them.
For DS repository mirroring, you’ll need at least an already installed DS to perform it (or even maybe a simple Eclipse install, as it is entirely done with Eclipse).
Two commands to be executed:
devstudio -nosplash --launcher.suppressErrors -application org.eclipse.equinox.p2.metadata.repository.mirrorApplication -source http://updatesite.sierrawireless.com/developerStudio3/32RC4 -destination file:C:/tmp/dsMirror
(should be short)
devstudio -nosplash --launcher.suppressErrors -application org.eclipse.equinox.p2.artifact.repository.mirrorApplication -source http://updatesite.sierrawireless.com/developerStudio3/32RC4 -destination file:C:/tmp/dsMirror -verbose -ignoreErrors
(should be long, a bit more than 300MB to be downloaded)
Note that this technique won’t mirror the Open AT GCC toolchain, as its repository is shared by several DS versions. So you can either redistribute the installed directory from an existing DS install, or mirror the repository as above, from the updatesite.sierrawireless.com/de … /gccOAT474 URL.
For packages mirroring, you can either redistribute those you have install with DS, or use the same mirroring mechanism than for DS.
Then, you can tell to the installer from where to download its stuff.
The easiest way is maybe to create a .bat file aside of the installer executable, and to add these parameters to the installer command line:
installer.exe -install.Declipse.p2.metadata=%repo% -install.Declipse.p2.artifacts=%repo% -install.Dds.spm.repo=%spmRepo%
(use the spmRepo stuff only if you’ve mirrored the packages the same way that for DS repository; otherwise, you should just uncheck the package install option, and install them from DS after)
Then you only need to run the .bat file, in order to install DS from your mirror.
Note: if you prefer, you can also share your local mirror through HTTP; you only need to have the files served by a basic HTTP server.
And that’s it. Please tell me if you have questions or troubles.
Last words concerning the hardware filter at the beginning of the installer:
This filter selects what’s compatible with your hardware for drivers and packages. DS in itself will be installed exactly the same way for all modules. So if you have multiple modules to use, the recommended way is to do a first install with a given hardware, and then to install additional packages from DS, and additional drivers from the Developer Zone.
wow, probably one of my longest post here
Just hoping everything is clear; if not, please just ask