Node Webkit - platforms to export

We have some projects that are taking quite a bit of time to export via Node-Webkit (more than 30 mins <img src="smileys/smiley19.gif" border="0" align="middle" /> ).

This pumps out the win32, osx, linux32, linux64 builds.

While being a nice coffee break opportunity, it would be great if we could reduce our export times.

Would having a choice of which platforms to export to in Node-Webkit help this?

We send win32 and osx builds regularly for testing, but only require the linux builds on our release builds.

Would love to know if there is a way currently to set this, or perhaps it would be a simple addition for the future? <img src="smileys/smiley9.gif" border="0" align="middle" />

It is hard to express how much we love Construct 2! Great job guys! <img src="smileys/smiley32.gif" border="0" align="middle" />

No, it wouldn't - it exports once and then just applies wrappers to the same data. 30 minutes is really an extraordinary amount of time, especially considering key parts of the export process can use multicore processors. You must have an ultra-huge project or a super-slow computer! Try skipping image recompression.

Thanks for the fast response and clarification Ashley, much appreciated.

This project does have a huge amount of large image data (a requirement of our current brief).

-edit.. just read this..

"If you choose None for the PNG recompression setting on export, the color counting and PNGCrush steps are skipped."

scirra.com/tutorials/577/construct-2s-export-time-optimisations

Setting this to "None" reduced the export time to under 5 mins!

You just saved us a whole lot of wasted time in these test builds!

Thank you!!!!

I do that for most of my test exports on even html5 exports, turn off PNG Crush and minimize and it finishes dozens of times faster. However it makes the final export seem really long (scary) if you weren't already experiencing it in tests. ;-)