unsubscribe

[Amaury Hernández Águila]

Re: picolisp on windows

[C K Kashyap]

Oops, I should have looked more closely. I do see the .src files :)
Thanks!

On Tue, Feb 5, 2019 at 6:07 AM Alexander Burger  wrote:

> Hi Kashyap,
>
> > Anyway, I could not find the java sources - I could only find the
> compiled
> > jar file. Are the java sources available?
>
> They are in fact included in the PicoLisp distro, however not as *.java
> files,
> but as
>
>ersatz/sys.src
>ersatz/fun.src
>
> The script mkJar takes them, builds a single PicoLisp.java file, and
> compiles
> that with javac.
>
> The mkJar script is written in PicoLisp, so this is a chicken-egg problem

Re: picolisp on windows

[Alexander Burger]

Hi Kashyap,

> Anyway, I could not find the java sources - I could only find the compiled
> jar file. Are the java sources available?

They are in fact included in the PicoLisp distro, however not as *.java files,
but as

   ersatz/sys.src
   ersatz/fun.src

The script mkJar takes them, builds a single PicoLisp.java file, and compiles
that with javac.

The mkJar script is written in PicoLisp, so this is a chicken-egg problem. But
you can use Ersatz to (re)build itself.

☺/ A!ex

-- 
UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe

Re: picolisp on windows

[C K Kashyap]

Thanks for the tips rcs,
Yes indeed I was able to build minipicolisp on windows using mingw32. The
best part is that I could take the generated exe and run it on another
machine :)

My goal is to understand picolisp implementation and perhaps switch to it
as my programming environment. I cant wait to get a system working with
picolisp + libuv + SDL! I spent a lot of time trying to build a compiler
starting with the 90 minutes scheme to c compiler (I've managed to
translate it to clojure and python ) In
my mind I had no reason to doubt some things which picolisp paper calls as
myths :) ... but after reading it, I feel like I should atleast see it in
action. I was particularly moved by the thought that compilation causes the
loss of lispiness!

Anyway, I could not find the java sources - I could only find the compiled
jar file. Are the java sources available?

Regards,
Kashyap

On Tue, Feb 5, 2019 at 4:26 AM r cs  wrote:

> Kashyap:
>
> Under MinGW32 miniPicoLisp fails to build without two tweaks to the
> Makefile:
>
> 1. Remove the -lc switch in this line:
>
> *$(CC) -o $(bin)/picolisp $(picoFiles:.c=.o) -lc -lm*
>
>
> 2. After doing the above an executable will be produced, but the *strip*
> command in the line after that will also fail because under MinGW the
> output file is given an ".exe" filename extension.  You can either add it
> to the Makefile or just run *strip picolisp.exe* manually (which takes
> the resulting file down to 170K from 331K, so it is worth it).
>
> As an alternative to miniPicoLisp on Windows you may want to consider
> using *ersatz*, the Java-based PicoLisp variant (thanks Alex!).  The
> provided jar file works fine under Windows, and it can be rebuilt from
> source there too.  The "non-Unix" command to run it in the README works on
> Windows (using semicolon delimiters), but when you run ersatz from Linux
> you have to use colons instead:
>
> java -DPID=42 -cp .;tmp;picolisp.jar PicoLisp lib.l *(Windows)*
>
> java -DPID=42 -cp .:tmp:picolisp.jar PicoLisp lib.l *(Linux)*
>
> On Windows the Oracle JRE/JDK works fine.  On Linux for openjdk 8 these
> packages are needed: *openjdk-8-jdk, openjdk-8-jdk-headerless,
> openjdk-8-jre, openjdk-8-jre-headerless*.
>
> Regards,
> rcs
>
> On Mon, Feb 4, 2019 at 10:24 AM C K Kashyap  > wrote:
>
>> Hi Alex,
>> I wonder if libuv can substitute for POSIX?
>> Has there been any work in that direction?
>> Regards,
>> Kashyap
>>
>> On Sun, Feb 3, 2019 at 11:47 PM Alexander Burger 
>> wrote:
>>
>>> On Sun, Feb 03, 2019 at 10:25:13PM -0500, r cs wrote:
>>> > I've personally built PicoLisp under MinGW-32 on Windows 7, copied the
>>> EXE
>>> > from where I built it in msys under
>>> /MinGW/msys/1.0/home/myUser/picoLisp/src
>>> > to some place else on the system, and then just run it from a command
>>> > prompt.  Using *make* is also a lot less work than dealing with an
>>> IDE.  I
>>> > only use '32 because it is easy to install and I've been using it for
>>> > years, but the newer '64 should work the same way.
>>>
>>> You mean miniPicoLisp, right? Because neither pil32 nor pil64 can run
>>> under
>>> native Windows. They depend on POSIX.
>>>
>>> ☺/ A!ex
>>>
>>> --
>>> UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
>>>
>>
>
> --
> *Níl aon tinteán mar do thinteán féin. *[Irish Gaelic]
> (There is no fireside like your own fireside.)
>
>
>

