Compatibility issue

[stanceboyCZ]

Hey guys, almost all of the tools and programs for Stunts are not for 32-bit. And i request you guys to do it compatible.

[Matei]

I have 32-bit tools:

https://matei.one/idxscr.html

Besides the games, there's a  program for viewing tracks from Stunts in simcarstunts-6.0.4.tar.gz. I always compile the versions for wind0w$ with Open Watcom 1.9, so they are 32-bit. I still recommend that you install some GNU/Linux though and let's not forget that your CPU is 64-bit. My chess game is also 32-bit:

https://matei.one/idxchess.html

 

[Duplode]

@stanceboyCZ At the moment, which tool or tools you'd like to have a 32-bit executable, so that we can look into preparing it?

(For my tools in particular, I haven't been making 32-bit binaries because I no longer use 32-bit systems, and also because some relevant toolchains are gradually dropping 32-bit support. Still, I could try to work it out using a VM or some such.)

[Matei]

https://en.wikipedia.org/wiki/Haskell

The Glasgow Haskell Compiler (GHC) compiles to native code on many different processor architectures, and to ANSI C, via one of two intermediate languages: C--, or in more recent versions, LLVM (formerly Low Level Virtual Machine) bitcode.

So where's the problem?

[Duplode]

So where's the problem?

-fvia-c isn't really a practical option for compiling one's everyday programs. See https://downloads.haskell.org/ghc/latest/docs/users_guide/codegens.html#c-code-generator-fvia-c :

This is the oldest code generator in GHC and is generally not included any more having been deprecated around GHC 7.0. Select it with the -fvia-C flag.

The C code generator is only supported when GHC is built in unregisterised mode, a mode where GHC produces "portable" C code as output to facilitate porting GHC itself to a new platform. This mode produces much slower code though so it's unlikely your version of GHC was built this way. If it has then the native code generator probably won't be available. You can check this information by calling ghc --info (see --info).

[Matei]

Then why don't you just use C? My chess game, for instance, works everywhere, including in (Free)DOS:

https://matei.one/idxchess.html

SDL doesn't have support for DOS, btw.

[stanceboyCZ]

i'm not an programmer type, and i wouldn't dare to do something if i'm not that good

[stanceboyCZ]

@stanceboyCZ At the moment, which tool or tools you'd like to have a 32-bit executable, so that we can look into preparing it?

(For my tools in particular, I haven't been making 32-bit binaries because I no longer use 32-bit systems, and also because some relevant toolchains are gradually dropping 32-bit support. Still, I could try to work it out using a VM or some such.)

i was talking about Stressed and other tools, my system is 32-bit

[Duplode]

i was talking about Stressed and other tools, my system is 32-bit

Stressed should work with Qt 5. That avoids one of the difficulties in building a 32-bit version, as Qt 5 (as opposed to Qt 6) has x86 as a supported architecture. I'll look into it as soon as I get a chance.

[Cas]

Older versions of Bliss were 32 bit, then I began posting both, but eventually, it became very complicated to compile it for both architectures, so now I only compile (GNU/Linux) for 64 bit. I'm planning to create an AppImage to simplify the thing. As regards Windows, I don't use this platform myself, so for compilation, I use Wine and FreeBasic for Win. I don't remember if that one is available 32 bit on the site.

[Matei]

That's what happens when you don't use C.

[Cas]

I happens when you use C too. You can only avoid it if you have absolutely everything statically liked. Unfortunately, nowadays, libraries are bloated and designed in a way that makes that completely impractical. In GNU, there's an additional problem because the system is designed to make it very hard to link things statically. In the end, we're forced to use virtual layers, such as Wine, JVM, SDL or DOSBox because programs break from a computer to another or from an OS version to the next and as a result, nobody truly knows how to program a real computer anymore.

[Matei]

https://en.wikipedia.org/wiki/ANSI_C

https://en.wikipedia.org/wiki/C_standard_library

SDL is not bloated and those guys took care of everything::

https://github.com/libsdl-org/sdl2-compat/releases

https://github.com/libsdl-org/sdl12-compat/releases

Again:

Ok, then let's statically compile the entire operating system into the program, and while we're at it, the computer and also a nuclear power plant, just to be sure.

Problems with FreeBASIC:

http://freebasic.net/

Enable JavaScript and cookies to continue

And does it support Wayland? If it doesn't, have you statically linked X11 to your programs? Btw, the distribution I use uses X11 and I still can't run your programs and again:

https://sourceforge.net/projects/simple3d/

SDL_grf - functions for 2D/3D graphics (lines, circles, discs, rectangles, triangles, text and 2D or 3D models composed of triangles), sound and input, written in C;

That's for both SDL 1 and SDL 2. I suppose that adapting them for SDL 3 wouldn't be very complicated, but it's not necessary, as can be deduced from above.

[stanceboyCZ]

where do i put the files?