Speed up standalone builder process
Moderators: FourthWorld, heatherlaine, Klaus, kevinmiller, robinmiller
Speed up standalone builder process
When I create my standalone, it hangs at "Removing development properties and setting profile options...". Sometimes it takes 1 minute, other times 20+ minutes. What would cause this and can I do anything to speed it up?
Re: Speed up standalone builder process
Hi Paul,
Have you turned off "search for inclusions"? This feature can take a lot of time.
Is your standalone very big? Do you have an old, slow computer? Which version do you use? Can you provide any other relevant information?
Best,
Mark
Have you turned off "search for inclusions"? This feature can take a lot of time.
Is your standalone very big? Do you have an old, slow computer? Which version do you use? Can you provide any other relevant information?
Best,
Mark
The biggest LiveCode group on Facebook: https://www.facebook.com/groups/livecode.developers
The book "Programming LiveCode for the Real Beginner"! Get it here! http://tinyurl.com/book-livecode
The book "Programming LiveCode for the Real Beginner"! Get it here! http://tinyurl.com/book-livecode
Re: Speed up standalone builder process
The standalone is about 5mb. Its a newer computer with Revolution 4.0.0. I have selected the inclusions and do not search for them. Sorry, never seen this problem or any other posts about it so I'm not sure what is relevant to see what the problem is.
Re: Speed up standalone builder process
Hi Paul,
This issue has come up a few times before.
The delay is caused by the standalone builder removing "development properties" from your objects. These are custom properties set by the IDE to allow it to remember various things about your stack. They are not needed in the standalone application and cause unwanted extra filesize (though this could be minimal).
The repeat loop that removes these properties loops through every control in your stack. So typically if you have a very large number of controls (this includes cards) there will be delays here. Unfortunately with the current architecture its not possible to significantly optimize this. We hope to do this in the future, possibly by adding a "repeat for each control" loop, which is optimized for this situation.
What I would suggest for now is to use a quick hack to speed things up while you are testing, then just put up with the delay once when you build your final shipping versions. The hack to tell the standalone builder not to remove development properties is to set the cREVKeepDevelopmentProperties of your main stack to true.
For more information about this issue there is an open bug report here:
http://quality.runrev.com/qacenter/show_bug.cgi?id=2217
Regards
Oliver
This issue has come up a few times before.
The delay is caused by the standalone builder removing "development properties" from your objects. These are custom properties set by the IDE to allow it to remember various things about your stack. They are not needed in the standalone application and cause unwanted extra filesize (though this could be minimal).
The repeat loop that removes these properties loops through every control in your stack. So typically if you have a very large number of controls (this includes cards) there will be delays here. Unfortunately with the current architecture its not possible to significantly optimize this. We hope to do this in the future, possibly by adding a "repeat for each control" loop, which is optimized for this situation.
What I would suggest for now is to use a quick hack to speed things up while you are testing, then just put up with the delay once when you build your final shipping versions. The hack to tell the standalone builder not to remove development properties is to set the cREVKeepDevelopmentProperties of your main stack to true.
For more information about this issue there is an open bug report here:
http://quality.runrev.com/qacenter/show_bug.cgi?id=2217
Regards
Oliver
Oliver Kenyon
Software Developer
Runtime Revolution
Software Developer
Runtime Revolution
Re: Speed up standalone builder process
Frankly, I personally would prefer you'd optimise the IDE to not put cprops everywhere 

Various teststacks and stuff:
http://bjoernke.com
Chat with other RunRev developers:
chat.freenode.net:6666 #livecode
http://bjoernke.com
Chat with other RunRev developers:
chat.freenode.net:6666 #livecode
Re: Speed up standalone builder process
Ok, thanks Oliver.