Re: Gambas 3.19.6 and 3.19.90 recipes

[Benoît Minisini <benoit.minisini@xxxxxxxxxxxxxxxx>]

Le 16/11/2024 à 15:50, gbWilly a écrit :
> On Saturday, November 16th, 2024 at 00:11, Benoît Minisini <benoit.minisini@xxxxxxxxxxxxxxxx> wrote:
>
> > > Before 3.15 the package list is a static table. Each new version should
> > > actually have a static table and the @{package-table} only serves the
> > > needs of latest master version.
> > > So, when 3.20 comes out the current @{package-table} should be made
> > > static for 3.20, so that new added components to master to not interfere
> > > with required packages for that version.
> I have taken the liberty of making the 3.19 package table static, so correct packages are listed.
> I also added your changes on wiki for development version to the 'The runtime package' in 3.19.

A pity, but there is no better solution at the moment.

> So, gb.jit is now listed as part of runtime.
> No more gb.hash, gb.jit or gb.test in the static package list
>
> Please check (you'll need to log in on wiki to see the edits)
> Below I added ad section 'Page revisions' where changes are explained, by who they where done and when.

Thanks. I will check, but later, as the urgency is making my packaging 
specification file generation program.

> If the static table is to your liking I will copy it to 3.18 and remove gb.highlight and change gb.form to depend on gb.eval.highlight.
> That is about all that is different between 3.18 and 3.19 I believe.
> So, 3,18 will have a static table as well and I guess 'The runtime package' in 3.18 needs to be changed as well to include gb.jit
>
> Has gb.jit always been part of runtime? As, I have seen packages being installed for it in the past, but that might have been debian official packages
> If not, at what version of gambas3 did it change?

The previous JIT compiler was a component on its own, as it depended on 
llvm.

But the new one only needs a C compiler, and detect it dynamically, so 
it is not a mandatory dependency. It's more like a dynamic part of the 
interpreter. It's just that, if there is no C compiler, the JIT compiler 
will do nothing.

Regards,

--
Benoît Minisini.