Am 29.09.2009 19:45, schrieb imm: > Edzard Egberts wrote: > >> 3. Konfiguration of wine regarding to libgcc_s_sjlj-1.dll, see > > Hmm, which version of gcc did your cross-compiler install?
mingw32-gcc-4.4.0-0.7.fc11 (i586) is the package and gcc --ver tells gcc-Version 4.4.1 20090725 (Red Hat 4.4.1-2) (GCC) > That DLL is used to do exception handling and propagation (I think the > sjlj bit stands for "short-jump long-jump" or something) and is used > when you are using a shared libgcc, built using a 4.x series gcc. Yes, I also tried to find out, what this is good for and it is ment for passing exceptions between dlls. But I did'nt really understand, what this is good for. %) > As far as I know, the mingw core stuff stopped at around gcc 3.4.5 > whilst they worked around this issue (that DLL is not needed with builds > using gcc 3.4.5) and I think that is the recommended stable option still. Yes, you are right - the most recent stable MinGW version is "gcc version 3.4.5 (mingw-vista special r3). When using this, no dll is needed and for the moment I think, I should use this for final releases of "TANtec Studio 4.x". I want to use cross compile for transition development to "TANtec Studio 5", which is ment to use FLTK 1.3 for UTF-8 and should compile at Linux and Windows. When the whole TANtec suite is ported to Linux, I won't need cross compile any more, but it's a bunch of programs... > For gcc 4.x they introduced this DLL, which you need if you link with a > shared gcc, but I am told that you can simply do a "-static-libgcc" in > your build and then you will not need the DLL (although what happens to > exception handling I am not clear about.) What in detail do you mean by simply doing a "-static-libgcc"? This is an option to what? I think, I want to try it out, but how to do? > From gcc 4.4 (or thereabouts) I understand that they have switched to a > DWARF based object format, and that works around the need for this DLL > in some different way - I have not looked into this aspect at all however. "DWARF"? Wow, that sounds really funny - did you know, that "M81 dwarf B" is 15,3 million lightyears away from earth? :o) >> MinGW paths and names, but for a more sophisticated cross compile >> environment it might be useful, to copy the tools and rename them to >> standard names like "i686-pc-mingw32-g++" => g++ > > I wouldn't do this - too risky! > The long names are better, since they explicitly say what you are > invoking... You are right, but because I want to use Eclipse IDE and didn't find a possibility to change names of toolchains (only possibility to change paths) this seems to be the only way to proceed. Obviously this means, FLTK makefiles are more sophisticated than Eclipse, I'm sorry! ;o) _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
