|
From: Joseph J. S. <jo...@st...> - 2005-01-23 19:53:18
|
At 3:03 PM -0800 1/20/05, James W. Walker wrote: >>Any opinions on whether we're in that state now, and if not, what >>is it that's gotten worse? > >As you would know if you looked at the CVS mailing list, Roger >Holmes is in the midst of a wholesale change in Quesa's >infrastructure, taking advantage of our recent move to C++. We >should wait until that work is complete and has been tested before >making a release. In retrospect, we should have done a release before starting such major changes, but that's moot now. (I should have done a better job of keeping on top of this list, too -- I'll try to do so in the future.) I may need to ship my product with my own custom builds of Quesa, then. Any suggestions on how I should identify it? It's after 1.6d19, but prior to what will presumably be 1.6d20... Should I call it 1.6d19b, perhaps? For that matter, if I find that 1.6d19 will work, are there official builds of that available? <http://sourceforge.net/project/showfiles.php?group_id=45158> seems to have built SDKs for 1.6d18, but for 1.6d19, it has only source code tarballs. Theoretically I can build one that comes out exactly the same as anybody else's build, but in reality, that's not always the case. So, is there an official build somewhere I'm missing, or should I just build my own and bill it as 1.6d19? Thanks, - Joe -- ,------------------------------------------------------------------. | Joseph J. Strout Check out the Mac Web Directory: | | jo...@st... http://www.macwebdir.com/ | `------------------------------------------------------------------' |