Re: web/xml/porting porting.en.xml,1.2,1.3

Daniel Macks <[email protected]> said:
>
> Remove very-old and no-longer-useful section.
>
>===================================================================
> RCS file: /cvsroot/fink/web/xml/porting/porting.en.xml,v
> --- porting.en.xml	12 Mar 2004 15:06:20 -0000	1.2
> +++ porting.en.xml	10 Mar 2005 20:01:09 -0000	1.3
> @@ -364,71 +364,6 @@
> </ol>
> </section>
>  
> -<section name="dylibversionfix">
> -<title>Fixing version strings for libtool generated dylibs</title>
> -<p>Libraries generated by libtool might have the wrong version numbers. This is caused by a wrongly used flag in the packages Makefile.
> -When libtool is called in a Makefile like this:
> -<code>
> --release "version"
> -</code>
> -the resulting binaries after the make command has been run will be:
> -</p>
> -<ol>
> -<li> libname.dylib</li>
> -<li> libname-"version".dylib</li>
> -</ol>
> -<p>
> -You can easily tell if <code>-release</code> is used in your Makefile. You may notice the <em>-</em> after the libraries name. This indicates that libtool is called with <code>-release</code> to generate the binaries.
> -
> -In some other cases the resulting libraries might look something similar to this:
> -</p>
> -
> -<ol>
> -<li>libname.dylib</li>
> -<li>libname-"version".x.x.x.dylib</li>
> -</ol>
> -<p>
> -indicating that both flags, namely <code>-release</code> and <code>-version-info</code> were being used.
> -</p>
> -<p>
> -Setting the correct <code>-version-info</code> can be a complicated task. Apple provides some excellent information in their Developer Tools documentation. 
> -Since you are running Fink you will have some sort of developer tools installed. A precise explanation of libtool linking on recent Mac OX Systems can be found in this <link url="file://localhost/Developer/Documentation/DeveloperTools/libtool/libtool_6.html#SEC34"> document</link>.
> -To make sure that this document is complete an abbreviated version of the document mentioned above is included
> -</p>
> -<p>
> -Quoting from the developer documentation:
> -<tt>libtool library versions are described by three integers:</tt>
> -</p>
> -
> -<ul><li>
> -<em>current</em>
> -<p>
> - The most recent interface number that this library implements.
> -</p>
> -</li>
> -<li>
> -<em>revision</em>
> -<p>
> - The implementation number of the current interface. 
> -</p>
> -</li>
> -<li>
> -<em>age</em>
> -<p>
> -The difference between the newest and oldest interfaces that this library implements. In other words, the library implements all the interface numbers in the range from number current - age to current.
> -If two libraries have identical current and age numbers, then the dynamic linker chooses the library with the greater revision number. 
> -</p>
> -
> -</li>
> -</ul>
> -<p>
> -More Information on setting and updating library version numbers using libtool can be found at the link mentioned above. Creating new and updating existing version numbers via <code>-version-info</code> is extensively covered.
> -</p>
> -
> -</section>
> -
> -
> -
> <section name="notes"><title>Further Notes</title>
> <p>For more information on libtool itself and what it does, see the <link url="http://www.gnu.org/software/libtool/libtool.html">libtool homepage</link>.</p>


-- 
Daniel Macks
[email protected]
http://www.netspace.org/~dmacks




-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click