Re: picolisp on windows

[r cs]

Kashyap:

Under MinGW32 miniPicoLisp fails to build without two tweaks to the
Makefile:

1. Remove the -lc switch in this line:

*$(CC) -o $(bin)/picolisp $(picoFiles:.c=.o) -lc -lm*


2. After doing the above an executable will be produced, but the *strip*
command in the line after that will also fail because under MinGW the
output file is given an ".exe" filename extension.  You can either add it
to the Makefile or just run *strip picolisp.exe* manually (which takes the
resulting file down to 170K from 331K, so it is worth it).

As an alternative to miniPicoLisp on Windows you may want to consider using
*ersatz*, the Java-based PicoLisp variant (thanks Alex!).  The provided jar
file works fine under Windows, and it can be rebuilt from source there
too.  The "non-Unix" command to run it in the README works on Windows
(using semicolon delimiters), but when you run ersatz from Linux you have
to use colons instead:

java -DPID=42 -cp .;tmp;picolisp.jar PicoLisp lib.l *(Windows)*

java -DPID=42 -cp .:tmp:picolisp.jar PicoLisp lib.l *(Linux)*

On Windows the Oracle JRE/JDK works fine.  On Linux for openjdk 8 these
packages are needed: *openjdk-8-jdk, openjdk-8-jdk-headerless,
openjdk-8-jre, openjdk-8-jre-headerless*.

Regards,
rcs

On Mon, Feb 4, 2019 at 10:24 AM C K Kashyap  wrote:

> Hi Alex,
> I wonder if libuv can substitute for POSIX?
> Has there been any work in that direction?
> Regards,
> Kashyap
>
> On Sun, Feb 3, 2019 at 11:47 PM Alexander Burger 
> wrote:
>
>> On Sun, Feb 03, 2019 at 10:25:13PM -0500, r cs wrote:
>> > I've personally built PicoLisp under MinGW-32 on Windows 7, copied the
>> EXE
>> > from where I built it in msys under
>> /MinGW/msys/1.0/home/myUser/picoLisp/src
>> > to some place else on the system, and then just run it from a command
>> > prompt.  Using *make* is also a lot less work than dealing with an
>> IDE.  I
>> > only use '32 because it is easy to install and I've been using it for
>> > years, but the newer '64 should work the same way.
>>
>> You mean miniPicoLisp, right? Because neither pil32 nor pil64 can run
>> under
>> native Windows. They depend on POSIX.
>>
>> ☺/ A!ex
>>
>> --
>> UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
>>
>

-- 
*Níl aon tinteán mar do thinteán féin. *[Irish Gaelic]
(There is no fireside like your own fireside.)

Re: picolisp on windows

[r cs]

Yes -- good catch Alex, thanks.

On Mon, Feb 4, 2019 at 2:47 AM Alexander Burger  wrote:

> On Sun, Feb 03, 2019 at 10:25:13PM -0500, r cs wrote:
> > I've personally built PicoLisp under MinGW-32 on Windows 7, copied the
> EXE
> > from where I built it in msys under
> /MinGW/msys/1.0/home/myUser/picoLisp/src
> > to some place else on the system, and then just run it from a command
> > prompt.  Using *make* is also a lot less work than dealing with an IDE.
> I
> > only use '32 because it is easy to install and I've been using it for
> > years, but the newer '64 should work the same way.
>
> You mean miniPicoLisp, right? Because neither pil32 nor pil64 can run under
> native Windows. They depend on POSIX.
>
> ☺/ A!ex
>
> --
> UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
>


-- 
*Níl aon tinteán mar do thinteán féin. *[Irish Gaelic]
(There is no fireside like your own fireside.)