<div class="gmail_quote"><div>David,<br> <br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div>
> As it is, stuff is so messy right now that I'm not convinced it's even<br>
> salvageable.<br>
<br>
</div>I wouldn't go that far - I think libt4k-common is fine. </blockquote><div><br>That's true, at least :) What I meant was that the substantial work done in TT and TM will be hard to bring back into their respective trunks, by hand or with merges. <br>
</div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Last time I<br>
worked on it (maybe two months ago), I had gotten it to build with<br>
autotools as a shared libtool library, and it seemed to install<br>
properly and make a valid tarball with "make dist". I didn't get<br>
tuxmath to successfully link with it, however, even though the library<br>
appeared to be installed. However, I pretty much just left it at that<br>
point without any detailed troubleshooting and moved on to other<br>
stuff.<br>
</blockquote><div><br>That's good to hear. I'll see if I can get TM linking properly to a shared lib. I'm inclined to stick to CMake and leave the autotooling to the experts, though. Is a libtool library special, or did you just mean you built with libtool?<br>
</div><div> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div>
</div>Yes - the distros really seem to dislike static libs, although what<br>
they really are trying to avoid is having multiple packages each have<br>
their own copy of e.g. libSDL statically linked into the binary.<br></blockquote><div><br>Fair enough, that's valid. <br></div><div> <br>
</div></div>-Brendan<br>