Question About Windows Standalone

[Mark Schonewille]

Hi Gregory,

You need to send the entire Windows folder to your users. This includes the separate stack files, referenced files if there are any, and the externals folder. You might leave out the externals folder if you really want to.

If you prefer to send just one file, you could use the Installer Maker Plugin. This plugin creates one .exe file, which you don't need to compress to send it to your users. The .exe file doesn't need any externals, so you don't need to include that folder, even if your own standalone needs externals (but you need to include the externals when you make the installer). You can find the Installer Maker Plugin here http://qery.us/za

--
Best regards,

Mark Schonewille

Economy-x-Talk Consulting and Software Engineering
Homepage: http://economy-x-talk.com
Twitter: http://twitter.com/xtalkprogrammer
KvK: 50277553

Send me a friend request on Facebook if you like https://www.facebook.com/marksch

On 6 sep 2011, at 02:11, Gregory Lypny wrote:

> Hello everyone,
> 
> I’m am Mac user who doesn’t know much, if anything, about Windows.  I’ve just built a standalone for Mac and Windows and I’d like to confirm what it is I need to provide to Windows users.  The Standalone Builder produced a folder called Windows.  Inside of it is a folder called Externals, which is empty because I have none, the executable file, and the stack files I used in the project.  Do I give users the entire Windows folder or just the executable?  The reason that I ask is that the Mac build hides everything nicely in a package, and I was a little concerned seeing those stack files sitting out in the open.
> 
> Regards,
> 
> Gregory
>