Re: anyone tried cygwin or mingw recently?
Hi, > It sounds like containers may be exactly what you want. The same > development environment isolated from your host OS of choice. Docker > containers run great on Linux and my understanding is that Windows is > gaining/already has better support than the past. There's not much more > work to get persistent storage working, all the directions are in the links > I posted. I hope that it can be useful to you. yes, containers are great. In fact I was thinking it would be easier and cheaper to ship a raspi or an old phone with picolisp and the app installed than to muck around with windows. Picolisp in termux would be more than sufficient and could also run in any emulator on windows. But it is somehow bizare that it is cheaper to buy an extra computer than port a piece of software. Richard -- Name and OpenPGP keys available from pgp key servers -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Re: anyone tried cygwin or mingw recently?
Hello Richard, It sounds like containers may be exactly what you want. The same development environment isolated from your host OS of choice. Docker containers run great on Linux and my understanding is that Windows is gaining/already has better support than the past. There's not much more work to get persistent storage working, all the directions are in the links I posted. I hope that it can be useful to you. -David On Mon, Jul 17, 2017 at 6:21 AM, Richard Z wrote: > On Sun, Jul 16, 2017 at 12:21:39PM -0400, David Bloom wrote: > > Hi, > > > Hi Richard. If you want to get PicoLisp running on windows compilation > can > > be difficult but you mention wine. What are you trying to run PicoLisp > on, > > Linux, BSD? If you are willing to try using Docker containers I've made > > some slim images of 64-bit PicoLisp. > > running on Linux is no problem, what I tried to do is have a binary that > would run reliably on Windows and inside Wine/Linux. > It appears the tools are not good enough yet to make that easy. > > Richard > > -- > Name and OpenPGP keys available from pgp key servers > > > -- > UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe >
Re: anyone tried cygwin or mingw recently?
On Sun, Jul 16, 2017 at 12:21:39PM -0400, David Bloom wrote: Hi, > Hi Richard. If you want to get PicoLisp running on windows compilation can > be difficult but you mention wine. What are you trying to run PicoLisp on, > Linux, BSD? If you are willing to try using Docker containers I've made > some slim images of 64-bit PicoLisp. running on Linux is no problem, what I tried to do is have a binary that would run reliably on Windows and inside Wine/Linux. It appears the tools are not good enough yet to make that easy. Richard -- Name and OpenPGP keys available from pgp key servers -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Re: anyone tried cygwin or mingw recently?
On Jul 16, 2017 10:33 AM, "Richard Z" wrote: On Sun, Jul 09, 2017 at 02:06:05PM -0400, r...@tamos.net wrote: Hi, > Curious, if you gave Msys2 a try, as Mike was asking about here: unfortunatley, msys2 (like cygwin) doesn't work with my wine installation so I am out of luck for this project. Also, it seems the float support of picolisp would make my project too troublesome. Richard Hi Richard. If you want to get PicoLisp running on windows compilation can be difficult but you mention wine. What are you trying to run PicoLisp on, Linux, BSD? If you are willing to try using Docker containers I've made some slim images of 64-bit PicoLisp. See: https://hub.docker.com/r/progit/pil-minimal/ And https://hub.docker.com/r/progit/pil-enhanced/ I hope this helps ease you into running PicoLisp. -David
Re: anyone tried cygwin or mingw recently?
On Sun, Jul 09, 2017 at 02:06:05PM -0400, r...@tamos.net wrote: Hi, > Curious, if you gave Msys2 a try, as Mike was asking about here: unfortunatley, msys2 (like cygwin) doesn't work with my wine installation so I am out of luck for this project. Also, it seems the float support of picolisp would make my project too troublesome. Richard -- Name and OpenPGP keys available from pgp key servers -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Re: anyone tried cygwin or mingw recently?
> > > Does MSYS handle fork? > > yes.
Re: anyone tried cygwin or mingw recently?
On Sun, Jul 09, 2017 at 02:06:05PM -0400, r...@tamos.net wrote: Hi Rick, > Curious, if you gave Msys2 a try, as Mike was asking about here: > > On Thu, 06 Jul 2017 13:07 +0300, Mike Pechkin wrote: > > Richard, > > > > I've compile picoLisp under msys (http://www.msys2.org/) > > and 'ctl' locking works here. > > You should a try. will give it a try.. I have it works better that cygwin with wine because I don't even have windows here;) Does MSYS handle fork? Richard -- Name and OpenPGP keys available from pgp key servers -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Re: anyone tried cygwin or mingw recently?
Hi, Richard! Curious, if you gave Msys2 a try, as Mike was asking about here: On Thu, 06 Jul 2017 13:07 +0300, Mike Pechkin wrote: > Richard, > > I've compile picoLisp under msys (http://www.msys2.org/) > and 'ctl' locking works here. > You should a try. (Glad to see that joebo chimed in. I wish I could help him too, but I don't think I have the chops or time.) Cheers, --Rick -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Re: anyone tried cygwin or mingw recently?
On Wed, Jul 05, 2017 at 02:00:51PM -0400, Joe Bogner wrote: Hi Joe, thanks for your answer. > I'm not sure about mingw/cygwin but I do have an unofficial port of pil-64 > that runs on windows using midipix -- > https://github.com/joebo/picoLisp-win-x86-64 out of curiosity, does the 32bit port run on w64? > Aside from a proof of concept, I haven't moved forward on keeping this up > to date with the latest pil or pushing it forward. If there was community > interest, I'd be more motivated to push it forward sadly, I can't help and with all that issues it would seem too risky for the project that I was thinking about. Richard -- Name and OpenPGP keys available from pgp key servers -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Re: anyone tried cygwin or mingw recently?
Richard, I've compile picoLisp under msys (http://www.msys2.org/) and 'ctl' locking works here. You should a try. On Wed, Jul 5, 2017 at 4:20 PM, Alexander Burger wrote: > On Wed, Jul 05, 2017 at 02:27:34PM +0200, Richard Z wrote: > > > We now checked with Mike. Seems most of it is still needed. So we just > did the > > > first case in src/io.c > > > > so database locking now works (minus ocassional Windows bugs)? > > Unfortunately not. It just passes compilation. We tested with 'ctl'. It > just > seems to ignore the lock under Cygwin. > > ♪♫ Alex > > -- > UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe >
Re: anyone tried cygwin or mingw recently?
Hi Richard, I'm not sure about mingw/cygwin but I do have an unofficial port of pil-64 that runs on windows using midipix -- https://github.com/joebo/picoLisp-win-x86-64 My port has somewhat stalled as midipix is moving a bit slower than I expected. If I recall, most tests were passing and it worked reasonably well for prototyping on windows. I wouldn't use it for production apps Sockets and forking seemed to be stable and fast. Database locking does not work though. I started to look into using the windows api to lock (LockFile)... but stopped as midipix was going to be adding support for it "soon" as-of 6 months ago or so. It's not been added to midipix yet. If it was needed, I think it could be added to the shim and then incorporated into the assembly code https://github.com/joebo/picoLisp-win-x86-64/blob/master/src64/arch/win-x86-64-native_shim.c Aside from a proof of concept, I haven't moved forward on keeping this up to date with the latest pil or pushing it forward. If there was community interest, I'd be more motivated to push it forward Thanks, Joe On Sun, Jul 2, 2017 at 1:37 PM, wrote: > On Sun, 02 Jul 2017 19:07 +0200, Richard Z wrote: > > Did anyone test it recently? > > Hi Richard, > > Hopefully, joebo will comment on this. He is the one I know for sure > who has looked into mingw-type builds of picolisp this the past year. > > Best, --Rick > > -- > UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe >
Re: anyone tried cygwin or mingw recently?
On Wed, Jul 05, 2017 at 02:27:34PM +0200, Richard Z wrote: > > We now checked with Mike. Seems most of it is still needed. So we just did > > the > > first case in src/io.c > > so database locking now works (minus ocassional Windows bugs)? Unfortunately not. It just passes compilation. We tested with 'ctl'. It just seems to ignore the lock under Cygwin. ♪♫ Alex -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Re: anyone tried cygwin or mingw recently?
On Tue, Jul 04, 2017 at 11:04:16AM +0200, Alexander Burger wrote: > On Mon, Jul 03, 2017 at 04:42:32PM +0200, Alexander Burger wrote: > > > Cool! So I can safely remove it? It looks ugly indeed ;) > > > > Looking at it, there are move such "ifndef __CYGWIN__" lines, besides the > > above > > from "src/io.c" alsoin "src/pico.h" and "src/main.c". > > > > Rather ugly stuff, even renaming 'main' to 'main2'. I would be glad to > > throw all > > that garbage out. > > We now checked with Mike. Seems most of it is still needed. So we just did the > first case in src/io.c so database locking now works (minus ocassional Windows bugs)? Richard -- Name and OpenPGP keys available from pgp key servers -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Re: anyone tried cygwin or mingw recently?
On Mon, Jul 03, 2017 at 04:42:32PM +0200, Alexander Burger wrote: > > Cool! So I can safely remove it? It looks ugly indeed ;) > > Looking at it, there are move such "ifndef __CYGWIN__" lines, besides the > above > from "src/io.c" alsoin "src/pico.h" and "src/main.c". > > Rather ugly stuff, even renaming 'main' to 'main2'. I would be glad to throw > all > that garbage out. We now checked with Mike. Seems most of it is still needed. So we just did the first case in src/io.c ♪♫ Alex -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Re: anyone tried cygwin or mingw recently?
On Mon, Jul 03, 2017 at 04:29:23PM +0200, Alexander Burger wrote: > Hi Mike, > > > > noticed that the code still has > > > > > > #ifdef __CYGWIN__ > > > #include > > > #define fcntl(fd,cmd,fl) 0 > > > #endif > > > > > > > on my cygwin it compiles and pass buildin tests without code above > > Cool! So I can safely remove it? It looks ugly indeed ;) Looking at it, there are move such "ifndef __CYGWIN__" lines, besides the above from "src/io.c" alsoin "src/pico.h" and "src/main.c". Rather ugly stuff, even renaming 'main' to 'main2'. I would be glad to throw all that garbage out. ♪♫ Alex -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Re: anyone tried cygwin or mingw recently?
Hi Mike, > > noticed that the code still has > > > > #ifdef __CYGWIN__ > > #include > > #define fcntl(fd,cmd,fl) 0 > > #endif > > > > on my cygwin it compiles and pass buildin tests without code above Cool! So I can safely remove it? It looks ugly indeed ;) ♪♫ Alex -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Re: anyone tried cygwin or mingw recently?
On Sun, Jul 2, 2017 at 8:07 PM, Richard Z wrote: > Hi, > > noticed that the code still has > > #ifdef __CYGWIN__ > #include > #define fcntl(fd,cmd,fl) 0 > #endif > on my cygwin it compiles and pass buildin tests without code above
Re: anyone tried cygwin or mingw recently?
On Sun, 02 Jul 2017 19:07 +0200, Richard Z wrote: > Did anyone test it recently? Hi Richard, Hopefully, joebo will comment on this. He is the one I know for sure who has looked into mingw-type builds of picolisp this the past year. Best, --Rick -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe