From: Alien <ali...@us...> - 2005-06-19 20:21:04
|
Op zondag 19 juni 2005 21:45, schreef Daniel Caujolle-Bert: > Hi, > > Le Samedi 18 Juin 2005 19:39, Alien a =C3=A9crit=C2=A0: > > i don't really understand; first it checks if it's dynamically loadable, > > then if the headers exist, and then it checks if a static lib file > > actually exists on certain spots with no regard to /etc/ld.so.conf ... > > > > 1. why does it require static libs? > > Because it'(s/was) not available on all distro as package (in the past). > Also, we don't know if the API is/was wrote in stone. well, there are versions, maybe it's time to move away from that static thi= ng > > 2. if a lirc_prefix is supplied this will not be checked for the include > > file 3. does it check the normal prefix? > > 4. does it check the libdir and includedir options specified at > > ./configure? 5. what about 64bit? it's stored at /usr/lib64 by default = on > > my system? 6. why is that macro 2 times defined? > > 2 times defined ? once in xine-lib, once in xine-ui > > in general, wouldn't it be better if there was a huge big AC_CHECK_XINE > > macro, that would not only check where and what libxine was configured > > with, but would also validate all the options it was configured with, (a > > check to see if they still apply), libxine could export the macro and > > xine-ui could use it for example... > > xine-lib should not care about lirc, since it don't use at all, AFAIK! well, it does check for it, i donno if any code is in there regarding lirc. furthermore, it seems that all frontends have their own lirc implementation= ,=20 which is totally not necessary. since it's mostly duplicate code, i think. |