Re: [Chicken-users] Installing chicken on windows

[Dan Leslie]

Oops, you shouldn't need to install cmake and global. I copy/pasted that
from my Emacs setup readme.

-Dan


On 2016-07-09 5:36 PM, Dan Leslie wrote:
>
> I have just returned from vacation and have access to my Windows 10
> machine again, and so can try out my setup.
>
> Here's what I have done:
>
> Install 64-bit MSYS2, launch bash using the MingW64 shell:
>
> |https://msys2.github.io|
>
> Install the necessary dependencies:
>
> |pacman -Sy pacman -S mingw-w64-cross-toolchain base-devel
> mingw64/mingw-w64-x86_64-cmake global|
>
> Build and install Chicken:
>
> |tar xf chicken-4.11.0.tar.gz; cd chicken-4.11.0 make
> PLATFORM=mingw-msys make PLATFORM=mingw-msys install |
> And now you have a Win64 build of Chicken.
>
> Note that I also install and use Emacs this way, and interface with
> Chicken through Geiser.
>
> -Dan
>
> On 2016-07-09 4:38 PM, Matt Gushee wrote:
>>
>>
>> On Fri, Jul 8, 2016 at 12:01 PM, Matt Welland > > wrote:
>>
>>
>> Oh, as an aside, it would be fantastic to have IUP be just as
>> easy to install on Linux/Unix. Sadly this is not the case. I have
>> not surveyed the GUI toolkit world recently. Is there a better
>> alternative available for Chicken now?
>>
>>
>> ​I haven't looked around *very* recently, but I've been through many
>> cycles of looking for better GUI toolkits. And everytime I've looked,
>> I seem to find the same answer: that IUP is the *only* reasonably
>> modern and full-featured cross-platform GUI toolkit written in plain
>> C. Ah well, GTK is technically written in plain C, but it has its own
>> complex infrastructure. Everything else is C++ - which I suppose
>> would not be impossible to wrap for Chicken, but nobody seems to want
>> to do it.
>>
>> However, I think the IUP situation is getting better. I built the
>> latest versions of IM, CD, and IUP for Arch Linux about a month ago,
>> and I only had to make one minor change to one of the build scripts.
>> Every previous time I've built the packages, I've had to patch
>> Makefiles and other things. So it seems like the IUP team has finally
>> gotten around to addressing some of the problems people have been having.
>>  
>> --
>> ​Matt Gushee​
>>
>>
>>
>> ___
>> Chicken-users mailing list
>> Chicken-users@nongnu.org
>> https://lists.nongnu.org/mailman/listinfo/chicken-users
>



signature.asc
Description: OpenPGP digital signature
___
Chicken-users mailing list
Chicken-users@nongnu.org
https://lists.nongnu.org/mailman/listinfo/chicken-users

Re: [Chicken-users] Installing chicken on windows

[Dan Leslie]

I have just returned from vacation and have access to my Windows 10
machine again, and so can try out my setup.

Here's what I have done:

Install 64-bit MSYS2, launch bash using the MingW64 shell:

|https://msys2.github.io|

Install the necessary dependencies:

|pacman -Sy pacman -S mingw-w64-cross-toolchain base-devel
mingw64/mingw-w64-x86_64-cmake global|

Build and install Chicken:

|tar xf chicken-4.11.0.tar.gz; cd chicken-4.11.0 make PLATFORM=mingw-msys
make PLATFORM=mingw-msys install |

And now you have a Win64 build of Chicken.

Note that I also install and use Emacs this way, and interface with
Chicken through Geiser.

-Dan

On 2016-07-09 4:38 PM, Matt Gushee wrote:
>
>
> On Fri, Jul 8, 2016 at 12:01 PM, Matt Welland  > wrote:
>
>
> Oh, as an aside, it would be fantastic to have IUP be just as easy
> to install on Linux/Unix. Sadly this is not the case. I have not
> surveyed the GUI toolkit world recently. Is there a better
> alternative available for Chicken now?
>
>
> ​I haven't looked around *very* recently, but I've been through many
> cycles of looking for better GUI toolkits. And everytime I've looked,
> I seem to find the same answer: that IUP is the *only* reasonably
> modern and full-featured cross-platform GUI toolkit written in plain
> C. Ah well, GTK is technically written in plain C, but it has its own
> complex infrastructure. Everything else is C++ - which I suppose would
> not be impossible to wrap for Chicken, but nobody seems to want to do it.
>
> However, I think the IUP situation is getting better. I built the
> latest versions of IM, CD, and IUP for Arch Linux about a month ago,
> and I only had to make one minor change to one of the build scripts.
> Every previous time I've built the packages, I've had to patch
> Makefiles and other things. So it seems like the IUP team has finally
> gotten around to addressing some of the problems people have been having.
>  
> --
> ​Matt Gushee​
>
>
>
> ___
> Chicken-users mailing list
> Chicken-users@nongnu.org
> https://lists.nongnu.org/mailman/listinfo/chicken-users



signature.asc
Description: OpenPGP digital signature
___
Chicken-users mailing list
Chicken-users@nongnu.org
https://lists.nongnu.org/mailman/listinfo/chicken-users

