[Gambas-user] Distribution of custom shared libraries

[Tobias Boege]

On Fri, 22 Feb 2019, Cedron Dawg wrote:
> Hello all,
> 
> I've been messing around with Gambas for a few weeks now.  It's very impressive, and since VB6 has been my favorite rapid development platform I am finding Gambas very helpful.  I've done a little bit of GUI programming in raw X and Tkinter, and this beats them hands down.
> 
> I have written a small shared library to access GamePads or Joysticks using the "/dev/input/js#" device.  Along with that I have a small demo project which simply prints the GamePad data to the console and a more substantive video game that I intend to put in the software farm.
> 

Cool, I also have that (as a native component, though) but never got around
to release it :-/

> 3) If I want ot distribute compiled versions only, where to include it?  32-bit vs 64bit?
> 

Compiled Gambas executables are architecture-independent which I'm pretty
sure includes endianness as well as word length. That is because *.gambas
files contain classes compiled to Gambas bytecode. You need the Gambas
virtual machine, aka interpreter, to execute them -- unlike the *.exe files
that VB6 presumably produces.

If you want to distribute compiled versions of your program, I would suggest
making an installation package via the IDE. This includes the *.gambas file
and links to all the dependencies required on the consumer's machine to
run it, including at least the Gambas interpreter. Their package manager
will resolve the dependencies when your program gets installed.

Regards,
Tobi

-- 
"There's an old saying: Don't change anything... ever!" -- Mr. Monk