[Gambas-user] Working with .so library

[Cedron Dawg]

Thanks Jussi, I will use this version.

As you describe it is how I have been doing it.  I am reluctant to build in the copy command to /usr/lib into the code as that requires the user to enter their admin password, which as a user myself, I don't do in software I've just downloaded and am not confident as been properly vetted.

The approach of building installation packages for each library is not attractive either.  This way also sheds the accompanying test code so you lose seeing how it can actually be employed.

I've also considered putting code into RunSh.module that will print starter compile.sh and a libGambas_XXX.c files if they don't exist.

Still a work in progress, but I really do like how easy it is to interface Gambas to a shared library, and being able to edit the source for the library and the test cradle simultaneously in the same IDE is just awesome.



----- Original Message -----
From: "Jussi Lahtinen" <jussi.lahtinen at gmail.com>
To: "user" <user at lists.gambas-basic.org>
Sent: Wednesday, June 26, 2019 5:52:23 PM
Subject: Re: [Gambas-user] Working with .so library

For demos application directory is good option. For real projects, things should be installed as root to the /usr/lib. For demos consisting of multiple projects, I guess ~/SharedDemoLibrary or similar would be good. I don't think there is standard to follow for that case. 


Jussi