[Ffmpeg-devel] [PATCH] Check for __PIC__ beside PIC to enable PIC-safe code
Diego 'Flameeyes' Pettenò
flameeyes
Sat Jul 1 22:42:41 CEST 2006
On Saturday 01 July 2006 22:14, M?ns Rullg?rd wrote:
> 1. Why can't those other projects just be civilized and use the ffmpeg
> build system, inside or outside their source tree?
Because it's unfeasible in the majority of cases. And both xine-lib and xdtv
uses slightly modified versions of ffmpeg code, in the case of xine-lib I'm
trying to merge the changes so that the only things that would change would
be for cutting down the unneeded code.
Interfacing autotools with another build system is a mess, if you didn't try
it before, I can ensure you, and converting any other package to your build
system is unlikely (starting from the fact that's opinable if it's better of
autotools or not).
> in some suitable header be nicer?
The problem is the suitable header, something that is not generated and that
would be included in all those points and in any other point that might use
PIC-aware code is needed, and I'm not really sure if there is one already (on
a first glance, my report was "no", but I might be mistaken as I don't know
the architecture enough).
--
Diego "Flameeyes" Petten? - http://farragut.flameeyes.is-a-geek.org/
Gentoo/Alt lead, Gentoo/FreeBSD, Video, AMD64, Sound, PAM, KDE
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://lists.mplayerhq.hu/pipermail/ffmpeg-devel/attachments/20060701/8fda8ffa/attachment.pgp>
More information about the ffmpeg-devel
mailing list