Re: [Chicken-users] Asynchronous I/O Egg Release

[Kristian Lein-Mathisen]

Not that I know of, unfortunately. You can do a regex search on
api.call-cc.org and see what you find. But it is my understanding that this
is actually how it's meant to work from core, and so it shouldn't be
necessary in the first place. I am guessing there is a bug ticket somewhere
waiting for someone to fix?

It would be nice to fix this once and for all, perhaps also making stdin
nonblocking so that you don't need parley for that.

K.

On Friday, July 8, 2016, Robert Smiley  wrote:

> In all honesty, I hadn't used the make-input-port procedure before. It
> didn't occur to me to use that to make a nonblocking input port. Your code
> snippet seems to solve the problem quite a bit better than my egg does.
>
> Is open-input-file*/nonblock in a currently released egg?
>
> On Thu, Jul 7, 2016 at 6:04 AM, Kristian Lein-Mathisen <
> kristianl...@gmail.com
> > wrote:
>
>> I don't know how useful this is, but I though I'd throw in a test I use
>> as we've encountered this a few times as well in the posix egg:
>>
>>
>> (use posix srfi-18)
>>
>> (define mythread
>>   (thread-start!
>>(lambda ()
>>  (let loop ()
>>(define start (current-milliseconds))
>>(thread-sleep! 0.1)
>>(define elap (- (current-milliseconds) start))
>>(if (> elap 500) ;; the 0.1 second sleep took > 0.5 seconds!
>>(print "OBS! elap = " elap)
>>(loop))
>>
>> (print "cmd: sleep 1 ; echo hi" (with-input-from-pipe "sleep 1.5 ; echo
>> hi" read-string))
>> (thread-join! mythread)
>>
>> $ csi -version
>> Version 4.9.0.1 (stability/4.9.0) (rev 8b3189b)
>> linux-unix-gnu-x86-64 [ 64bit manyargs dload ptables ]
>> bootstrapped 2014-06-07
>> $ csi -s blocking-io-test.scm
>> cmd: sleep 1 ; echo hihi
>>
>> OBS! elap = 1512.0
>>
>>
>> And this is a code-snippet
>>  
>> we
>> use to solve it.
>>
>>
>> K.
>>
>> On Fri, Jul 1, 2016 at 6:53 PM, Matt Welland > > wrote:
>>
>>>
>>>
>>> On Fri, Jul 1, 2016 at 3:11 AM, Andy Bennett >> > wrote:
>>>
 Hi,

 > And of course, reads of files on the file
 > system never block at all

 A read from a file can block when the operating system needs to go to
 disk for the data. This happens when the buffer empties and it cannot be
 refilled before the next read call.

>>>
>>> I don't know if it applies to this discussion but read blocking can be
>>> quite a pain when a network fileserver such as NFS goes offline. It would
>>> be nice if other threads would continue so that the program could detect
>>> the issue and potentially take appropriate action such as let the user know
>>> *why* the program is hung.
>>>
>>>





 Regards,
 @ndy

 --
 andy...@ashurst.eu.org
 
 http://www.ashurst.eu.org/
 0290 DA75 E982 7D99 A51F  E46A 387A 7695 7EBA 75FF


 ___
 Chicken-users mailing list
 Chicken-users@nongnu.org
 
 https://lists.nongnu.org/mailman/listinfo/chicken-users

>>>
>>>
>>> ___
>>> Chicken-users mailing list
>>> Chicken-users@nongnu.org
>>> 
>>> https://lists.nongnu.org/mailman/listinfo/chicken-users
>>>
>>>
>>
>> ___
>> Chicken-users mailing list
>> Chicken-users@nongnu.org
>> 
>> https://lists.nongnu.org/mailman/listinfo/chicken-users
>>
>>
>
___
Chicken-users mailing list
Chicken-users@nongnu.org
https://lists.nongnu.org/mailman/listinfo/chicken-users

Re: [Chicken-users] Installing chicken on windows

[Matt Gushee]

On Fri, Jul 8, 2016 at 12:01 PM, Matt Welland 
wrote:

>
> Oh, as an aside, it would be fantastic to have IUP be just as easy to
> install on Linux/Unix. Sadly this is not the case. I have not surveyed the
> GUI toolkit world recently. Is there a better alternative available for
> Chicken now?
>

​I haven't looked around *very* recently, but I've been through many cycles
of looking for better GUI toolkits. And everytime I've looked, I seem to
find the same answer: that IUP is the *only* reasonably modern and
full-featured cross-platform GUI toolkit written in plain C. Ah well, GTK
is technically written in plain C, but it has its own complex
infrastructure. Everything else is C++ - which I suppose would not be
impossible to wrap for Chicken, but nobody seems to want to do it.

However, I think the IUP situation is getting better. I built the latest
versions of IM, CD, and IUP for Arch Linux about a month ago, and I only
had to make one minor change to one of the build scripts. Every previous
time I've built the packages, I've had to patch Makefiles and other things.
So it seems like the IUP team has finally gotten around to addressing some
of the problems people have been having.

--
​Matt Gushee​
___
Chicken-users mailing list
Chicken-users@nongnu.org
https://lists.nongnu.org/mailman/listinfo/chicken-users