Hello Simon, not at my terminal, but the best way to fix for MyGui 3.4.2 is to edit the debian/rules files to add this extra cmake option: -DCMAKE_BUILD_TYPE="RelWithDebInfo" this is what makes the build usable.
so for example: # build for OpenGL - Release configuration dh_auto_configure -- -DCMAKE_BUILD_TYPE=RelWithDebInfo -DMYGUI_BUILD_DEMOS=FALSE -DMYGUI_RENDERSYSTEM=4 \ -DMYGUI_BUILD_DOCS=TRUE -DMYGUI_BUILD_PLUGINS=FALSE \ -DMYGUI_BUILD_TOOLS=FALSE -DMYGUI_USE_SYSTEM_GLEW=TRUE I'd fix that for all 3 plugins. Cheers, Bret On Mon, Aug 28, 2023 at 3:06 PM Simon McVittie <s...@debian.org> wrote: > Control: reassign -1 src:mygui 3.4.2+dfsg-1 > Control: affects -1 + openmw > > On Mon, 28 Aug 2023 at 13:17:22 +0200, bret curtis wrote: > > On Sun, Aug 13, 2023 at 5:33 PM dwimo <dwinomor...@gmail.com> wrote: > > > After starting a new game [of openmw] the crosshair and the > interactive prompts > > > (fe. typing in your name, clicking 'ok' or 'yes'/'no') and the menus > > > for character creation are not visble. They do seem to respond though > > > (fe. clicking exit in the menu and then pressing enter stops the game > > > like expected). > > > Otherwise it seems I can play the game normally, except from being > unable > > > to create a character I want (because I don't now what has been > selected) > > > > the issue is with MyGUI, a known issue, resolved upstream.[1] The problem > > is that unless a config release type is defined, it will produce a broken > > build. So there are two fixes proposed: > > > > 1) rebuild MyGUI 3.4.2 but set the build to: RelWithDebugInfo > > > > 2) upload MyGUI 3.4.3 which I've already prepared here: > > https://mentors.debian.net/package/mygui > > > > Caveat: 3.4.3 will require a patch for OpenMW 0.48 to support as there > are > > ABI changes. :( > > > > Could someone recategorize this error as being caused by MyGUI 3.4.2 > > please? [2] > > Reassigning to mygui as requested. > > If the fixed upstream release breaks ABI and will require a transition, > then I think it would be best if someone can prepare and test a patch > for 3.4.2 to get this fixed (either by changing the build options or > by patching upstream source to fix the bug), and then the transition to > 3.4.3 can be a separate change. > > smcv >
