Am Dienstag 04 Dezember 2007 schrieb Mike Jackson:
> > 2.1) I'm not sure but I don't think linux is working this way isn't
> > it ?
>
> No. Linux and to some extent windows do not work this way. Then
> again, windows has "DLL Hell" because all the dlls are just put in
> the same directory.
Or in t
Mike,
Thank again for your answers. I checked your tool and it seems to work great
here. I will add some more features (QT4 sublibs) to it and send you the
patch asap.
I will follow your advices and concentrate my efforts on making my bundle
"the good way".
Regards,
Félix C. Morency
On Dec 4, 2
On Dec 4, 2007, at 4:46 PM, Félix C. Morency wrote:
Mike,
Thank you for your precise answer. I will try this tomorrow. I have
few other questions for you:
1.0) Why isn't CMake doing this automatically ?
CMake will set the "install_path" for you if you use the
SET_TARGET_PROPERTIES macr
Mike,
Thank you for your precise answer. I will try this tomorrow. I have few
other questions for you:
1.0) Why isn't CMake doing this automatically ?
1.1) Is is just a CMake's missing feature or is there any technical issues ?
I think QMake does it for you isn't is ?
2.0) I'm sure Apple has plen
Welcome to the "can of worms" called "install_name_tool" on OS X.
Yes, you can change 3rd party libs.. with one BIG caveat. Who ever
compiled it needs to have compiled with the -
Header_Pad_Max_install_Names (or something like that). If that was
done then you should be able to change the lib
Hi,
The INSTALL_NAME_DIR is a string specifying the directory portion of the
"install_name" field of shared libraries on Mac OSX to use in the installed
targets (as taken from the current documentation). Is there any way of
setting this property on a third party lib ? I checked the current CVS
CMa
