Bundling externals in MacOS X standalones.

Andre Garzia soapdog at mac.com
Fri Oct 13 15:12:25 EDT 2006

Hi Mark,

this didn't work for me out of the box. To make this work, I had to  
trap the "Startup" message and set the defaultfolder to the path of  
the inner stack or it would not find the externals folder next to the  
main stack.


On Oct 13, 2006, at 3:12 PM, Mark Schonewille wrote:

> Hi Andre,
> First set the externals property of the mainstack to "externals/ 
> externalname.bundle" or "externals/externalname.dll". Then put the  
> externals into the externals folder, which is next to the standalone.
> You can include externals in the list of files to copy, in the  
> standalone builder. Create a folder next to your main stack, call  
> it "Externals" and put your externals into this folder. In the  
> standalone builder, you can now add the files. When they are  
> copied, the path relative to the stack will be the same (i.e. in th  
> externals folder).
> Best,
> Mark
> --
> Economy-x-Talk
> Consultancy and Software Engineering
> http://economy-x-talk.com
> http://www.salery.biz
> Get your store on-line within minutes with Salery Web Store  
> software. Download at http://www.salery.biz
> Op 13-okt-2006, om 20:07 heeft Andre Garzia het volgende geschreven:
>> Folks,
>> where should I put a external so it will be bundled in 2.7.4 MacOS  
>> X standalone app. I tried opening the package and putting it in  
>> the Externals folder next to the application inner executable with  
>> no success, I also tried putting it directly next to the inner  
>> executable with no success either.
>> How should I bundle it?
>> The externals prop of the stack has no path info.
>> Andre
> _______________________________________________
> use-revolution mailing list
> use-revolution at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your  
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-revolution

More information about the Use-livecode mailing list