On Thursday, September 12, 2002, at 02:09 PM, Benjamin Reed wrote: > > Well, the ones in experimental were not necessarily kept up-to-date > after I released into the 10.2 tree, so I'm not sure those are totally > up-to-date, but still they should fix it. > > If they don't then I'm not sure what to tell you, other than it is some > kind of Qt build issue. > > Keep in mind we're not using Qt as it's intended... they do have a > whole > lot of MacOSX-specific code in the qt-free tree, but it's all based > around the native Qt/Mac port, so some of it may actually cause issues > with running under x11 on OSX. It's very possible that we've missed > something that needs to be turned on to make Qt see these extra > plugins, > but I'm not sure what to tell you. > > One thing to make sure of is that you've rebuilt KDE after upgrading to > Qt 3.0.5 -- if your KDE was built against 3.0.4 you won't be able to > see > *any* of the plugins, because 3.0.4 -> 3.0.5 broke plugin binary > compatibility. > > Other than that, I'm stumped. I know enough to get Qt building and > such, but I don't understand the Qt internals enough to know where to > look to fix this issue.
OK, thanks. I only wanted to know, if there were any changes i should know. I don't use KDE - so there I have no problems ;) I thought, because of the qt-interest-archive-link, the problems are fixed and tested, and I've made an error. Only one question: the patch from then is also in the current build (qt 3.0.5-5) ? Nico ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Fink-beginners mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-beginners
