On Sun, Mar 22, 2009 at 7:02 PM, bkshepard <brian.shep...
> Hey Tim,
> Thanks so much for jumping on that! That seems to have done the
> trick! A couple of questions for you, though.
> 1. I know from the release notes that builds done on an Intel machine
> don't work on a PPC (I've already experienced that), so is it best to
> just build everything on a PPC, or should I build on both--one
> targeted for PPC machines and one for Intel machines?
Part of the problem with this is that I have inadequate resources to
fully research the problem with PPC machines. Apple has not produced
a consumer PPC machine in over 3 years, so given my long list of
priorities this one does not find itself within the top 100. If it
works for you, then yes by all means build on a PPC. I have also seen
other reports about this problem regarding other third-party externals
as well, so I don't *think* the problem is limited to just Tap.Tools,
but like I said I have not been able to research it thoroughly.
> 2. I've asked this on the MaxMSP forum, but gotten no answer, but I
> get the following error messages in the Max window of my builds:
> pattr_obex: no such file in collective
> mfont: no such file in collective
> requirements.txt: no such file in collective
> As you mentioned here before, the requirements.txt seems to not have
> any effect and is more cosmetic. How about the other two (pattr_obex
> and mfont)? Are they related to Tap.Tools? If so, is it anything I
> need to be concerned about?
Correct about the requirements.txt problem. I would say that
pattr_obex is clearly something to do with pattr, and thus no anything
to do with Tap.Tools. A spotlight of my hard disk shows that mfont is
something to do with js or jsui, and there is nothing related to
'mfont' in any Tap.Tools files.
> Thanks, again, for fixing this!
No problem -- thanks for the detailed reports!
Cycling '74 | http://cycling74.com
Electrotap | http://electrotap.com