i just fixed the deployment script to include the shaders in the minimal version but besides that there seems nothing wrong with it. doing a release-deployment build correctly creates these images for me:
vdrift-full.dmg 309,6 MB
vdrift-minimal.dmg 32,8MB
Yes, I used the release stuff to make the packages. If you've got it sorted now, I'll finish up testing tracks with what I've got then try the new svn and build packages with that, and see how it works. Thanks for taking care of it. I have no issues with making the packages and putting them somewhere they can be downloaded if it aids in testing on another platform.
as i said i fixed nothing besides the shaders not being in the minimal disk image, because i could not reproduce other problems.
i can recommend doing a "clean" and manually look for left over files in the build folder before build.
if you get a image that is not about 310MB (full) or 33MB (minimal) there must be something wrong again.
could you go to "Edit Project Settings" and set "Place build products In:" to "Custom location" and choose a new and empty directory there?
if that still doesn't help you can have a look at the (second) "Run Script" "Build Phase" which contains the crude shell script that does the disk image stuff.
ok in the full dmg the data folder is named vdrift-data instead of data. because of this vdrift won't start and also because of this the .svn folders aren't deleted which results in the size difference.
however why the folder is misnamed i have no clue. it is created by this command:
#copy data for full version and remove unnecessary stuff
/Developer/Tools/CpMac -r $SRCROOT/../../data vdrift/
which i don't think can result in a misnamed folder. did you modify the deployment script somehow?
Nope, didn't change a thing. I can tell you that my source is in a directory called "code" or "projects" depending on which computer I'm on, which contains two directories - "vdrift" where the source is, and vdrift-data, where the data is.
>the change to two repositories made that bug possible
in addition i think you symlinked the vdrift-data folder to the data folder in vdrift? that way the copy picked up the name of the real folder (vdrift-data) instead of the name of the symlink (data).