Re: picolisp on windows

2019-02-03 Thread Alexander Burger
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


Re: picolisp on windows

2019-02-03 Thread C K Kashyap
Thanks rcs,
I'll go ahead and start using picolisp built with mingw-32 for now and
familiarize myself with it.
Thanks for the confirmation - it's good to know that it works :)
Regards,
Kashyap

On Sun, Feb 3, 2019 at 7:31 PM r cs  wrote:

> Kashyap:
>
> In case you didn't know this, MinGW produces MSVC executables compatible
> with normal Windows, so you just can grab the EXE out of the msys
> environment and run it on any computer where the MSVC redistributable from
> Microsoft has already been installed.
>
> 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.
>
> Cheers,
> rcs
>
> On Sun, Feb 3, 2019 at 9:55 PM C K Kashyap  wrote:
>
>> Hi,
>>
>> I'd like to use picolisp built on MSVC. I am planning to start trying to
>> compile miniPicoLisp (it should really be nano :) ) using MSVC.
>>
>> I was wondering if anyone has already done this.
>>
>> MinGW does not quit work for me (I don't have strong technical reasons
>> for this). WSL does not work for me because I intend to use existing DLLs
>> which I don't suppose would be straightforward to use from WSL.
>>
>> Regards,
>> Kashyap
>>
>
>
> --
> *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

2019-02-03 Thread r cs
Kashyap:

In case you didn't know this, MinGW produces MSVC executables compatible
with normal Windows, so you just can grab the EXE out of the msys
environment and run it on any computer where the MSVC redistributable from
Microsoft has already been installed.

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.

Cheers,
rcs

On Sun, Feb 3, 2019 at 9:55 PM C K Kashyap  wrote:

> Hi,
>
> I'd like to use picolisp built on MSVC. I am planning to start trying to
> compile miniPicoLisp (it should really be nano :) ) using MSVC.
>
> I was wondering if anyone has already done this.
>
> MinGW does not quit work for me (I don't have strong technical reasons for
> this). WSL does not work for me because I intend to use existing DLLs which
> I don't suppose would be straightforward to use from WSL.
>
> Regards,
> Kashyap
>


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


picolisp on windows

2019-02-03 Thread C K Kashyap
Hi,

I'd like to use picolisp built on MSVC. I am planning to start trying to
compile miniPicoLisp (it should really be nano :) ) using MSVC.

I was wondering if anyone has already done this.

MinGW does not quit work for me (I don't have strong technical reasons for
this). WSL does not work for me because I intend to use existing DLLs which
I don't suppose would be straightforward to use from WSL.

Regards,
Kashyap