Le 01/02/2016 16:59, Tobias Boege a écrit :
>
> To get it running required me a bit of thinking. My library naturally
> did not have a vendor name, so it was created as
>
> Desktop.DataDir &/ "" &/ "lib.gambas" ^-- Vendor
>
> and could not be found by the IDE because it looks only for the
> vendor
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
On Mon, 01 Feb 2016, Beno??t Minisini wrote:
> > Also I think I would at some point want to run my project from an
> > executable. Will there be a way that I can explicitely tell the
> > interpreter to look in ~/.local/share for libraries?
>
> At the moment, you must be in debug mode to use that
On Mon, 01 Feb 2016, Beno??t Minisini wrote:
> Hi,
>
> In revision #7593 you get a new implementation of the library management:
>
> 1) When you create an executable from a library project, a symbolic link
> is created in '~/.local/share/gambas3/lib/', where is
> the vendor name now defined
Hi,
In revision #7593 you get a new implementation of the library management:
1) When you create an executable from a library project, a symbolic link
is created in '~/.local/share/gambas3/lib/', where is
the vendor name now defined in the project property dialog, and in the
packager wizard.
Am 31.01.2016 um 04:55 schrieb Benoît Minisini:
> You can already do that, except that vendor name should be included in
> the library name.
Ok. I can throw them all in one directory. But the library name
unfortunately does not act like a namespace, it does not separate the
Classnames. If you
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
Le 30/01/2016 21:44, Tobias Boege a écrit :
> On Sat, 30 Jan 2016, Beno??t Minisini wrote:
>> Hi,
>>
>> I'm still thinking about that, especially trying to find the simplest
>> solution.
>>
>
> Good, I still need it :-) ATM I can continue work by having a copy of the
> library in each project that
Hi,
Am 30.01.2016 um 20:48 schrieb Benoît Minisini:
> 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).
That would break my current
Le 30/01/2016 21:58, Christof Thalhofer a écrit :
> Hi,
>
> Am 30.01.2016 um 20:48 schrieb Benoît Minisini:
>
>> 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
On Sat, 30 Jan 2016, Beno??t Minisini wrote:
> Hi,
>
> I'm still thinking about that, especially trying to find the simplest
> solution.
>
Good, I still need it :-) ATM I can continue work by having a copy of the
library in each project that uses it. So we should not rush things. (The
new
Am 30.01.2016 um 22:21 schrieb Benoît Minisini:
> I will add a user-specific library directory only used at debug time:
> "~/.local/share/gambas3/lib". By putting libraries there, you won't have
> to install them globally to debug your project.
>
> You will just have to store your libraries
Am 30.01.2016 um 20:48 schrieb Benoît Minisini:
> 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?)
If there shall be the opportunity to
Le 31/01/2016 01:42, Christof Thalhofer a écrit :
> Am 30.01.2016 um 20:48 schrieb Benoît Minisini:
>
>> 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
El 26/1/16 a las 23:46, Christof Thalhofer escribió:
>
> So your proposal, Benoît, is the more generic one and better. Especially
> with the future possibility to invent namespaces in mind.
>
> Alles Gute
>
> Christof Thalhofer
Uhh!, namespaces. Good point, Chris. That way, we could avoid
Am 26.01.2016 um 01:31 schrieb Benoît Minisini:
> Here is a proposal, tell me what you think.
>
> 1) When you create a project library, you will have to specify a vendor.
Good, but look at the end of my post.
> 2) When creating the library executable of a library project, a symbolic
> link to
Hi,
now I see that this ...
Am 26.01.2016 um 10:31 I wrote
> You could instead give the author the chance to define a path where to
> find own libs at runtime. I would prefer that because I would store libs in
>
> /usr/lib/$vendor/gambas
>
> or in
>
> /usr/local/lib/$vendor/gambas
>
> so
On Tue, 26 Jan 2016, Beno??t Minisini wrote:
> Here is a proposal, tell me what you think.
>
> 1) When you create a project library, you will have to specify a vendor.
>
> 2) When creating the library executable of a library project, a symbolic
> link to the executable will be created in
>
On 01/25/2016 07:31 PM, Benoît Minisini wrote:
> 4) When creating a package of a library, the library executable will be
> installed in '/usr/lib/gambas3/' ('/usr/lib/gambas3' is for
> components). Maybe '/usr/share/gambas3/lib/' should be better,
> to mimic 2). After all, Gambas libraries are not
Here is a proposal, tell me what you think.
1) When you create a project library, you will have to specify a vendor.
2) When creating the library executable of a library project, a symbolic
link to the executable will be created in
'~/.local/share/gambas3/lib/'.
3) When another project wants
20 matches
Mail list logo
