From: David B. <dav...@gm...> - 2010-06-22 21:15:29
|
Hi Brendan, > One question I'd like to bring up in the meantime is how to handle the > (rather unlikely?) situation where a user wants to build with a > "canned" version of t4k_common but doesn't have RSVG/SDLPango > available. This will (and should) presently fail with unresolved > linkage. libt4k_common can support usage of SDL_ttf or PNG, but I'm > not sure how easy/possible it is to compile the shared library with > those flexible dependencies. In essence, we'd be shifting the > conditional compilation of the backend in functions like LoadImage > (which prefers, but doesn't need, RSVG) from t4k_common compile time > to tuxtype compile-time. Worth it? Probably not, but part of me thinks > it would be fun to try. So, if I understand correctly, the question is whether it is possible to compile t4k_common without knowing whether e.g. SDL_Pango is available at the time of subsequent linkage with tuxtype? This would I guess be a sort of conditional linkage, in which the link failures would result in an attempt to link with the fallback library, rather than just failing. I have no idea if this is possible - if it is, I don't know how to do it. David |