279 pageTitle: 'Build' |
279 pageTitle: 'Build' |
280 windowSpecSelector: page7_buildSpec |
280 windowSpecSelector: page7_buildSpec |
281 canEnterQuerySelector: #canEnterBuild |
281 canEnterQuerySelector: #canEnterBuild |
282 enterCallbackSelector: #restoreMakeOutputsContents |
282 enterCallbackSelector: #restoreMakeOutputsContents |
283 leaveCallbackSelector: #rememberMakeOutputsContents |
283 leaveCallbackSelector: #rememberMakeOutputsContents |
284 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.' |
284 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). |
|
285 You must have the compiler (borland-bcc or visual-c) and NullSoft NSIS packages installed for this to work. |
|
286 Without NSIS, zip the folder where the exe is generated and unzip on a target machine. |
|
287 <P> |
|
288 To try the application, open an explorer/finder on the directory and double click on the executable. |
|
289 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.' |
285 ) |
290 ) |
286 |
291 |
287 (AssistantPageSpec |
292 (AssistantPageSpec |
288 pageTitle: 'Deploy' |
293 pageTitle: 'Deploy' |
289 windowSpecSelector: page8_deploySpec |
294 windowSpecSelector: page8_deploySpec |
290 canEnterQuerySelector: #canEnterDeploy |
295 canEnterQuerySelector: #canEnterDeploy |
291 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.' |
296 infoText: 'Find the installer-file to be deployed (or test-run the executable). |
|
297 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.' |
292 ) |
298 ) |
293 ) decodeAsLiteralArray. |
299 ) decodeAsLiteralArray. |
294 |
300 |
295 "Modified: / 04-09-2012 / 09:49:50 / cg" |
301 "Modified: / 04-09-2012 / 09:49:50 / cg" |
296 ! ! |
302 ! ! |