diff -r d03c40cd3fa5 -r 6d37e90dab00 Tools__ProjectBuilderAssistantApplication.st --- a/Tools__ProjectBuilderAssistantApplication.st Mon Mar 11 19:39:57 2013 +0100 +++ b/Tools__ProjectBuilderAssistantApplication.st Mon Mar 11 20:07:35 2013 +0100 @@ -281,14 +281,20 @@ canEnterQuerySelector: #canEnterBuild enterCallbackSelector: #restoreMakeOutputsContents leaveCallbackSelector: #rememberMakeOutputsContents - infoText: 'Start the build-process. This will run "make"+"bcc/vc/gcc" to compile all required classes and "nsis" to generate a self-installable executable (on windows). You must have the compiler (borland-bcc or visual-c) and NullSoft NSIS packages installed for this to work.' + infoText: 'Start the build-process. This will run "make"+"bcc/vc/gcc" to compile all required classes and "nsis" to generate a self-installable executable (on windows). +You must have the compiler (borland-bcc or visual-c) and NullSoft NSIS packages installed for this to work. +Without NSIS, zip the folder where the exe is generated and unzip on a target machine. +

+To try the application, open an explorer/finder on the directory and double click on the executable. +Alternatively, open a command window and type the name of the executable there. Sorry, but double-click in the ST/X file browser does not work.' ) (AssistantPageSpec pageTitle: 'Deploy' windowSpecSelector: page8_deploySpec canEnterQuerySelector: #canEnterDeploy - infoText: 'Find the installer to be deployed (or test-run the binary). You can open a Windows-Explorer there to copy the files for deployment. After that, the build directory is no longer needed. However, you can keep it for a faster compile the next time.' + infoText: 'Find the installer-file to be deployed (or test-run the executable). +You can open a Windows-explorer/finder there to copy the files for deployment. After that, the build directory is no longer needed. However, you can keep it for a faster compile the next time.' ) ) decodeAsLiteralArray.