On Mon, 14 Mar 2005, Matti Haveri wrote:
> I failed to mention that I did try to compile y4mscaler manually from
> the tarball but I'm not so familiar with this stuff. Phrases like
> "You may need/want to edit "Makefile" to change MJPEG_PREFIX or other
> relevant parameters" make me dizzy. What relevant parameters?!
The relevant parameters would probably be 1) the "-I" flag(s) placed in
CFLAGS so the compiler can find the header (.h) files needed for
compiling and 2) the -L flag(s) placed in LDFLAGS so the linker can
find the libraries.
> Thanks. I tried it but it seems that I have to edit some files to
> point to /sw where Fink has installed mjpegtools. And I didn't find
If you have "pkg-config" installed you don't need to worry about
CFLAGS (-I) and LDFLAGS (-L) because y4mscaler's Makefile will use
the pkgconfig (.pc) file.
If Fink has installed the file mjpegtools.pc (the mjpegtools pkgconfig
file) then all that's necessary is to add a directory to the
environment variable PKG_CONFIG_PATH
For example, if Fink has installed mjpegtools.pc into /sw/lib/pkgconfig
then
setenv PKG_CONFIG_PATH /sw/lib/pkgconfig
would be what you want to do. On my OS/X system I have this line in
my .cshrc file (if you use a different shell the filename and syntax
will of course be different):
setenv PKG_CONFIG_PATH
/usr/local/lib/pkgconfig:/usr/lib/pkgconfig:/usr/X11R6/lib/pkgconfig
Then y4mscaler's Makefile will get most of the information it needs
from the lines:
MJPEG_CXXFLAGS := $(shell pkg-config --cflags mjpegtools)
MJPEG_LDFLAGS := $(shell pkg-config --libs mjpegtools)
All that you need to do is change line 47 to suit local preferences,
change
MJPEG_PREFIX = /usr/local
to be /sw/bin or whatever you want - you could put y4mscaler into
/usr/local/bin by leaving that line as it is.
The only really mandatory change is the CPU_OPT settings - look at
lines 26 thru 37. Comment out the entry for "686-class machine)
and then uncomment either the G4 PPC or G5 PPC line.
> the neccessary files there. Maybe I should forget Fink, bite the
> bullet, and install also mjpegtools manually. I'll do it some day.
That's worked out well for myself. True, getting the infrastructure
in place (recent versions of autoconf, automake, etc) is necessary
but once that's done the rest of the stuff I was interested in
built without hassles.
Cheers,
Steven Schultz
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Mjpeg-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mjpeg-users
