Sorry, the linking command that errors is this one: c++ -headerpad_max_install_names -o debug/open1394.app/Contents/MacOS/open1394 open1394.o mainwindow.o monitor.o select.o myconv.o mytrans.o captureset.o featureset.o multigrab.o reticles.o reticlesdialog.o options.o recordmovie.o moc_mainwindow.o moc_monitor.o moc_select.o moc_captureset.o moc_featureset.o moc_multigrab.o moc_reticlesdialog.o moc_options.o moc_recordmovie.o qrc_open1394.o -F/usr/local/Trolltech/Qt-4.3.2/lib -L/usr/local/Trolltech/Qt-4.3.2/lib -ldc1394 -lavcodec -framework QtOpenGL -L/usr/local/Trolltech/Qt-4.3.2/lib -F/usr/local/Trolltech/Qt-4.3.2/lib -framework QtGui -framework Carbon -framework AppKit -framework QtCore -lz -lm -framework ApplicationServices -framework OpenGL -framework AGL
I manually tried running the command again whilst playing with the position of -lavcodec, no results though. I also tried explicitly adding -L/usr/local/lib but this also didn't help, and shouldn't even be necessary. ---------------------------------------- > Date: Mon, 14 Apr 2008 12:28:11 +0200 > From: [EMAIL PROTECTED] > To: [email protected] > Subject: Re: [libav-user] -lavcodec on os X > > Hi Jasper, > > Jasper Leemans wrote: >> hi everyone, >> >> I wrote a Qt/ffmpeg program which compiles fine with the -lavcodec flag on >> my Linux box. >> >> then I installed ffmpeg on my os X machine with general ./configure make >> sudo make install >> (no need for the audio codecs I only use video) > [...] >> "avcodec_open(AVCodecContext*, AVCodec*)", referenced from: >> RecordDialog::setupRecording(int, int, bool, float)in recordmovie.o >> ld: symbol(s) not found >> collect2: ld returned 1 exit status >> make: *** [debug/open1394.app/Contents/MacOS/open1394] Error 1 >> >> These are the same typical you get when you forget the -lavcodec flag > > On some systems, I've seen similar errors when the "-lavcodec" option > is placed in the wrong position in the compilation command. > Since you did not post the command you used for compiling/linking your > program, it's hard to tell where the problem is. > > Anyway: > 1) Do the "ffmpeg", "ffplay", and "ffserver" executable compile and link > correctly in your OS X installation? If yes, you can look at the command > lines used by the ffmpeg build system to compile and link them... > 2) In general, you can use the "pkg-config" command to know the correct > options (in the correct order). > > > Luca > _______________________________________________ > libav-user mailing list > [email protected] > https://lists.mplayerhq.hu/mailman/listinfo/libav-user _________________________________________________________________ Discover the new Windows Vista http://search.msn.com/results.aspx?q=windows+vista&mkt=en-US&form=QBRE _______________________________________________ libav-user mailing list [email protected] https://lists.mplayerhq.hu/mailman/listinfo/libav-user
