X-Spam-Check-By: sourceware.org Message-ID: <4531248C.7030306@cygwin.com> Date: Sat, 14 Oct 2006 13:55:24 -0400 From: "Larry Hall (Cygwin)" Reply-To: cygwin AT cygwin DOT com User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.7) Gecko/20060916 Fedora/1.5.0.7-1.fc4.remi Thunderbird/1.5.0.7 Mnenhy/0.7.4.0 MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: Cygwin and Portaudio References: <453039A5 DOT 5050103 AT byu DOT net> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Hugh wrote: > Eric Blake byu.net> writes: > >> Welcome to dynamic libraries. If you compile against a dll, then the dll >> must be present to run the binary. You can see if you can try and force a >> static compile, but the result will be that your binary is bigger, and >> that you no longer automatically pick up any library updates. > > > Hi Eric, > > Thankyou for your reply. I compiled a static version of Portaudio and installed > it, but compiling my sources against Portaudio caused some errors to peak from > the Portaudio static sources. > > I am most likely going to use the shared libraries, because then I can easily > update the libraries as needed. Is that your recommendation? Recommendation? What you do is at your discretion, based on what your needs are. As you've found and as Eric has already pointed out, there are trade-offs either way. So what Eric has offered is advice. But if you need a recommendation then, sure dynamic libraries is a good way to go. -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 216 Dalton Rd. (508) 893-9889 - FAX Holliston, MA 01746 -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/