Re: [Openquicktime-devel] Moving files in CVS

[<mi...@cl...>]

> I am just about to do my big file moving around and all the Makefile
> editing that is going to result.
>
> There doesn't seem to be a 'nice' way of moving files in CVS (only
> deleting and adding again) - which would result in the change log
> being lost. Nearly all the files will be moved...
>
> So I think the best thing to do would be for me to make it all work
> nicely on my systems (Darwin and Linux) and then upload to a fresh
> new module in CVS...

Maybee we could discuss a little about the changes on the source tree
before putting it on the CVS.
Do you think we should:
 - put the player oqtplayer in the same module as the library (unlike
the other utilities, oqtplayer needs the SDL library, which is really
huge) ?
 - put the encoder as well (btw, is it working ? does it need extra
libraries ? )
 - put the DirectShow stub in it ?
 - keep the plug-ins in the same module, or put them in separate modules ?

Three remarks about the new Makefile.am (maybee useful if you wish to
change the source tree) :

* Now, the configure script sets two variables AUDIO_PLUGINS and
VIDEO_PLUGINS that are used in audioplugin/Makefile.am and
videoplugin/Makefile.am to know which plug-ins to create (the variables
contain a subdirectory names, such as MP3, PHOTO_JPEG, or XANIM) you need
to change this in the configure script if you add some plugins or change
the directory they are staying in.

* audioplugin/MP3 contain sources in subdirectories (corresponding to the
mpg123 and lame distributions); automake does not allow building from
sources not in the Makefile.am file, so I use "convinience library"; ie:
each subdirectory has its owm Makefile.am and creates a simple .a library
(or .la because of libtool) that is used by the parent Makefile.am...
heavy but it's the cannonical way, I guess.

* Makefile.am that build plug-ins should put the -module and
-avoid-version flags in LDFLAGS (this is passed to libtool, not ld
actually), and the correct -I CFLAGS so that we can include the library
headers...

Oh, and try avoid using assert from assert.h, I had strange errors while
linking with gcc and libtool on Solaris 5.8 (thus, I put my own assert
macro in audioplugin/MP3/audioencoder/lame3.70/ )

I hope the rest is straightforward.

-
Antoine