[Gambas-user] Working with .so library

[Jussi Lahtinen]

That is good way to share C library code. However, little thing.
Instead of giving error messages like "MaybeCompileLibrary: compile.sh not
found.", give them like this:
"MaybeCompileLibrary: " & theShSpec & " not found."

That way the user knows what exactly could not be found and from where. Or
in case of open source program, even like this:
System.Backtrace[0] & ": " & theShSpec & " not found."

This way the user knows immediately the line in the source code what gives
the error.


Jussi









On Wed, Jun 26, 2019 at 6:55 PM Cedron Dawg <cedron at exede.net> wrote:

> I've whipped up a sample project which should be similar to your situation.
>
> This project shows:
>
>  * How easy it is to interface to a C shared library.
>
>  * My clever, but a bit complicated, way of compiling a C shared library
> from Gambas
>
>  * The difference between Gambas' ordinary string functions (ASCII) and
> the static String functions (UTF-8)
>
> You should note:
>
>  * The C code is oblivious to the UTF-8 encoding of the string constant.
>
>  * There is no conv function usage
>
>  * I use a string instead of allocated memory
>
> Hopefully this will clarify the issues at hand.
>
> Ced
>
>
> ----[ Gambas mailing-list is hosted by https://www.hostsharing.net ]----
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.gambas-basic.org/pipermail/user/attachments/20190626/15341ad6/attachment-0001.html>