| |
chatGPZ
Registered: Dec 2001
Posts: 11135 |
VICE threaded UI test builds
In this thread i will post test builds of the (hopefully) soon to be merged threaded ui rewrite.
Linux and OSX users can always grab the current state from dqh's git repo here: https://github.com/dqh-github/vice-experiments/tree/threaded-ui.. (make sure to checkout the "threaded-ui-exp" branch after cloning the repo)
Please test and report back positive and negative results. Especially interesting right now are rendering errors/problems and unexpected crashes. Please tell exactly what OS you are using, and what GPU.
I will keep posting new windows builds here - starting with todays: https://sourceforge.net/projects/vice-emu/files/experimental%20..
64bit only right now - i'll have to figure out how to build proper 32bit binaries on my box (not that you should be still using a 32bit OS in 2020). |
|
... 149 posts hidden. Click here to view all posts....
|
| |
dqh
Registered: Jun 2019
Posts: 46 |
JackAsser - btw, have you tried the Xcode support via the —enable-cmake feature? I find it very useful for debugging. |
| |
chatGPZ
Registered: Dec 2001
Posts: 11135 |
and why am i compiling in windows AND ITS SO FUCKING SLOW I WANT TO KILL SOMEONE |
| |
JackAsser
Registered: Jun 2002
Posts: 1989 |
Quote: and why am i compiling in windows AND ITS SO FUCKING SLOW I WANT TO KILL SOMEONE
I do make -j12 on the cmdline, takes about 10s.
Havn’t tried xcode yet? New or legacy build system? |
| |
dqh
Registered: Jun 2019
Posts: 46 |
Just configure in-tree normally, but add --enable-cmake to the configure line to generate a cmake build system from the autoconf makefiles. Or just run cmake-bootstrap.sh on a configured tree.
From there it's usual cmake stuff, i.e. create a build folder, cd to it, then cmake -G Xcode <path to vice folder> to generate an Xcode project. Or even just cmake <path to vice folder> to generate regular makefiles that work faster with make -j than the autoconf ones. And also, the cmake projects let you build a single emu rather than all of them if you want. |
| |
JackAsser
Registered: Jun 2002
Posts: 1989 |
Quote: Just configure in-tree normally, but add --enable-cmake to the configure line to generate a cmake build system from the autoconf makefiles. Or just run cmake-bootstrap.sh on a configured tree.
From there it's usual cmake stuff, i.e. create a build folder, cd to it, then cmake -G Xcode <path to vice folder> to generate an Xcode project. Or even just cmake <path to vice folder> to generate regular makefiles that work faster with make -j than the autoconf ones. And also, the cmake projects let you build a single emu rather than all of them if you want.
Oh thanks! Will definetly try!
Edit: Building in XCode is sooo much faster and nicer than the Make-command-line system. Thanks for that hint! |
| |
dqh
Registered: Jun 2019
Posts: 46 |
No worries, and debugging is a lot nicer than using the command line debugger directly.
FYI if you pull the latest from my threaded-ui-exp branch you’ll get proper retina support, makes a big difference when the CRT filter is enabled. |
| |
JackAsser
Registered: Jun 2002
Posts: 1989 |
Quote: No worries, and debugging is a lot nicer than using the command line debugger directly.
FYI if you pull the latest from my threaded-ui-exp branch you’ll get proper retina support, makes a big difference when the CRT filter is enabled.
Ossom!! |
| |
Burglar
Registered: Dec 2004
Posts: 1033 |
Bug report for latest threaded-ui-exp (commit a4f8366237bdbd39c8ff9384d4aa46297f887669) on linux (Ubuntu 18.04.4 LTS).
I compiled with --enable-new8580filter --enable-native-gtk3ui
x64sc hangs when starting vice with a d64 like /opt/vice-threaded-ui-exp-20200615/bin/x64sc demo.d64
No errors are logged, last vice output: AUTOSTART: Autodetecting image type of `demo.d64'.
Vice is running, window is allocated on screen but completely invisible. I can "focus" on it by clicking the area where it should've been, or by clicking the icon. alt-f4 will then crash the process with the following message:
gnome-shell[30250]: JS ERROR: TypeError: windowActor is null
_removeWindowEffect@resource:///org/gnome/shell/ui/closeDialog.js:90:13
wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22
vfunc_hide@resource:///org/gnome/shell/ui/closeDialog.js:184:9
wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22
Now, the interesting thing is, vice works fine if I just open it directly without a file specified. Selecting a d64 works and emu runs great. |
| |
chatGPZ
Registered: Dec 2001
Posts: 11135 |
....and i can reproduce this here :) smells like a locking issue to me :) |
| |
dqh
Registered: Jun 2019
Posts: 46 |
Yep, it was, related to a recent lock refactoring I did. I have pushed a fix. |
| Previous - 1 | ... | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 - Next |
