18 Reasons Why Compiling with RunRev May Fail

What to do when building standalones goes mysteriously wrong?

This post is an update to an earlier post about why one may not be able to build a RunRev standalone. Below follow 18 possible fixes for reasons why compiling a standalone fails. These reasons are not related to each other. You should try them one by one, preferably not in combinations. If all of these possible fixes fail, try to combine those that are most likely to solve the problem.

If you have no clue where to start or if you have tried everything and still can’t create a standalone, feel free to contact me at support@economy-x-talk.com and ask for help. We will handle your request as a support incident and will charge for it as such.

• try removing passwords from stacks

• try toggling the destroyStack property

• check whether pictures are referenced or imported as controls

• make sure that pictures are in the correct location relative to your stack

• make sure to use relative file paths for portability

• select “Select inclusions” instead of “Search for required inclusions” on the General pane of the standalone application settings

• after selecting “Select inclusions”, make sure that you actually include all components that you need for your stack, this may involve knowing for sure what each component does

• you might try to forget about profiles, just select “Remove all”

• if you build for multipe platforms, try building for one platform at a time

• quit and restart Revolution without saving your project right after building a standalone

• quit and restart Revolution after saving your project and before building a standalone

• when moving your standalone for Mac OS 9 or Mac OS X to a different computer, make sure to create a sit or zip file of your standalone first

• when uploading your compressed standalone or exe file to a server, make sure that your FTP software treats it as binary

• you might try to build a standalone while suppressing messages (see Development menu)

• you might try to build a standalone while suppressing errors (see Development menu)

• if building standalones takes ages, set the cREVKeepDevelopmentProperties of your mainstack to true

• Change the preference “If destroyStack is false, when closing last stack in file:” to something other than “Ask”. This can be found by doing Edit -> Preferences -> Files & Memory.”

• Try setting the cantModify of your stack to false, if you happen to have set this property to true.

If you encounter any unparsed errors while building standalones, you can parse them at http://runrev.info/error.html

2 thoughts on “18 Reasons Why Compiling with RunRev May Fail

Leave a Reply

Your email address will not be published. Required fields are marked *