X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient: geda-user AT delorie DOT com
X-Cam-AntiVirus: no malware found
X-Cam-SpamDetails: not scanned
X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/
Date: 01 Oct 2011 23:34:37 +0100
From: "Peter C.J. Clifton" <pcjc2 AT cam DOT ac DOT uk>
To: geda-user AT delorie DOT com
Subject: Re: [geda-user] Building PCB with Mac OS X 10.6.8
Message-ID: <Prayer.1.3.4.1110012334370.9767@hermes-2.csi.cam.ac.uk>
In-Reply-To: <CAMonFrRVL2KmKGgt90a9EuDqwHKUCa+GAGU_=yQxMFoPEodfnQ@mail.gmail.com>
References: <9BA5588F-2354-41EC-9B67-740D896945DA AT comcast DOT net>
 <CAMonFrRVL2KmKGgt90a9EuDqwHKUCa+GAGU_=yQxMFoPEodfnQ AT mail DOT gmail DOT com>
X-Mailer: Prayer v1.3.4
Mime-Version: 1.0
Content-Type: text/plain; format=flowed; charset=ISO-8859-1
Sender: "Peter C.J. Clifton" <pcjc2 AT hermes DOT cam DOT ac DOT uk>
Reply-To: geda-user AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: geda-user AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

On Oct 1 2011, Andrea D'Amore wrote:

>To the list: why does PCB patch gts at all? cf. [1]

Aside from the unrelated to the commit-messages changes I've found typical 
in the toporouter code...

I would expect that the purpose of moving the predicate computation to 
runtime (rather than at build time) lets us cross-compile for other target 
architectures (e.g. Win32), without having to know what the results will be 
on that architecture at build time.

But we shouldn't be conflicting with a system install libgts. (I guess we 
probably _are_ conflicting from what you said), but we should get away with 
just statically linking our local copy of that library.

Needs some love to the build scripts I guess.