static int native_file_chooser_gtk(int mode)
{
int type = (mode == DIR_CHOOSER) ? Fl_Native_File_Chooser::BROWSE_DIRECTORY : Fl_Native_File_Chooser::BROWSE_FILE;
Fl_Native_File_Chooser fnfc;
fnfc.title(title);
fnfc.type(type);
int ret = fnfc.show();
if (ret != -1 && ret != 1) {
std::cout << quote << fnfc.filename() << quote << std::endl;
return 0;
}
return ret;
}
Starting program: /home/djcj/dev/fltk-dialog/fltk-dialog --file --native
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffec2d5700 (LWP 29631)]
[New Thread 0x7fffebad4700 (LWP 29632)]
[New Thread 0x7fffeb2d3700 (LWP 29633)]
[New Thread 0x7fffea68b700 (LWP 29634)]
free(): invalid pointer
Thread 1 "fltk-dialog" received signal SIGABRT, Aborted.
__GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51
51 ../sysdeps/unix/sysv/linux/raise.c: No such file or directory.
Update: I thought it could have something to do with FLTK 1.4 being built against Pango, but even with Pango set to OFF the same happens.
--
You received this message because you are subscribed to the Google Groups "fltk.general" group.
To unsubscribe from this group and stop receiving emails from it, send an email to fltkgeneral...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
The thing is: I want my tool to be as portable as possible without the need to create an AppImage or a tarball that includes all dependencies.I guess this means I will have to add my own copy of jpeg, png and zlib with prefixed symbols and make sure those are used.
If you need prefixed image libraries whose versions you can control
(which would IMHO be a prerequisite for a closed-source application)
then you should keep your own copy of the image libs and patch them such
that they can use any prefix you want.
Then you could build FLTK using these image libraries and link your
application with the same image libraries. Since all prefixing happens
by defining some macros in the libary headers this should work w/o
patching the FLTK library.
Please correct me if I'm wrong.
> I'm currently doing it, not because I'm working on a closed-source
> project but more for convenience and to see if it works.
Looking forward to your results.
Seems like I'm still encountering issues with Gtk, depending on the platform I build and run it.I guess I have to stick with patching the image library sources, if I really want to keep the automated builds.