[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: gambas 3.20.0 on debian i386 problem


On Thursday, January 30th, 2025 at 16:29, Benoît Minisini benoit.minisini@xxxxxxxxxxxxxxxx wrote:

Le 30/01/2025 à 15:24, gbWilly a écrit :

I've tried a few things.
Option 1 - The executable:
1. I made a executable of the selftest on a system running gambas 3.20.0 IDE
2. Next on VM in a terminal I did "gbr3 /path/to/executable/gambas3-
selftest.gambas"
3. Reply: 'This is the Gambas Selftest. To run it in the IDE hit F4'

To run the tests of a project from the command-line, you must type:

$ gbx3 -T '*'

Well, that did not work. See below.

nostartup.png

So I looked at the source code I build these binaries from, being the downloaded source from tag 3.20.0 on git. It appears that this downloaded source code is lacking the startup file that is present in the master version. The gambas 3.20.1 source code download from git tag is also missing the startup file for selftest project. I did not check older versions.

Below a freshly downloaded source archive with 3.20.1 from git tag opened in selftest project and as you see NO startup file.

sourcearchive.png

I guess that is why my installed gambas 3.20.0 will not run $ gbx3 -T '*' as the source it was build from is lacking the startup. So, it seems I will need to have a complete source first, build packages again and install those on i386 before I can even run the test properly.

gbWilly


Follow-Ups:
Re: gambas 3.20.0 on debian i386 problemBenoît Minisini <benoit.minisini@xxxxxxxxxxxxxxxx>
References:
gambas 3.20.0 on debian i386 problemgbWilly <gbWilly@xxxxxxxxxxxxxx>
Re: gambas 3.20.0 on debian i386 problemBenoît Minisini <benoit.minisini@xxxxxxxxxxxxxxxx>
Re: gambas 3.20.0 on debian i386 problemgbWilly <gbWilly@xxxxxxxxxxxxxx>
Re: gambas 3.20.0 on debian i386 problemBenoît Minisini <benoit.minisini@xxxxxxxxxxxxxxxx>
Re: gambas 3.20.0 on debian i386 problemgbWilly <gbWilly@xxxxxxxxxxxxxx>
Re: gambas 3.20.0 on debian i386 problemBenoît Minisini <benoit.minisini@xxxxxxxxxxxxxxxx>