Problem building Standalone with 3.0.1 Pro

[bkshepard]

I am building a standalone that includes several iterations of the
tap.pan~ object. When I build my app in MaxMSP (5.0.6), I then run
the Tap.Tools Builder from the Max Extras menu and it reports "Done!"
almost immediately. Everything works fine until I try to run the app
on a different machine which reports multiple "no such object" and "no
such file in collective" messages in the Max window about the tap.pan~
object. I also get the following long error message in the Max
window:

Referenced from: /Users/jenny/Desktop/EchoDamp.app/Contents/support/
extensions/tap.tools.mxo/Contents/MacOS/tap.tools
2009-03-20 17:00:11.677 EchoDamp[756:20b] Error loading /Users/jenny/
Desktop/EchoDamp.app/Contents/support/extensions/tap.tools.mxo/
Contents/MacOS/tap.tools: dlopen(/Users/jenny/Desktop/EchoDamp.app/
Contents/support/extensions/tap.tools.mxo/Contents/MacO
S/tap.tools, 262): Library not loaded: @executable_path/../Frameworks/
JamomaDSP.framework/Versions/A/JamomaDSP

I've checked, and the tap.tools.mxo is in the extensions directory of
my built application, it just doesn't seem to be either authorized, or
working properly.

BTW, on the computer that has tap.tools installed, I get 8 copies of
"requirements.txt: no such file in collective." One error for each
iteration of the tap.pan~ object.

[Timothy Place]

Hi,

Thanks for the report. This is definitely a bug in the 3.0.1 release
candidate and I will fix it ASAP.
best,
Tim

--
Cycling '74 | http://cycling74.com
Electrotap | http://electrotap.com

[bkshepard]

Thanks Tim. As an additional piece of information, I tried doing the
build on both a PPC and an Intel computer with the same results. I
saw in the release notes that there is an issue with building on an
Intel and running on a PPC, but that seems to be a separate issue from
this. Thanks, again!

[Timothy Place]

Hi,

Attached is a fix for the Tap.Tools Builder in the 3.0.1 release
candidate for the Mac (just replace your existing copy). Proper
installers are forthcoming.

best,
Tim
____________________________________
Timothy Place
Cycling '74 | Electrotap | 74Objects

[bkshepard]

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?

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?

Thanks, again, for fixing this!

>  TapToolsBuilder.maxpat.zip
> 5KViewDownload

[Timothy Place]

On Sun, Mar 22, 2009 at 7:02 PM, bkshepard <brian....@usc.edu> wrote:
>
> 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!
Tim