Re: Python recompile

On 08/03/2025 10:12, Muttley@dastardlyhq.com wrote:

On Fri, 7 Mar 2025 18:02:23 +0000
bart <bc@freeuk.com> gabbled:

On 07/03/2025 14:09, Muttley@DastardlyHQ.org wrote:

On Fri, 7 Mar 2025 14:00:13 +0000
bart <bc@freeuk.com> wibbled:

On 07/03/2025 09:53, Muttley@DastardlyHQ.org wrote:
Note that if downloadeding pre-built binaries, you will usually have a
separate binary file for each platform. The same here: a separate C file
per platform.

>
Not sure why you think that makes things simpler. Just means you could end
up with 10x the number of files unless you have a different source package
for each platform.

>
Sure, because downloading the source code for all conceivable platforms is so simple!

 Huh?
 

I haven't started to look at what's involved in building it for Windows Actually I haven't got a clue how to go about it. Neither do I know how long it might take.
>
Is this what you mean by 'simpler'?

 Err, no idea what you're talking about. Perhaps you didn't read what I
wrote properly. The simple solution is to have a single package for all OSs

This what I understood you meant: you want to download a bunch of source code, together with makefiles and configure scripts and all the usual stuff. It doesn't matter if platform configuration is done with #ifdefs or by choosing some combination of files.
It's usually a horrible, sprawling less with a high chance of failure. It's bad mistake to just dump the developer's directory tree onto users, and lazy.
Usually a precompiled binary download is a smaller, simpler selection of files (often just one), there is no building involved and no special tools needed (and no need to employ CYGWIN, MSYS2 or WSL if building on Windows, or having to install VS).
My idea is similar to supplying binaries, but replacing each binary file with one C source file. This now needs a C compiler to turn into a binary, but nothing else. No configure, no makefiles, virtually no special options, no special compiler needed and no special version.
 > which has a load of ifdefs in the code itself and the user doesn't have to
 > do anything except pick the correct makefile or for windows project file.
I suspect you either haven't done much building of open source software on Windows, or were remarkably lucky.
Have a go at building GMP or LIBFFI for example. With either of those, just give me the relevant DLL file.