This fixed it.
In dynlolib.c, change
pLib = (void *)dlopen(r,RTLD_LAZY);
to
pLib = (void *)dlopen(r,RTLD_LAZY|RTLD_GLOBAL);
On Sat, 2019-07-06 at 16:53 -0300, Antonio Scuri wrote:
> IUP itself don't load its libraries.
> If it is like Lua, Scriba is the library loader in this case. Y
IUP itself don't load its libraries.
If it is like Lua, Scriba is the library loader in this case. You will
have to check there and make a test.
Best,
Scuri
Em sáb, 6 de jul de 2019 às 01:09, John Spikowski
escreveu:
> AIR found this reference on the the GNOME dev-list. (same errors)
>
>
AIR found this reference on the the GNOME dev-list. (same errors)
To solve it the Nim application needs to load it's shared libraries
with dlopen(RTLD_GLOBAL).
I'm not sure how to apply this change.
Your tutorial editor opens the OpenDlg and SaveAsDlg just fine fron the
extension module. Only the
I mean a regular IupDialog on the same script, show it then show the font
dialog. Was that?
Em sex, 5 de jul de 2019 às 16:58, John Spikowski
escreveu:
> I tried the Open and SaveAs dialogs(which work fine) before trying the
> Font dialog. Same issue.
>
> If I compile the tutorial simple edi
I tried the Open and SaveAs dialogs(which work fine) before trying the
Font dialog. Same issue.
If I compile the tutorial simple edit example as a standalone
executable, the Font dialog works as expected wth no errrors or
warnings.
Here is my extension module calls.
/*Ihandle* IupFontDlg(void);
Can you try to add another dialog in the same example, but shown before
the font dialog?
Best,
Scuri
Em sex, 5 de jul de 2019 às 01:09, John Spikowski
escreveu:
> It works fine as a standalone executable.
>
> No errors until IupPopup() of the FontDlg occurs.
>
> Could I be missing something
It works fine as a standalone executable.
No errors until IupPopup() of the FontDlg occurs.
Could I be missing something in my extension module make?
On Thu, 2019-07-04 at 21:05 -0300, Antonio Scuri wrote:
> Don't know. Seems to be something inside GTK. If you take a look at
> iup/src/gtk/iupgt
Don't know. Seems to be something inside GTK. If you take a look at
iup/src/gtk/iupgtk_fontdlg.c you will see that the IUP code is quite
simple, GTK does all the work.
Maybe something in GTK was not initialized correctly when running the
script. Missing IupOpen?
Best,
Scuri
Em qui, 4 de jul
Hi Antonio,
I'm trying to reproduce your simple editor tutorial using the
ScriptBasic IUP extension module on the Raspberry Pi 3 B which I
compiled an IUP distribution for. Everything seems to be working fine
other than those wierd warning messages you told me to ignore. I just
cant seem to get th
