[Gambas-user] Arch Version 3.18.4 issue with bytecode version
Benoît Minisini
benoit.minisini at gambas-basic.org
Tue Jan 2 15:13:20 CET 2024
Le 02/01/2024 à 01:59, Brian G a écrit :
>
> On 1/1/24 16:10, Brian G wrote:
>>
>> On 1/1/24 15:41, Benoît Minisini wrote:
>>> Le 01/01/2024 à 23:40, Brian G a écrit :
>>>>>
>>>>> Can you send me the package that includes the program that raises
>>>>> the "bytecode too recent" error?
>>>>>
>>>> Yes I can Send the package, In the mean time I cloned the repository
>>>> to a Archlinux system and built new packages on the 3.18.4
>>>> system and then installed it everything runs fine with that.
>>>>
>>>> As expected.
>>>>
>>>
>>> I understood. The requested bytecode version is not taken into
>>> account when the packager commands are run, as this feature is based
>>> on an environment variable.
>>>
>>> As a temporary workaround, you can define "GB_PCODE_VERSION=3.18"
>>> -before- running the IDE and then make the packages from that IDE.
>>>
>>> Regards,
>>>
>> OK, will give it a go.
>>
>> Thanks Benoît
>>
>>
>> ----[ http://gambaswiki.org/wiki/doc/netiquette ]----
>
> Ok, that works just fine, the correct byte code is generated.
> But takes me down a bit of a rabbit hole!
> The app image works correctly, but loads plugins that were cached, built
> with the new pcode.
>
> Maybe the scripter should be also checking the pcode version of cached
> scripts/plugins
>
> Oh well the world is not perfect ;)
>
> arch and appimage work correctly now on fresh installs.
>
> Is there a way to check the pcode version of an lib/comp/plugin before
> they are loaded?
>
Can you try the last commit? Now the bytecode version is a compiler
option ("-b"), so the packager will take it into account without the
previous workaround.
You will be able to use that new option in the scripter too if you like.
Regards,
--
Benoît Minisini.
More information about the User
mailing list