Have An Issue With Running Your Cascades Release Build?

How-to

So you have been developing your Cascades app for a while. Everything is working great! You’re ready to just export the release build, double check that it works, and… oh, no, it’s broken.

“PANIC!!!” you might think.

Well, luckily you found this blog post. I am going to walk you through the all the steps you need to get this working, so buckle up and sit tight, because the clock is ticking.

Step one:

Add Q_DECL_EXPORT in front of your main method, so it looks like this:

Q_DECL_EXPORT int main(int argc, char **argv)

Step two:

Nope, that’s it.

We added that requirement in the Gold SDK and added it to the template then, so if your project was created afterwards it’s already taken care of.

If you are still having problems, make sure you aren’t writing to the assets directory, as it’s read-only on release builds. If you want to change something there, copy it to the data folder first.

Anyway, the Q_DECL_EXPORT change was part of Project Zygote, so if you are running into this error you might want to go all the way through the process  and get a big start time decrease for your app. Again, apps built with the Gold SDK have already had this done for them. Don’t let those newbies show you up!

Good luck! We’re almost there!

About Paul Bernhardt

I work for BlackBerry on the Developer relations team helping developers write apps in Cascades. I focus on camera, gaming and Unity mostly. My views are my own. In my free time, I'm a hardcore PC gamer and draw D&D maps for fun!

Join the conversation

Show comments Hide comments
+ -
blog comments powered by Disqus