Differences

This shows you the differences between two versions of the page.

--- 2500_config_apps:4300_runtime_exec [2026/08/13 00:55] – ↷ Page moved from docs:2500_config_apps:4300_runtime_exec to 2500_config_apps:4300_runtime_exec localdev
+++ 2500_config_apps:4300_runtime_exec [2026/08/13 07:33] (current) – Imported by DokuWiki Advanced Plugin aware_support3
@@ Line 2: / Line 2: @@
 ====== Building Runtime Executable ======
-<callout type="primary" icon="true" title="note"> This feature is only available in the AwareIM Developer Edition.</callout>
+<alert type="primary" icon="fa info-circle">
+**note**
+ This feature is only available in the AwareIM Developer Edition.</alert>
 If you want to sell applications configured with //**AwareIM**// you can use the "Build Executable" feature to prepare the system for your end users with your own product name and copyright.
@@ Line 62: / Line 65: @@
 ===== Custom JAR’s location =====
-If your application requires any custom JAR files (for example if you write your own Java extensions – see [[2000_concepts:0900_prod_feats:0800_extending_awareim|Extending AwareIM]] and [[docs:3500|Programmers Reference Guide]]), move these JAR files into a separate directory and specify the name of this directory. This value is optional.
+If your application requires any custom JAR files (for example if you write your own Java extensions – see [[2000_concepts:0900_prod_feats:0800_extending_awareim|Extending AwareIM]] and [[:3500|Programmers Reference Guide]]), move these JAR files into a separate directory and specify the name of this directory. This value is optional.
 ===== JDK location =====
@@ Line 70: / Line 73: @@
 Once you provide the required values and press OK //**AwareIM**// will build the executable (for Windows platform) or zip file (for Linux and Mac OS X platforms) in the output directory that you specified. You can distribute this executable or zip file to your end users.
-<callout type="primary" icon="true" title="note"> When you install the runtime application you will not be able to run the Configuration Tool. If you want users to be able ton run the Configuraton Tool install the standalone Configuration Tool on the runtime machine or copy the AwareIM/ConfigTool directory from your development machine to the runtime machine.</callout>
+<alert type="primary" icon="fa info-circle">
+**note**
+ When you install the runtime application you will not be able to run the Configuration Tool. If you want users to be able ton run the Configuraton Tool install the standalone Configuration Tool on the runtime machine or copy the AwareIM/ConfigTool directory from your development machine to the runtime machine.</alert>
+<alert type="primary" icon="fa info-circle">
+**note**
-<callout type="primary" icon="true" title="note"> If you are distributing an application for Mac OS X platform you can take the resulting zip file to the Mac platform, unpack it and create an application bundle and/or distributable package out of it (see Mac OS X manuals for details). You can then distribute the application bundle or package to your customers. If you decide to distribute the application as an original zip file, you will need to provide startup instructions in a readme file. Customers will need to unpack the zip file, start the Mac OS X Terminal application, change to the ''BIN'' directory and run the startAwareIM.sh script.</callout>
+ If you are distributing an application for Mac OS X platform you can take the resulting zip file to the Mac platform, unpack it and create an application bundle and/or distributable package out of it (see Mac OS X manuals for details). You can then distribute the application bundle or package to your customers. If you decide to distribute the application as an original zip file, you will need to provide startup instructions in a readme file. Customers will need to unpack the zip file, start the Mac OS X Terminal application, change to the ''BIN'' directory and run the startAwareIM.sh script.</alert>