How to build VVOpenSource so that frameworks are packaged in the target mac application?

[GoogleCodeExporter]

I have successfully written a Mac application that integrates VVOSC, VVMIDI and 
VVBasic. Now I'm trying to package my app in a DMG in order to make the 
installation of my app as simple as possible. Unfortunately, with the way the 
frameworks are built, in the build/Release directory of my project, I get 
MyApplication.app package and all 3 frameworks beside my app package. But to 
make it simpler to set up my app by just drag and dropping it to /Applications, 
I guess I would need to have all 3 frameworks inside my app package. On 
StackOverflow 
(http://stackoverflow.com/questions/3612787/packaging-a-mac-application-for-manu
al-install-even-though-it-has-frameworks), someone suggested that I change the 
Installation directory build setting for the frameworks, but I'm afraid to 
break something as I don't really know what I'm doing.

Can you help me with that? How can I configure VVOpensource's build so that 
they are inside my application's package?

Original issue reported on code.google.com by sebastie...@gmail.com on 7 Sep 2010 at 6:44

[GoogleCodeExporter]

the installation directories are already configured correctly for all the 
frameworks compiled by vvopensource, you can safely ignore what you read on 
stack overflow (it's correct, just not necessary in this case).

you probably just aren't copying the compiled frameworks into your application 
bundle- this is a change you need to make to your project, not to vvopensource. 
 you need to make a new "copy files" build phase, set it to copy to the 
'Frameworks' folder, and drag the frameworks into it (i think these 
instructions are posted on vvopensource's project homepage).  when you build 
your app, the frameworks should get copied into 
YourAppName.app/Contents/Frameworks/.  you may want to examine the sample apps 
included with the project so you can compare them to your app.

Original comment by raycut...@gmail.com on 7 Sep 2010 at 7:45

[GoogleCodeExporter]

"but I'm afraid to break something as I don't really know what I'm doing."

this is something you should never have to worry about- developers use SCM 
(source code management) software like SVN (or CVS, or git) specifically so 
they don't have to worry about changes breaking stuff.  now would be an 
excellent opportunity to learn a bit more about SCM software (i'd suggest 
starting with SVN as i find it to be more straightforward than the 
alternatives), and perhaps set up your own repository for your own projects:

http://svnbook.red-bean.com/en/1.5/index.html

...it takes a lot less time to experiment than it does to ask questions and  
wait for answers- and experimentation is a lot easier to undertake if you know 
that there can't be any negative repercussions : )

Original comment by raycut...@gmail.com on 7 Sep 2010 at 8:08

[GoogleCodeExporter]

I know about SVN thanks. My project is under SVN already. Anyway, what your 
documentation says is the following:

"Expand your application's target, and drag all of the frameworks you just 
added to your project into the copy files build phase you created in the last 
step. Be sure to drag the frameworks from your project into the copy files 
build phase- you're not dragging from the Finder to XCode, you should be 
dragging from XCode to XCode! "

Nothing about the fact that I need to change the destination of the "copy 
files" phase. Maybe you could add this part. Indeed now that I changed the 
destination, it's copying frameworks at the right place. Thanks for your help.

Original comment by sebastie...@gmail.com on 7 Sep 2010 at 8:27

[GoogleCodeExporter]

sure, no problem

Original comment by raycut...@gmail.com on 8 Sep 2010 at 12:11

• Changed state: Verified