[GRASS-user] Problems with CVS compile part 2!
Glynn Clements
glynn at gclements.plus.com
Tue Aug 1 20:10:10 EDT 2006
Darrel Maddy wrote:
> Very many thanks, I now have a working copy :)
>
> **************************************************************************
> I can think of several possible solutions to this:
>
> 1. Use "./configure ... --without-ffmpeg ..."
>
> This did not make any difference. The compile gave the same errors.
If you re-run configure, you need to run "make clean" before
re-compiling.
> 2. Remove $(FFMPEGLIB) from lib/ogsf/Makefile and add it to
> visualization/nviz/src/Makefile instead.
>
> This appear to have worked a treat! Just aswell as I would have had to
> do some reading in order to perform the following:
>
> 3. Build libavcodec as a shared library.
> 4. Build libavcodec as a static library but compiled with the -fPIC
> switch.
>
> ****************************************************************************
>
> This is a very helpful list. Will I have to 'make' this change everytime
> I update the CVS?
If you don't need the ffmpeg option (which provides the ability to
record fly-throughs directly to AVI files, rather than writing out
individual frames then having to use a separate encoder), the easiest
option is to just not use the --with-ffmpeg option (it's disabled by
default).
If you need the ffmpeg option and don't want to recompile it, you may
occasionally need to re-fix the Makefiles. When you update a file from
CVS, any changes to the repository version are applied to the local
copy as a patch, so any changes to your local copy will normally be
preserved. However, if the changes affect the modified portion of the
files, you will get a conflict, and will have to fix the Makefiles
manually.
--
Glynn Clements <glynn at gclements.plus.com>
More information about the grass-user
mailing list