Re: relocatable guile on windows
Mike Gran writes: Hi! > For reasons why you shouldn't use Microsoft Windows ever, see: > https://www.gnu.org/philosophy/upgrade-windows.html Right. No-one in their right mind should ever use Windows. Sadly, people even pay for this stuff. Having said that, great work! > Almost all instances of the long integer are replaced with intptr_t, > since on 64-bit Windows, sizeof(long) < sizeof(void *), in violation > of Guile's expectations. Largely janneke did this work, but, I added > a couple more. Now that you found more, do you know if JIT works? I couldn't get it to work on wip-mingw, so I've been using --disable-jit. Greetings, Janneke -- Janneke Nieuwenhuizen | GNU LilyPond https://LilyPond.org Freelance IT https://www.JoyOfSource.com | Avatar® https://AvatarAcademy.com
Re: OpenCV binding
As a follow-up to this, some recent bindings for OpenCV to other languages use "unofficial" (not OpenCV supported) C bindings generated by the binding authors themselves to bind... for example Go's gocv contains C APIs generated from using libclang to parse OpenCV C++ headers and these C APIs are then used for bindings to Go, and D. I read that Java and Python OpenCV bindings were also made this way but I did not confirm them. Wonder if this is the way to go for accessing modern OpenCV from guile? On Thu, Sep 8, 2022 at 11:59 AM Hans Åberg wrote: > > > > On 8 Sep 2022, at 19:54, David Pirotte wrote: > > > >> curious if there is OpenCV binding for guile? and anything like NumPy > >> for guile? > > > > No, and currently that would not be possible, as Open-CV is written in > > C++ and there no ffi for C++ code ... > > I wrote a C++ wrap for Guile, and the opposite is also possible with GCC, > only that C++ exceptions do not work properly: > https://lists.gnu.org/archive/html/guile-user/2010-05/msg00035.html > >
Re: [EXT] relocatable guile on windows
Hi Mike, On Sat, Dec 3, 2022 at 9:49 PM Mike Gran wrote: > > Hello Guile, > > The Lisp Game Jam was a few weeks ago, and in prep, I took a stab an > making Guile work better on Windows, using MinGW MSys64 UCRT64 for > compilation. Little did I imagine that it would take a couple months > to make something servicable, so I never got around to actually making > a game. > > This Guile is a fork with a lot of hacks for Windows: lack of > POSIX shell, DLL nonsense, Windows filesystem instead of FHS, > yadda yadda yadda. The biggest hack is that of making > all the file paths relative to the guile executable, so that > it can be distributed as a single zip file or MSIX install file. I haven't had a chance to try this out yet but I wanted to say that this is great work! I'd really like to have a good story to tell for shipping games built with Guile and Chickadee on Windows. In the past I've tried to cross-compile Guile for Windows from Linux and made it as far as getting Guile 3 to boot, but the JIT didn't work and I think threads, though enabled, were broken. I haven't used Windows for development in over 10 years so I'm somewhat helpless when things go wrong. It would be really great if we could organize a bit around upstreaming patches for proper Windows support and come up with some documentation with official recommendations for how to build for Windows. I never know what the best approach is: cygwin? mingw? native build (more work than the other two)? A lot of other Scheme implementations run on Windows, so Guile should, too. - Dave
