General Category > LisaList2
LisaEm 1.2.7-RC4 support bug reports
rayarachelian:
New Beta release is pending. Watch this thread, likely this weekend, or Monday the latest with a focus on macos x This will include the new macos version selector script as described above, and a rebuilt script for creating wxWidgets on macos. I guess you can go on a virtual easter egg hunt, where the eggs are bugs and report them here. ::)
rayarachelian:
Phrew, that was a marathon of Yak Shaving. This is named 2020.03.31 because that's when the final source code changes were made, it's released today because I spent about two weeks shaving a very big Yak - namely (mostly) automating the dmg creation process and setting up a bunch of macos Virtualbox VMs to be able to create obese binaries for macos x.
* https://lisaem.sunder.net/downloads/LisaEm_1.2.7-BETA_-_2020.03.31.dmg
* https://lisaem.sunder.net/downloads/lisaem-1.2.7-2020.03.31.tar.xz
* https://github.com/rayarachelian/lisaem/This release contains binaries for macos x 10.8, 10.10, 10.11, 10.12 and 10.15 x86_64. On startup it will run whichever matches the OS most closely. This doesn't contain i386 binaries, nor PPC binaries, but the final release likely will. It's likely this will run on 10.7, as it was compiled on 10.8 with min macos SDK 10.7, but I don't have a way to test it there as I don't have a 10.7 VM.
While I do have a 10.9 VM, compiling under it does not produce viable binaries - LisaEm compiles successfully there but immediately crashes on startup, and I'm not sure why. I've peeled off some layers of that onion, but got nowhere, so I'll just rely on 10.8 binaries working on 10.9.x.
It's not necessary to make a bespoke binary for every os, but it's likely a good idea to build one for every major change so that the best combination of binary + wxWidgets library is provided. For example, the 10.8 in this release uses wx3.0.4, but the 10.15 one uses wx3.1.3, so it should pick up the latest fixes. (wx3.1.3 does not compile on macos 10.8 )
To mostly fix the worst display artifacts I had to switch to a double buffered wxDC, which causes display refreshing to be very slow. I'll hack on this some more until I find a better solution, so hopefully this is temporary, but it gets rid of the nasty flashing on macos x.
Next, I'll be continuing on the display artifacts issue, and then will add a couple more features, and that will lead to the final 1.2.7 release if all goes well.
rayarachelian:
Edit: 2020.06.05 updated with new links, source + dmg.
RC1 is ready for download here: https://lisaem.sunder.net/downloads/ - here are the relevant direct links:
* https://lisaem.sunder.net/downloads/lisaem-1.2.7-2020.05.27.tar.xz* https://lisaem.sunder.net/downloads/lisaem-1.2.7-RC1-2020.05.27-macos-10.10-x86_64.pkg
* https://lisaem.sunder.net/downloads/lisaem-1.2.7-RC1-2020.05.27-macos-10.11-x86_64.pkg
* https://lisaem.sunder.net/downloads/lisaem-1.2.7-RC1-2020.05.27-macos-10.12-x86_64.pkg
* https://lisaem.sunder.net/downloads/lisaem-1.2.7-RC1-2020.05.27-macos-10.15-x86_64.pkg
* https://lisaem.sunder.net/downloads/lisaem-1.2.7-RC1-2020.05.27-macos-10.5-i386.pkg
* https://lisaem.sunder.net/downloads/lisaem-1.2.7-RC1-2020.05.27-macos-10.5-ppc.pkg
* https://lisaem.sunder.net/downloads/lisaem-1.2.7-RC1-2020.05.27-macos-10.7-x86_64.pkg
* https://lisaem.sunder.net/downloads/lisaem-1.2.7-RC1-2020.05.27-macos-10.8-x86_64.pkg
* https://lisaem.sunder.net/downloads/LisaEm_1.2.7-RC1_2020.05.27-macosx.dmg
The packages (pkg) will install both the LisaEm.app to /Applications as well as the command line tools to /usr/local/bin/ but these are skinny versions of LisaEm - that is they only hold the executable built from a specific macos x machine. They should run on machines with macos x of the same version or newer.
The DMG has the new "obese" "swole" binaries (on 2nd thought swole is a better word than obese), so if you install from there, you'll be able to move it around between systems, but the binary will be much larger 38MB rather than the 7~12MB skinny versions.
The above are small versions with only one macosx binary each. If you try to run one that's not suitable for your system, it will fail to start. ie. trying to run the 10.5-ppc versions on 10.15 which only wants x86-64.
The command line tools inside the Command Line Tools folder are packages that only install the CLI tools, but you'll need to specifically install the right one for your os. The packages will not block you from installing the wrong versions as there's no test script in them (yet).
These were built using a master script that powers on a vbox vm, waits for it to come up, ssh's into it and builds for that os, then shuts it down and repeats until all are done. The final one also builds the DMG. Since the 10.5-ppc was built on a 10.5 intel VM, and I haven't yet tested it, it might not work.I was hoping that the 10.5 version would work on 10.4, but sadly it does not. I've not been able to get a wxWidgets 3.x to compile properly on 10.4. :-\
Similarly for some reason I couldn't compile i386 versions on 10.7 and above, only x86_64 builds properly. There's some linking issue vs wxWidgets 3.0.2 and 3.0.4.But this is ok as the last of the actual 32 bit mac os x was 10.6, and while you could run 32 bit binaries all the way to 10.14, it doesn't offer much of an advantage to do so over a 64 bit binary.
Enjoy. :D
jamesdenton:
Hi Ray,
Trying to boot off an existing ProFile image returns the following error:
"I'm sorry, the emulation has aborted due to a fatal error
cpu68k_makeipclist: But! ipc is null!
Stopped at cpu68k.c:cpu68k_makeiplist:1071 with code :501"
Also, browsing to select a ProFile seems to want to only create a new profile image, potentially overwriting an existing file.
rayarachelian:
--- Quote from: jamesdenton on June 01, 2020, 10:43:09 am ---Hi Ray,
Trying to boot off an existing ProFile image returns the following error:
"I'm sorry, the emulation has aborted due to a fatal error
cpu68k_makeipclist: But! ipc is null!
Stopped at cpu68k.c:cpu68k_makeiplist:1071 with code :501"
--- End quote ---
Ouch, is this on 10.15? Does it also happen with the same image on older betas or 1.2.6?
--- Quote from: jamesdenton on June 01, 2020, 10:43:09 am ---Also, browsing to select a ProFile seems to want to only create a new profile image, potentially overwriting an existing file.
--- End quote ---
I think that's normal, although misleading as that field allows you to just set the location, it won't actually overwrite it. If there's no profile at that path, it will prompt you on power on to select what size to create.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version