[Interest] Build Qt from source in 32bit (-platform macx-clang-32)

[Nuno Santos]

Sorry if you have already told me that. It might have escaped me. Yesterday there was too much information to absorve! :)

I’m currently struggling with the Qt plugins path. It seems that Qt uses qt.conf to tell where the plugins are. If the qt.conf is not found it uses hard coded path. The problem is:

- Even if I use the qt.conf, the prefix is the application path, which is going to be the host program and not the plugin
- If I don’t use qt conf, it will use the hard coded paths used during qt compiling.

Otherwise I would need to define an absolute path for the plugins location, and then the plugins would need to know the location of the qt libs, which is going to a mess.

I think the best option here would be to static linking with the plugins. 

What do you think? 

Nuno

> On 29/05/2015, at 18:26, René J.V. Bertin <rjvbertin at gmail.com> wrote:
> 
> On Friday May 29 2015 17:51:58 Nuno Santos wrote:
> 
> Hi Nuno,
> 
> 
>> The solution is to change the loading path of dependent QtFrameworks to something like this:
>> 
>> install_name_tool -change /Users/nsantos/Qt/5.4/clang_32/lib/QtCore.framework/Versions/5/QtCore @loader_path/../../../QtCore.Framework/Versions/5/QtCore drc.vst/Contents/Frameworks/QtNetwork.framework/QtNetwork
> 
> I think that's what I told you: all shared libraries that you ship and that are to be loaded dynamically must agree on where each is to be found.
> 
> The only thing that you may be able to get away with is setting the id (the first line printed by otool -L, containing the library's own name) to something without a path at all, just the library name. I'm not sure though.
> 
> R.