I was able to fix this problem with the following script:
#!/bin/sh
APP="MyApp"
SOURCE_BUILD_DIR="build/Release"
TARGET_BUILD_DIR="build/Deploy"
LOCAL="$SOURCE_BUILD_DIR/$APP.app/"
REMOTE="$TARGET_BUILD_DIR/$APP.app/"
rsync --progress $* -avzut $LOCAL $REMOTE --exclude .DS_Store --copy-links
P
MD5 hashes match. I am building my app on an encrypted disk image if that
would matter at all. I wouldn't think it would affect it.
My tester is on a 64bit machine. I'll try building it on 0.9 and see if
that helps.
Any idea why the directory size would be so dramatically different?
Kevin
On
Hi Kevin,
It sounds like a data corruption problem, but it could also maybe due to
running the application on an Intel 32-bit machine (because, as of 0.10, i386
support is not built in anymore by default).
I would run md5 hashes on both the embedded dylib and the one in
/Library/Frameworks to
I'm running the following command to prepare my app to share with testers.
PATH="$PATH:/usr/local/bin" macruby_deploy --embed --compile
"$TARGET_BUILD_DIR/$PROJECT_NAME.app"
On my machine, its says the app directory is ~25MB but testers get the
following error when they try to run it:
dyld: Libr
