JorWong schrieb:
I'm using Bloodshed Dev-C++, the latest version of Cygwin, and the PortAudio
API. I put the PortAudio .tar in my /usr/src folder and ran the following
commands:
$ cd /usr/src
$ tar zxf pa_snapshot_v19.tar.gz
$ cd portaudio
$ autoconf
$ ./configure --disable-static
$ make
$ make
ygwin says installation was successful, but when I take the files from
/usr/local and put them in the appropriate folders in the Dev-C++ directory,
I still get multiple linker errors when trying to compile a PortAudio
program.
--
View this message in context:
http://www.nabble.com/Cygwin-and-Port
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 p
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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Hugh on 10/13/2006 5:14 PM:
> I can compile Portaudio in Cygwin, using shared and static libraries only.
> That
> is fine with me though. I can build my sources using Cygwin, except whenever
> I
> run the programme, I always require cy
I can compile Portaudio in Cygwin, using shared and static libraries only. That
is fine with me though. I can build my sources using Cygwin, except whenever I
run the programme, I always require cygportaudio-2.dll. Is there any possible
way to have the library information hard coded into the com
6 matches
Mail list logo
