On Mar 30, 2008, at 6:02 AM, Mark Heath wrote: >> >> >> These look to me like it cannot find the symbols for the listed >> functions within the libraries that I built and installed. > > > I had similar problems linking these libraries within Xcode. > > I believe the issue is that using the configure script builds > libraries that are only for a single CPU architecture (IE all mine are > built powerPC only) > Xcode wants to build a cross compiled binary for both Intel and > PowerPC. > > I worked around the problem by building the application from the > command line... > > eg gcc -L/sw/lib -lmjpegutils -I/sw/include/mjpegtools -framework > OpenGL -framework QuartzCore -framework Cocoa -framework > CoreFoundation main.m yuvVideoView.m -o yuvVideo > > (OK this project wasn't using libav but the mjpegutils) > > I know that this is not really a suitable solution. > > So If anyone else knows how to build cross compiled libraries or force > Xcode to produce executables for only one architecture, I'm sure it > would solve the issue.
I tried this: g++ -L/usr/local/lib -L/opt/local/lib -I/usr/local/include -I/opt/ local/include -I/usr/local/include/SDL -framework OpenGL -framework Cocoa -framework SDL_mixer -I/Users/orcein/Documents/Programming/Vided -lavformat -lavcodec -lavutil -lz -lguichan -lguichan_sdl -lSDL - lSDL_image -lguichan_opengl VE_Controller.cpp ve_video.cpp VE_Media.cpp VE_Sound.cpp VE_FrameServe.cpp main.cpp -o vEd and ended up getting pretty much the same error results that XCode was sending me. >.< Somehow I get the feeling that if I could recompile ffmpeg (currently I'm having problems with it trying to use MMX routines when I've expressly disabled them) and install it fresh that these issues would just... go away... Can you built ffmpeg on your Mac currently? -- Scott _______________________________________________ libav-user mailing list [email protected] https://lists.mplayerhq.hu/mailman/listinfo/libav-user
