Hi Kashyap, I've been interested in a picolisp port to Windows for several years. I've tried a number of different options. My last effort was to use https://midipix.org/ as the POSIX layer. It worked OK but then midipix seemed to lose steam with Windows Subsystem for Linux (WSL) coming out. Now, I just use picolisp on WSL.
Reading this thread, https://www.mail-archive.com/picolisp@software-lab.de/msg08551.html, I see that WSL isn't an option because you intend to use existing dlls. Have you considered hosting your DLLs in a HTTP service (e.g. golang) and then calling them from picoLisp running on WSL? That likely would be an easier path to integrate than rewriting the POSIX layer or porting to Windows APIs. It also looks like piping works https://docs.microsoft.com/en-us/windows/wsl/interop so perhaps you can avoid HTTP altogether. Regards, Joe On Sun, Feb 24, 2019 at 9:50 PM C K Kashyap <ckkash...@gmail.com> wrote: > Hi, > I have been considering the idea of getting picolisp to run on windows > (without a heavy weight setup - cygwin/mingw) for a while now. What if I > try and target nasm instead of gnu assembler? That should work. Regarding > the POSIX dependency, I think it should be a matter of making all the > functions (do*) NOPs. I should be able to get a 64bit picolisp calculator > up and running. And then leisurely add the do* functions. > > Ofcourse, if this works, it would be a convenient way to build on mac too! > > Regards, > Kashyap >
