<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Gcc on Angus Thinks</title>
		<link>https://www.malcolmhardie.com/weblogs/angus/tags/gcc/</link>
		<description>Recent content in Gcc on Angus Thinks</description>
		<generator>Hugo</generator>
		<language>en</language>
		
		
		
			<copyright>@2026 Angus Hardie</copyright>
		
		
			<lastBuildDate>Thu, 26 Oct 2006 00:00:00 +0000</lastBuildDate>
		
			<atom:link href="https://www.malcolmhardie.com/weblogs/angus/tags/gcc/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>static link library to replace dylib in mac os x</title>
				<link>https://www.malcolmhardie.com/weblogs/angus/posts/2006/10/26/static-link-library-to-replace-dylib-in-mac-os-x/</link>
				<pubDate>Thu, 26 Oct 2006 00:00:00 +0000</pubDate>
				<guid>https://www.malcolmhardie.com/weblogs/angus/posts/2006/10/26/static-link-library-to-replace-dylib-in-mac-os-x/</guid>
				<description>&lt;p&gt;&lt;a href=&#34;http://lists.apple.com/archives/xcode-users/2006/Jun/msg00801.html&#34; class=&#34;link-external&#34; rel=&#34;noopener&#34;&gt;This post&lt;/a&gt;&#xA; on the xcode-users list explains a neat trick on how to get xcode to link a static library instead of a dynamic library.&lt;/p&gt;&#xA;&lt;p&gt;Imagine the circumstance: you want to use a particular non-standard version of a native library which is already part of the system; perhaps you want to use an old version with better compatibility, or a newer version with more features. The obvious thing to do is to take a static build of the library and add it your xcode project.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
