Yes, I'll try and will post here my experience in order to help with any
trouble.
I saw a message from you talking about not including arm binaries but in
last tgz I got there's a binary include, should I remove it?
On Sat, Sep 23, 2017 at 8:32 AM, Alexander Burger
wrote:
> On Sat, Sep 23, 2017
On Sat, Sep 23, 2017 at 08:06:44AM +0200, pd wrote:
> I've created a github repository in https://github.com/pepdiz/pilbox and I
> can keep it synchronized to PilBox.tgz versions if you want
Yes, that would be nice!
The next task would be to publish it ad F-Droid. I haven't studied the
requireme
I've created a github repository in https://github.com/pepdiz/pilbox and I
can keep it synchronized to PilBox.tgz versions if you want
regards
On Thu, Sep 21, 2017 at 1:02 PM, Alexander Burger
wrote:
> On Thu, Sep 21, 2017 at 12:43:02PM +0200, Richard Z wrote:
> > assuming it is OpenSource, ho
I also vote +1 for submitting to f-droid.
Whoever takes care of the git repo, please **do not** include the arm64
binaries as part of the repo, otherwise over time it will grow quite
large (versioning) and become impossible to clone.
AW
On 17-09-21 11:02 AM, Alexander Burger wrote:
On Thu,
Hello Paul Rubin :-)
You are now subscribed
--
UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Hi all,
to make building your own PilBox from https://software-lab.de/PilBox.tgz easier,
I've now included the picoLisp/ directory (had to be downloaded and installed
separately before), and pre-compiled the Arm64 binaries
bin/picolisp
picoLisp/bin/ssl
openssl/libcrypto.so.1.0.0
opens
