".bin" are a "dump" of Scilab 5 macros stack representation, so it is impossible in Scilab 6 to reproduce it. I am afraid that you need to rebuild your toolboxes especially to Scilab 6.
Some compatibility points will be managed by ATOMS. example : tbx_2 -> deps : tbx_1 ( any ) If you install tbx_2 on Scilab 6, atoms will looking for latest version of tbx_1 >= 6 If you install tbx_2 on Scilab 5, atoms will looking for latest version of tbx_1 5.0 <= x < 6 ( not currently coded, we need to update process that generate ATOMS dependencies ) But yes, that a lot of work to rebuild all toolboxes for Scilab 6, check behaviors, tests, demos, dependencies. Anyway, thank you for the problem analysis. Antoine Le 15/07/2015 15:02, Samuel Gougeon a écrit : > Le 15/07/2015 14:53, Samuel Gougeon a écrit : >> .../... >> OK: a module may provide both lib files, and in its startup file, test the >> Scilab version and copy the right lib file in its ~\macros\ directory. >> But this is quite tricky. From now (5.5) and until Scilab 6.1, genlib() >> could generate both "lib" and "lib.xml" files, and lib() use the right file >> among both. > . > By the way, this trick won't work for modules installed for all users, since > the user would then need write privileges on > SCI\contrib\<module>\<version>\macros\ > So, let's forget it. Modifying genlib() and lib() would be much better. > > > > _______________________________________________ > dev mailing list > [email protected] > http://lists.scilab.org/mailman/listinfo/dev -- Antoine ELIAS Software developer ----------------------- Scilab Enterprises 143bis rue Yves Le Coz - 78000 Versailles Phone: 01.80.77.04.70 http://www.scilab-enterprises.com
_______________________________________________ dev mailing list [email protected] http://lists.scilab.org/mailman/listinfo/dev
