[Gambas-user] binaries not compiling with force bytecode setting

Bruce Steers bsteers4 at gmail.com
Fri Jan 5 12:11:18 CET 2024


I found the problem Ben.
line 2168 Project.module

  If ForceBytecodeVersion Then sExec &= "-b " & ForceBytecodeVersion

Should be
  If ForceBytecodeVersion Then sExec &= "-b " & ForceBytecodeVersion & " "

Respects
BruceS

On Fri, 5 Jan 2024 at 10:33, Bruce Steers <bsteers4 at gmail.com> wrote:

> I've just spent a while dealing with a problem.
>
> The problem was with the binaries in the .gambas folder not being compiled
> when i hit the compile all button.
>
> breakpoints were not activating.
> commented out code was still running like it was not commented because the
> older binaries are still being used.
> I tried to reset the binaries by deleting the .gambas folder then pressing
> "compile all" and the .gambas folder did not get created and no binaries
> were made.
>
> if i opened the project folder in a terminal and typed gbc3 -waxg then it
> compiled as expected and the .gambas folder appeared.
>
> I tracked the problem down to having the project properties "force
> bytecode version" set to 3.15.
>
> I'm finding if i set a bytecode version to anything the project does not
> compile the binaries and the .gambas folder is not created.
>
> If i unset the "force bytecode version" then the gambas folder is created
> and the binaries are compiled as expected.
>
>
> Respects
> BruceS
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gambas-basic.org/pipermail/user/attachments/20240105/85540e86/attachment.htm>


More information about the User mailing list