Where can I get a Recent-Git-Build of FreeBASIC?

[coderJeff]

I planned to try cross-compiling with https://github.com/andrewwutw/build-djgpp/releases next.

But before I do that I wondered which environment is used for the official DOS-builds, that are still provided?
Also, which Linux distribution/version is used for the official Linux builds? I'm still using an old debian version, which has the advantage that most systems out there should have a compatible glibc.
Could you give some insights @coderJeff ?

For the DOS releases, I do a clean full build under vmware+winxp and djgpp (for dos) to build. More or less same as 10+ years ago. (I used to build releases under win98 but it is too difficult to network the resources (git, etc) in to win98.)

I use andrew's cross build tool chain during development to cross build from win7 host to a dos target exe to run and test DOS programs in dosbox/dosbox-x or vmware+msdsos. But only for development testing or bug squashing. I didn't find a way for this cross build to help with full test suite validation.

Here is the list of hosts / targets that I build on a release - with the full build and test suite run on each host for each target (all non-windows are under various VM's except the RPi builds which are built and tested on actual RPi's):

host = ubuntu-14.04-x86
host = ubuntu-14.04-x86_64
host = ubuntu-16.04-x86
host = ubuntu-16.04-x86_64
host = ubuntu-18.04-x86
host = ubuntu-18.04-x86_64
host = ubuntu-20.04-x86_64*
host = winnt-6.1
- target = win32-mingworg
- target = win32-gcc-5.2.0
- target = win64-gcc-5.2.0
- target = win32-gcc-7.1.0
- target = win64-gcc-7.1.0
- target = win32-gcc-8.1.0
- target = win64-gcc-8.1.0
- target = win32-winlibs-gcc-10.3.0
- target = win64-winlibs-gcc-10.3.0
- target = win32-winlibs-gcc-10.2.0
- target = win64-winlibs-gcc-10.2.0
- target = win32-winlibs-gcc-9.3.0
- target = win64-winlibs-gcc-9.3.0
- target = win32-winlibs-gcc-8.4.0
- target = win64-winlibs-gcc-8.4.0
- target = win32-equation-gcc-8.3.0
- target = win64-equation-gcc-8.3.0
host = winxp
- target = dos
- target = win32-mingworg
host = ubuntu-21.10-aarch64 (missing**)
host = slackware-14.2-x86*
host = slackware-14.2-x86_64*
host = raspbian9-arm
host = rpios10-arm (missing**)
host = rpios11-arm
host = rpios11-aarch64
host = freebsd-13.0-x86
host = freebsd-13.0-x86_64


(* I have built/tested before, but not recently)
(** I think I planned for these, but have not done yet for fbc 1.10)

[adeyblue]

host = ubuntu-21.10-aarch64 (missing**)

If you need a machine and 200 GB is enough disk space, Oracle Cloud will let you have a 4 core 24GB memory one for free (and it's not time limited). Of course, with Oracle Cloud the real struggle is getting an account in the first place

[fxm]

@St_W,

fbc daily builds did not fire.

[St_W]

Thanks for the notification. I still have the old setup running as I couldn't spend any time on the modernization effort. And it's again not responding to web requests any more. I'll try to replace the Tomcat+AJP with nginx first, cause that is independent from the Java upgrade and hopefully fixes the not-responding-issue. No promises about a date when it will be finished, though.

[St_W]

That was easier and faster than expected
I spent some time this evening and have a basic nginx+Jenkins setup running now. Far from perfect and still using an old Jenkins version that still supports Java 8, but at least the setup got way easier and hopefully also less error-prone. The Tomcat + AJP behind Apache setup is a thing of the past now.
Let's see how stable it runs or if there are any new issues. A DOS build (which has been stuck) already finished successfully today and the latest builds should be uploaded tonight again.

[coderJeff]

A DOS build (which has been stuck) already finished successfully today and the latest builds should be uploaded tonight again.

Just wondering ... Did you try a cross build? Or using your previous method?

[fxm]

That was easier and faster than expected
I spent some time this evening and have a basic nginx+Jenkins setup running now. Far from perfect and still using an old Jenkins version that still supports Java 8, but at least the setup got way easier and hopefully also less error-prone. The Tomcat + AJP behind Apache setup is a thing of the past now.
Let's see how stable it runs or if there are any new issues. A DOS build (which has been stuck) already finished successfully today and the latest builds should be uploaded tonight again.

Good for builds, but not for documentation.

[fxm]

Indeed, it is now the 'manual.chm' that has not been updated !

[SARG]

As always you can find it here : https://users.freebasic-portal.de/sarg/fbdoc.chm

[fxm]

Thanks.

[fxm]

Indeed, it is now the 'manual.chm' that has not been updated !

Same problem for 2 nights.

[St_W]

A DOS build (which has been stuck) already finished successfully today and the latest builds should be uploaded tonight again.

Just wondering ... Did you try a cross build? Or using your previous method?

No, still the old method. The cross-build requires considerably more work (than I spent recently) to configure everything for having it running in an automated way, not sure yet when I'll take the time for that.

Indeed, it is now the 'manual.chm' that has not been updated !

Same problem for 2 nights.

There are two issues: first, the URLtrigger Jenkins plugin can't persist the change-detection state and thus will miss changes if the server is restarted. That's a limitation in my setup that exists since years and I unfortunately don't know an easy solution for that. That has been the issue for your first problem report.
Second, the new standalone setup of jenkins (not running in a Tomcat container anymore) had some different memory settings which led to OutOfMemory errors, effectively killing the server. I've fixed the configuration and added some simple monitoring rule to get notified about such issues earlier. Btw, I can recommend Uptime Kuma for simplistic monitoring purposes. Using that for about a year and works really well for me.
Note that I had to restart the server and thus today's changes up to now are ignored until there's another documentation change due to the plugin limitation explained above.

[SARG]

@St_W
The gcc tools in daily build are a bit out dated.
In fbc 1.10 --> 2.34
In daily build --> 2.24

It causes some problem eg https://freebasic.net/forum/viewtopic.p ... 42#p301242

[coderJeff]

Here's the current list of targets:

• DOS
• FreeBSD x86_64
• Linux x86
• Linux x86_64
• Linux ARMv6
• Linux ARMv7A
• Windows x86
• Windows x86_64

Hey St_W, do you patch fbc or do anything fancy with the ARM builds?

Came up in discussions:
viewtopic.php?p=301307#p301307

[fbfans]

https://users.freebasic-portal.de/stw/builds/
Error: Last modified 2023-11-20
Aborting due to runtime error 3 (file I/O error) at line 66 of src\compiler\lex.bas()