Exactly Thiago! Why isn't it able to locate the plugins then on other machines then?
Do I need anything else? One curious fact. In this last couple of days I have been trying to deploy a plugin bundle of OSX with Qt frameworks bundled inside the plugin. I have given up when I realized plugins would be a trouble to load due to the paths. I have even tried to put a qt.conf file inside the resources. Curiously, yesterday, I was already using the static compiled qt and the window never opened because it was complaining about the missing modules. I couldn't understand why. Today, I remembered that I had the qt.conf on the resources. I have removed it and guess what. The window opened. It was able to find the modules. But that doesn't happen if I share the plugin bundle with someone else. There is definitely a relation between this facts. I can assure you I'm linking the plugins statically an everything is being built with statically linked qt. How can I go deeper? What is wrong here? Thank you so much, -- Nuno Santos No dia 30/05/2015, às 17:06, Thiago Macieira <thiago.macie...@intel.com> escreveu: >> On Saturday 30 May 2015 15:23:54 Nuno Santos wrote: >> I’m building and compiling a plugin bundle with a statically built version >> of Qt. >> >> The plugin results in a single dll/bundle and loads successfully on my >> computer. > > There's something wrong with this part of the explanation. > > A statically compiled version of Qt does not load plugins. > > -- > Thiago Macieira - thiago.macieira (AT) intel.com > Software Architect - Intel Open Source Technology Center > > _______________________________________________ > Interest mailing list > Interest@qt-project.org > http://lists.qt-project.org/mailman/listinfo/interest _______________________________________________ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
