Le 01/02/2016 20:15, Benoît Minisini a écrit : >> >> There is one point, however: These automatically created symlinks are >> a bit scary. I can imagine moving my whole source tree into another >> directory and depending on where I put the real executable archive, >> the symlink may be broken. I would like to have a new button on the >> toolbar which saves the real library executable archive under >> >> ~/.local/share/gambas3/<vendor>/<title>:<version>.gambas >> >> instead of making this a symlink. > > Mmm. The goal of these symlinks was the ability to install the same > library projects at different places and to be able to use them for > debugging anyway. > > Moreover, the executable is named "<project>.gambas". Only the symlink > has the version number. > > But I think you're right: by default, create the executable directly in > the local folder, and optionally be able to create where you want, with > a symlink in the local folder. >
I'm stupid: I just have to *copy* the executable instead of making a symbolic link! -- 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
