|
|
> El 27 ago. 2022, a las 07:33, Gonzalo Garramuño <ggarra13@gmail.com> escribió:
>
>
> On 27/8/22 05:37, Manolo wrote:
>> I will insist there's a problem of updating to new FLTK code because this part of your traceback speaks clear :
>> #2 0x105235597 in Fl_Quartz_Graphics_Driver::XDestroyRegion(flCocoaRegion*) Fl_Quartz_Graphics_Driver.cxx:152
>> #3 0x104f7457d in fl_height() fl_draw.H:771
>>
>> Function fl_height() is a 1-liner:
>> return fl_graphics_driver->height();
>> It should call Fl_Quartz_Graphics_Driver::height(). Instead it calls Fl_Quartz_Graphics_Driver::XDestroyRegion()
>> because there's a problem with the layout of class Fl_Graphics_Driver that's essential for access to virtual member functions and was recently changed.
>
> You are probably right. Give me a week or so I can investigate what's going on. I think there might be some other fltk install on my mac screwing things over.
>
Okay. I found what it was. I had some legacy install of fltk in /usr/local/include/FL and albeit I compile to a sandbox, and use CMAKE_PREFIX_PATH, the FindFLTK.cmake script that ships with cmake would pick the includes from /usr/local.
—
Gonzalo Garramuno
ggarra13@gmail.com
--
You received this message because you are subscribed to the Google Groups "fltk.coredev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to fltkcoredev+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/fltkcoredev/A92C0252-60F6-4645-A622-C367B95295EF%40gmail.com.
[ Direct Link to Message ] | |
|
| |