On 18.03.2010, at 08:55, manolo gouy wrote: >> On 18.03.2010, at 07:52, Matthias Melcher wrote: >>> >>> On 18.03.2010, at 00:22, Albrecht Schlosser wrote: >>> >>> Still, it bugs me that it doesn't work "out of the box". >> >> Well, it did! After you finished your code it worked. The trouble >> began when Manolo moved code around and removed the Fl_Gl_Printer >> class (which was okay). IMHO it is only a technical problem now. >> If you don't reference an object module, the linker won't link it >> into your executable. And that is what happened here.
[...] > I doubt the problem comes from my removing of the Fl_Gl_Printer class. > The thing is linked in: > Fl_Plugin: adding plugin named "opengl.device.fltk.org" at 0x004610B4 > the problem is that it is lost afterwards: > Fl_Plugin: returning plugin named "opengl.device.fltk.org": 0x00000000 > > Also the same code compiled with gcc cross-compiler/cross-linker works, > whereas it fails with gcc on msys+mingw+XP. > There is probably a very subtle bug in the plugin code. Yes, maybe we are both right, and there are two problems. And, BTW, I didn't say it was your fault (it was correct to do what you did), but the problem _began_ for me with svn -r 7281. In retrospect there are some interesting changes: In src/Fl_Device.cxx there are some changes with fl_gc and save_gc that are probably unrelated (they are still there, and it works for me now). In test/cube.cxx you removed two lines with printer.print_gl_window() that would (*maybe*) have referenced the module in question. I don't want to look deeper into this though, it's all history. In test/glpuzzle.cxx you removed all references to Fl_Gl_Printer. To say it again: that was all correct. But this, together with the later removal of the entire class and restructuring the source files, are all evidence that this led to the problem of not linking the object module. But that doesn't explain the effect that you see (and that I can't reproduce here at home). Maybe this is the second problem, and we both (me: in my office sytem) have another MinGW version than my home versions here. I'll try later in the office, if this is another version and if the problem still manifests there. To start with version comparing: My home systems have both mingw-runtime 3.17-1 MinGW says: $ uname -a MINGW32_NT-5.1 PC 1.0.11(0.46/3/2) 2009-07-11 17:46 i686 Msys The installed MinGW/MSYS versions are from: MinGW-5.1.6.exe MSYS-1.0.11.exe Albrecht _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
