I compiled a patch as a standalone with Max 4.6.2 and Jitter 1.6.2

When I launched it on other computers (mac iBook and power Book)

The standalone asked to install the CFM support, but couldn't do it

("unable to read a file", that i guess it couldn't find)

What is the proper way to distribute the standalone?

Should I include some libraries in the app support folder?

...like these files in the Libraries/CFMsupport/

Is there any documentation about these file somewhere?

Or is there an external installer for CFM lib?

Will there be a better documentation for standalone/collective 

(but... yea.. i know its a pain to do that...:) )

I compiled  a patch as a standalone with Max 4.6.2 and Jitter 1.6.2
When I launched it on other computers (mac iBook and power Book)
The standalone asked to install the CFM support, but couldn't do it
("unable to read a file", that i guess it couldn't find)

What is the proper way to distribute the standalone?
Should I include some libraries in the app support folder?
...like these files in the Libraries/CFMsupport/
/edb1drv
/jitlib
/JSRef.shlb
/JSRefThreadsafe.shlb
/MaxAudioCFMAdaptor.shlb
/MaxCFMAdaptor.shlb
/VstPlugLib.shlb

Is there any documentation about these file somewhere?
Or is there an external installer for CFM lib?

Bonus question for C74 team:
Will there be a better documentation for standalone/collective 
compilation someday?
(but... yea.. i know its a pain to do that...:) )

cfm-support-in-standalones

I have made a standalone on a G4 running OX.4.8, Max/MSP 4.6.2 and Jitter 1.6.2. It works perfectly well everywhere it can. But when running on a PPC using panther it ask for installing support for objects of older version of Max? It ask it every time I run the standalone (even if I choose Don't ask again).

As there is no object from older version in my standalone, is there a way to skip this proposal ?

It's almost the same problem.
I have made a standalone on a G4 running OX.4.8, Max/MSP 4.6.2 and Jitter 1.6.2. It works perfectly well everywhere it can. But when running on a PPC using panther it ask for installing support for objects of older version of Max? It ask it every time I run the standalone (even if I choose Don't ask again).
As there is no object from older version in my standalone, is there a way to skip this proposal ?
Many thanks
Patrick


> I have made a standalone on a G4 running OX.4.8, Max/MSP 4.6.2 and 

> Jitter 1.6.2. It works perfectly well everywhere it can. But when 

> running on a PPC using panther it ask for installing support for 

> objects of older version of Max? It ask it every time I run the 

> standalone (even if I choose Don't ask again).

> As there is no object from older version in my standalone

Are you really-really sure that no older objects are on your disk(s)?

v4.6.2 looks also for content of folders targeted by an alias put in 

any folder defined in the File Preferences of MaxMSP.

And sometimes, it doesn't look for content of sub-folders. (which is 

As I'm planning a Universal version of a MaxMSP standalone, I'd like 

If it's a very problem specific to the previous version of Mac OS, 

In a such case, I'd delete the "Max 4.6 Preferences Folder" and 

rebuild my File Preferences, and create more search fields inside if 

> I have made a standalone on a G4 running OX.4.8, Max/MSP 4.6.2 and  
> Jitter 1.6.2. It works perfectly well everywhere it can. But when  
> running on a PPC using panther it ask for installing support for  
> objects of older version of Max? It ask it every time I run the  
> standalone (even if I choose Don't ask again).
> As there is no object from older version in my standalone

Are you really-really sure that no older objects are on your disk(s)?
v4.6.2 looks also for content of folders targeted by an alias put in  
any folder defined in the File Preferences of MaxMSP.
And sometimes, it doesn't look for content of sub-folders. (which is  
in fact a safer process.)

As I'm planning a Universal version of a MaxMSP standalone, I'd like  
to know what happens to you.
If it's a very problem specific to the previous version of Mac OS,  
this is not normal.

In a such case, I'd delete the "Max 4.6 Preferences Folder" and  
rebuild my File Preferences, and create more search fields inside if  
necessary.

A doubt: does a Universal MaxMSP standalone application is supposed to run on Panther... ?

>> But when running on a PPC using panther it ask for installing 

>> support for objects of older version of Max?

Remove the MaxMSPCFMSupportInstaller from your standalone bundle.

This is mentioned in the standalone documentation, in the Topics pdf. 

Peter Castine +--> Litter Power & Litter Bundle for Jitter

Interface Building for |home | chez nous|

Max/MSP Extremely cool |bei uns | i nostri|

>> But when running on a PPC using panther it ask for installing  
>> support for objects of older version of Max?

This is mentioned in the standalone documentation, in the Topics pdf.  
It's buried deep, but it's in there.

--------------    http://www.bek.no/~pcastine/Litter/    -------------
Peter Castine             +--> Litter Power & Litter Bundle for Jitter
                                Universal Binaries on the way
iCE:  Sequencing,  Recording &
       Interface  Building  for                   |home    | chez nous|
       Max/MSP   Extremely cool                   |bei uns |  i nostri|
       http://www.dspaudio.com/                   http://www.castine.de

UB standalones should run in 10.3.9 (assuming u have not included any 10.4 only 3rd party objects).

If you have no old-version objects in the standalone, just go into the application package of the new standalone and trash the CFM support installer package - I think its in Resources with the app icons if I am not mistaken. Then it will not ask again - my UB standalone built in 10.4.7 does not ask on 10.3.9 when this file is deleted.

Its best to avoid having to install old-version CFM support if possible, as it interferes with the newest version of Pluggo or pluggo runtime, which someone might also want to have on their machine. I think you cannot have both old-version CFM support and the newest pluggo installed and functioning at the same time.

Computer A : PPC with Tiger and 4.6.2. I have made the standalone on this computer

Computer B : PPC with Panther. I only run the standalone.

The standalone (the UB made on 4.6.2) is working perfectly on Panther.

There was one object (shell) of previous version on the computer A. It's not used in this standalone. I've just trashed it and created the same standalone. It changes nothing.

In this standalone there is no objects of previous version (it's 100% Max 4.6.2 and Jitter 1.6.2). 

when running the standalone on the PPC with Panther (computer B) it only asks for the install of cfm support for object ... (the same with Max when you start the 4.6 version for the first time). That's all.

It happens every time (even if you choose "Don't ask again").

On this computer (B) I have an older version of max (4.5 for using with Auvi objects), but I guess it doesn't matter. I ran my standalone from the desktop

Computer A : PPC with Tiger and 4.6.2. I have made the standalone on this computer
Computer B : PPC with Panther. I only run the standalone.

The standalone (the UB made on 4.6.2) is working perfectly on Panther.
There was one object (shell) of previous version on the computer A. It's not used in this standalone. I've just trashed it and created the same standalone. It changes nothing.
In this standalone there is no objects of previous version (it's 100% Max 4.6.2 and Jitter 1.6.2). 
when running the standalone on the PPC with Panther (computer B) it only asks for the install of cfm support for object ... (the same with Max when you start the 4.6 version for the first time). That's all.
It happens every time (even if you choose "Don't ask again").
It's just a bit annoying for the user.
On this computer (B) I have an older version of max (4.5 for using with Auvi objects), but I guess it doesn't matter. I ran my standalone from the desktop
P.


Without the MaxMSPCFMSupportInstaller, there is no install asking.

CFM support in standalones