Hi, I'm still thinking about that, especially trying to find the simplest solution.
Here is a new proposal, that requires less changes: 1) Add a new project option that allows to indicate the library search directory at runtime. If specified, the libraries are searched in that directory first. (Question: are multiple directories needed?) 2) Elsewhere, the libraries are searched in the same directory than the components, '<gambas installation prefix>/lib/gambas3'. The difference is that a library has no *.component file, and its name cannot starts with "gb.", which is reserved for gambas components. 3) For backward compatibility, the libraries are finally searched in '<gambas installation prefix>/bin'. 4) At debug time, in the IDE, libraries are searched in the same directories, and will be listed in the project configuration dialog to be checked (the old specific library tab may be removed). 5) The packager will install libraries in '<gambas installation prefix>/lib/gambas3', and prevent the use of 'gb.' at the beginning of project name. What do you think now? -- Benoît Minisini ------------------------------------------------------------------------------ Site24x7 APM Insight: Get Deep Visibility into Application Performance APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month Monitor end-to-end web transactions and take corrective actions now Troubleshoot faster and improve end-user experience. Signup Now! http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140 _______________________________________________ Gambas-user mailing list Gambas-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/gambas-user
