Hi David,
> Alex and others, how do you manage to keep everything so up to date so well
> and still maintain a life?
I use a set of pil- and shell-scripts to synchronize my work between my
tablet and a notebook, and to generate backups and releases. No problems
at all, and very simple.
♪♫ Alex
Hi Jon, Rafik,
> I will let Alex answer the question about precompiled binaries.
Sorry, I can't do that. I don't even have access to those platforms.
What I do since early on is providing pre-assembled *.s files for all
platforms (see the INSTALL file). This won't help on the Mac of course.
♪♫
Updated to 16.6. I really need to write a small script to e-mail me when
new versions come out.
Alex and others, how do you manage to keep everything so up to date so well
and still maintain a life?
Congrats on the docker image Rafik. It's nice to know that OSX users can
now go forth and hack
Hey guys,
In order to have latest pico on my mac osx, I created a new docker image
that builds from the source.
It is a bit fatter than the older one, but has the benefit to be built from
source, so I don.t need a binary to build it if a new version of pico goes
out :)
Check it out here:
Hi Rafik,
I have an old Mac (OS X 10.8.5) that I use mainly for compiling 32-bit
PicoLisp. The compiled binaries I can copy to newer Macs, where they run fine.
If you want, I can make the binaries available.
It is possible to install old/standard build tools on a new Mac. I have done it
once,
Hi Jeronimo,
> I have finally found some time to revamp the Picolisp packages for
> OpenWRT. I'm not sure I will be able to update them as soon as new
> versions are available, but I'll try.
Thanks! That's good news. :)
> I have not included all files that are usually installed. Examples and
>
Hi Rafik,
> As it turns out, as mac OSx defaults to clang, We get an error preventing
> the package to compile:
>
> flow.c:786:37: error: fields must have a constant size: 'variable length
> array in structure' extension will never be supported
> struct {any sym; any val;}
