Date: Fri, 16 Nov 2012 23:33:31 +0100 From: Maurice Lombardi Maurice.Lombardi@ujf-grenoble.fr Subject: Re: Grx Digest, Vol 8, Issue 12 To: grx@gnu.de Message-ID: 50A6BF3B.2060107@ujf-grenoble.fr Content-Type: text/plain; charset=ISO-8859-1; format=flowed
- provisions in makedefs.grx and in the configure script to build "fat"
binaries. If I correctly understood, it is only necessary to provide multiple -arch instructions to Apple gcc to make that.
Maurice
Feedback from fink reviewers: Depending on changes of the API of grx, the version in the install_name is probably to specific. If the API will not break, i would be better to make it libgrx20X-2.dylib. The complete patch would then be:
-install_name ${libdir}/libgrx20X-2.dylib
In case you plan for an API change with version 2.5.*, it should be 2.4.
All the rest has been received well.
Michael.
Le 19/11/2012 18:53, Schindler Karl-Michael a écrit :
Feedback from fink reviewers: Depending on changes of the API of grx, the version in the install_name is probably to specific. If the API will not break, i would be better to make it libgrx20X-2.dylib. The complete patch would then be:
-install_name ${libdir}/libgrx20X-2.dylib
In case you plan for an API change with version 2.5.*, it should be 2.4.
For this purpose, as in other linux packages, make install actually installs libgrx20X.so.2.4.9 and installs also two symlinks libgrx20X.so.2 pointing to it libgrx20X.so pointing to the previous
I thus provided to install libgrx.2.4.9.dylib with two chained symlinks libgrx20X.2.dylib libgrx20X.dylib
This way there is no problem changing package version -l grx20X always points to the last version installed (and if necessary -l grx20X.2 would always point two the last version of the grx.2 series, incompatible with the old grx.1 series, no more maintained)
Is there any reason that this should not work in Mac OS X ? In fact I found similar practice in XCode.
Maurice
-
Maurice Lombardi -
Schindler Karl-Michael