Improve dev setup on Windows

[cben]

This takes small steps towards dev instructions working out-of-the-box on Windows 11, but ultimately, I didn't get Boxer to launch. At least not with LispWorks Personal Edition.

• [x] Replaced some hardcoded paths with computed (taking care with drive letters).

• [x] Documented some defaults that were unobvious to me as a newbie.

  • I wasn't initially clear that on windows I need both C freetype libs AND the patched CL wrapper. On second reading it was pretty clear, doh, but after wasting time debugging issues already patched there I felt it's worth saying explicitly :-)
  • The concept of "home" can be confusing on Windows, depending on what one uses for "git clone" - might be WSL, or git-bash, (well probably not cygwin anymore) etc. - some of these emulate their own concept of "home dir" distinct from %HOMEPATH%.

• [ ] After the prerequisites listed in README, it's supposed to be enough to load src/bootstrap.lisp?
  Well that doesn't work on a clean system, as it attempts (asdf:load-system :boxer-sunrise) but I hadn't fetched most of its dependencies. => Component :CL-GLU not found, required by #<ASDF/SYSTEM:SYSTEM "boxer-sunrise">
  Looks like one needs something like this (but only once):

  (ql:quickload :cl-json)
  (ql:quickload :drakma)
  (ql:quickload :for)
  (ql:quickload :html-entities)
  (ql:quickload :iterate)
  (ql:quickload :pngload)
  (ql:quickload :qbase64)
  (ql:quickload :quri)
  (ql:quickload :serapeum)
  (ql:quickload :zip)
  (ql:quickload :zpng)
  (ql:quickload :3d-matrices)
  (ql:quickload :cl-opengl :verbose t)
  (ql:quickload :cl-glu :verbose t)

  Is there a way to get all deps already declared in the .asd file? Would (ql:quickload :boxer-sunrise) work?

• [ ] Repeatedly running out of LispWorks PE heap limit. 💀

  You are approaching the heap size limit for the Personal Edition of LispWorks. If you choose to continue now you are advised to save your work at regular intervals.

  Especially during (ql:quickload :serapeum). It looks like commenting out the previous quickload lines reduces heap usage - that way I was able to get past serapeum and eventually get to (asdf:load-system :boxer-sunrise), now with (most) dependencies installed.

• [ ] cl-opengl failing to compile:

  **++++ Error in (PACKAGE "CL-OPENGL"): 
  "OPENGL" is already a nickname for #<The OPENGL package, 298/4096 internal, 1678/4096 external>.

  Lndeed it wants this nickname.
  I guess the conflict is with LispWorks' own opengl package? Changelog & docs/development-notes.md suggest you've had both working independently, but HOW?

  Pretty sure at some point last week I did get cl-opengl to install and its examples to run - but I can't reproduce that now 🤷‍♂️.

  I see there was also (defpackage :opengl ... that you just removed (898f9243f2655f0c6a5b2113545f28a287e73e80). But I'm getting this nickname collision both before and after that.

  • I think for cl-opengl examples I also needed pacman -S mingw-w64-x86_64-freeglut ? Is it also needed for Boxer to run? (README only mentions freetype)

---

P.S. sbcl progress is exciting! 🎉👏 I'll probably stop banging my head against LispWorks as I don't want to shell out for a less limited version.

[sgithens]

Thanks @cben ! I just want to let you know I see and appreciate this work, but it will be a few days until I comment more, and it will be good to true up your notes against the windows 10 VM I've been working in.

[sgithens]

I'm spinning up a win11 VM to go with my windows 10 VM, but having read through everything up above, I think I can see through all the issues except the Lispworks PE heap limit... I don't think there is much I can do about that. I had the same issue when I tried to do it on Linux (and got a free 14 day edition, during which I got it working), but with all the libraries and then the boxer source itself, it just happens to top out.

I am almost VERY excited about SBCL, and then ECL, because I'm very keen on it running in WebGL. The SBCL stuff may actually go faster than I think, I made quite a progress just in the few days of hacking on it. Of course it won't have a toolbar or anything at first, but those wrappers will come.

I looked at your changes so far on this, and they seem fine, I just need a few more days to try them out on my VM's, as well as get back on your other points above.

[sgithens]

@cben I committed your changes after testing them with just one change. Commented out the quicklisp load since usually that would be a part of a lisp installs init file. ( I know this is availalbe with lispworks personal... ). Also, I load my quicklisp from a different drive and place on my windows vm, so the personal home dir drive letter didn't work. But anyways, it's there, just uncomment it if quicklisp isn't in your lisps init file. Thanks!

To the other items, yeah, you should be albe to just run quickload:boxer to load all the dependencies... I'm working on trying is out on a machine with the quicklisp repo deleted... need to finagle the startup abit.

Also, thanks for the shorthand for the modified local branches needed.. I just realized there may be another one (or two) that I need to add. Looking at that as well. It seems to be starting up again (and the space key works!) so I will likely roll a windows build as well later this week, early next to match the bug fix build I'm about to make for macOS.