From: John Wells <iindigo@gm...> - 2007-05-16 19:35:51
First of all, please forgive me if this is the incorrect mailing list
for this type of question.
Now since that's out of the way, my question: How does one go about
compiling the xine-lib framework from source? Is it only on CVS? Or,
for that matter, is it even still maintained?
I would not have asked, but it's only mentioned in whispers around
the internet along with Cocoaxine, and there doesn't seem to be any
documentation on the subject.
Thank you for your time,
From: Matt Messier <mmessier@gr...> - 2007-05-16 21:25:04
On May 16, 2007, at 3:35 PM, John Wells wrote:
> First of all, please forgive me if this is the incorrect mailing list
> for this type of question.
> Now since that's out of the way, my question: How does one go about
> compiling the xine-lib framework from source? Is it only on CVS? Or,
> for that matter, is it even still maintained?
> I would not have asked, but it's only mentioned in whispers around
> the internet along with Cocoaxine, and there doesn't seem to be any
> documentation on the subject.
I have been working pretty much full-time on Mac OS X support. The
current mainline xine-lib-1.2 hg repository mostly builds, but not
quite without one minor patch. I've been working on a new build
system that does build correctly without any patches on Tiger, and
includes support for building universal binaries. I hope that this
new build system will be merged into the primary repository soon.
I also plan on adding support for building xine-lib as a framework
soon, but I haven't started on that work just yet. The builds that I
have presently work just fine on ppc and i386 for Tiger. It does not
build on Leopard yet, but I can say no more about that. I have no
plan to support anything older than Tiger. My runtime testing has
been pretty limited so far, so I don't know if dvd support or some of
the other more esoteric features work. I can say that vcd support is
not included yet, though I do plan to do the necessary work to port
that, as well as Real binary codec support.
In my new build environment, builds work with Xwindows (XShm, Xv, and
OpenGL), CoreAudio, and Cocoa NSOpenGLView derived support. I will
be adding CoreVideo support soon before I do framework support,
because the way that the Cocoa video output plugin works now will not
fit into a framework environment. My ultimate goal, if it's not
already clear, is to do a proper full port of xine-lib to Mac OS X.
Don't expect an Xcode project, though. I don't think anybody wants
to try to maintain to different build environments for the same code
(I certainly don't). It's all built properly within the autoconf/
automake/libtool framework. I'll be putting together a README for
Mac OS X that details the status of the port soon.