<HTML><BODY style="word-wrap: break-word; -khtml-nbsp-mode: space; -khtml-line-break: after-white-space; "><BR><DIV><DIV>On Aug 11, 2006, at 1:45 PM, chris clepper wrote:</DIV><BR class="Apple-interchange-newline"><BLOCKQUOTE type="cite">On 8/11/06, <B class="gmail_sendername">Hans-Christoph Steiner</B> <<A href="mailto:hans@eds.org">hans@eds.org</A>> wrote:<DIV><SPAN class="gmail_quote"></SPAN><BLOCKQUOTE class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> <BR>I understand that. But still, managing source builds is a lot of<BR>work when multiplied by 10+, even when the software is "done". I<BR>don't want to have to build it even once. Right now, I can install<BR> many, many packages using Fink/apt-get/yum with basically one<BR>command: "fink install ..." or "apt-get install ..." or "yum<BR>install ..."</BLOCKQUOTE><DIV><BR>Someone could provide prebuilt FTGL andf freetype libs for OSX and Windows. <BR></DIV></DIV></BLOCKQUOTE><DIV><BR class="khtml-block-placeholder"></DIV><DIV>I think that checking binaries into CVS would be a really bad idea. It will cause more problems than its worth since there are many platforms, like G3, G4, G4, Intel Mac. There is already a lot of support built into the Pd-extended build system to do CPU-specific compiles. If this code is done, then automatically building it should not be hard.</DIV><BR><BLOCKQUOTE type="cite"><DIV><DIV>What are you doing for the Intel builds on the Mac?<BR></DIV></DIV></BLOCKQUOTE><DIV><BR class="khtml-block-placeholder"></DIV><DIV>Nothing, I have no access to an Intel Mac. Any volunteers?</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>.hc</DIV><BR></DIV><BR></BODY></HTML>