Cbridge setup - Versionsgeschichte

Cg: /* Ensure that the compilation works */

2026-03-23T13:09:36Z

Ensure that the compilation works

← Nächstältere Version		Version vom 23. März 2026, 13:09 Uhr
Zeile 115:		Zeile 115:
	* check if the compiler is correctly installed (especially MSVC and MINGW sometimes make trouble here).		* check if the compiler is correctly installed (especially MSVC and MINGW sometimes make trouble here).
	:: one particular problem with MSVC is when deinstalling and reinstalling another version. There seem to be leftover files and/or registry entries which may break the installation (this happend to one of our customers, and also to us when upgrading)		:: one particular problem with MSVC is when deinstalling and reinstalling another version. There seem to be leftover files and/or registry entries which may break the installation (this happend to one of our customers, and also to us when upgrading)
	:: Enter the compile-command ("cl", "cc", "gcc" or "clang") on a command line (cmd or shell)		* Enter the compile-command ("cl", "cc", "gcc" or "clang") on a command line (cmd or shell)
	:: check that you get an answer		:: check that you get an answer
	:: try to compile a one-liner (eg. "<code>main() { printf("hello\n"); }</code>" and run it to see if it links correctly. Run it!		:: try to compile a one-liner (eg. "<code>main() { printf("hello\n"); }</code>" and run it to see if it links correctly. Run it!

Cg: /* Ensure that the compilation works */

2026-03-23T13:09:13Z

Ensure that the compilation works

← Nächstältere Version		Version vom 23. März 2026, 13:09 Uhr
Zeile 115:		Zeile 115:
	* check if the compiler is correctly installed (especially MSVC and MINGW sometimes make trouble here).		* check if the compiler is correctly installed (especially MSVC and MINGW sometimes make trouble here).
	:: one particular problem with MSVC is when deinstalling and reinstalling another version. There seem to be leftover files and/or registry entries which may break the installation (this happend to one of our customers, and also to us when upgrading)		:: one particular problem with MSVC is when deinstalling and reinstalling another version. There seem to be leftover files and/or registry entries which may break the installation (this happend to one of our customers, and also to us when upgrading)
	:: ~~enter~~ the ~~compil~~-command ("cl", "cc", "gcc" or "clang") on a command line (cmd or shell)		:: Enter the compile-command ("cl", "cc", "gcc" or "clang") on a command line (cmd or shell)
	:: check that you get an answer		:: check that you get an answer
	:: try to compile a one-liner (eg. "<code>main() { printf("hello\n"); }</code>" and run it to see if it links correctly		:: try to compile a one-liner (eg. "<code>main() { printf("hello\n"); }</code>" and run it to see if it links correctly. Run it!
	* check if ~~that~~ script file works by running "<code>cBridge --log --ccScript <scriptfilename> --testCompile</code>"		* check if the bridge's cc script file works by running "<code>cBridge --log --ccScript <scriptfilename> --testCompile</code>"
	:: if required, make a copy of one of the script files (the one you think is best to start with) and fix any path inside. If required, add echo statements to show what is going on. Keep the original script and create a new one.		:: if required, make a copy of one of the script files (the one you think is best to start with) and fix any path inside. If required, add echo statements to show what is going on. Keep the original script and create a new one.
	:: under Windows: in the script, the PATH to the compiler is typically searched and set; for example by calling the vcvarsall.bat script which is provided by microsoft. If required, change the line which calls this (you can also add this batch-call to your autoexec.bat and remove the line from the script). In any case: at the end, the "cl" command should be found along your path.		:: under Windows: in the script, the PATH to the compiler is typically searched and set; for example by calling the vcvarsall.bat script which is provided by microsoft. If required, change the line which calls this (you can also add this batch-call to your autoexec.bat and remove the line from the script). In any case: at the end, the "cl" command should be found along your path.

Cg: /* Ensure that the compilation works */

2026-03-23T13:08:04Z

Ensure that the compilation works

← Nächstältere Version		Version vom 23. März 2026, 13:08 Uhr
Zeile 114:		Zeile 114:
	* check which compiler you installed and intent to use (MSVC, Mingw, gcc, clang or bcc), and look for a corresponding script file.		* check which compiler you installed and intent to use (MSVC, Mingw, gcc, clang or bcc), and look for a corresponding script file.
	* check if the compiler is correctly installed (especially MSVC and MINGW sometimes make trouble here).		* check if the compiler is correctly installed (especially MSVC and MINGW sometimes make trouble here).
			:: one particular problem with MSVC is when deinstalling and reinstalling another version. There seem to be leftover files and/or registry entries which may break the installation (this happend to one of our customers, and also to us when upgrading)
	:: enter the compil-command ("cl", "cc", "gcc" or "clang") on a command line (cmd or shell)		:: enter the compil-command ("cl", "cc", "gcc" or "clang") on a command line (cmd or shell)
	:: check that you get an answer		:: check that you get an answer

Cg: /* Ensure that the compilation works */

2026-03-20T14:50:25Z

Ensure that the compilation works

← Nächstältere Version		Version vom 20. März 2026, 14:50 Uhr
Zeile 116:		Zeile 116:
	:: enter the compil-command ("cl", "cc", "gcc" or "clang") on a command line (cmd or shell)		:: enter the compil-command ("cl", "cc", "gcc" or "clang") on a command line (cmd or shell)
	:: check that you get an answer		:: check that you get an answer
	:: try to compile a one-liner (eg. "<code>main() { printf("hello\n"); }</code>"		:: try to compile a one-liner (eg. "<code>main() { printf("hello\n"); }</code>" and run it to see if it links correctly
	* check if that script file works by running "<code>cBridge --log --ccScript <scriptfilename> --testCompile</code>"		* check if that script file works by running "<code>cBridge --log --ccScript <scriptfilename> --testCompile</code>"
	:: if required, make a copy of one of the script files (the one you think is best to start with) and fix any path inside. If required, add echo statements to show what is going on. Keep the original script and create a new one.		:: if required, make a copy of one of the script files (the one you think is best to start with) and fix any path inside. If required, add echo statements to show what is going on. Keep the original script and create a new one.

Cg: /* Ensure that the compilation works */

2026-03-20T14:47:22Z

Ensure that the compilation works

← Nächstältere Version		Version vom 20. März 2026, 14:47 Uhr
Zeile 112:		Zeile 112:
	* stop the manually started C-bridge (in the shell/cmd window) by pressing CTRL-C there		* stop the manually started C-bridge (in the shell/cmd window) by pressing CTRL-C there
	* depending on the C-compiler you intend to use, one of the "compile_xxx.bat" or "compile_xxx.sh" script files will be used. The task to be performed by these scripts is to compile a given C-file.		* depending on the C-compiler you intend to use, one of the "compile_xxx.bat" or "compile_xxx.sh" script files will be used. The task to be performed by these scripts is to compile a given C-file.
	* check which compiler you installed and intent to use (MSVC, Mingw, gcc, clang or bcc),and look for a corresponding script file.		* check which compiler you installed and intent to use (MSVC, Mingw, gcc, clang or bcc), and look for a corresponding script file.
			* check if the compiler is correctly installed (especially MSVC and MINGW sometimes make trouble here).
			:: enter the compil-command ("cl", "cc", "gcc" or "clang") on a command line (cmd or shell)
			:: check that you get an answer
			:: try to compile a one-liner (eg. "<code>main() { printf("hello\n"); }</code>"
	* check if that script file works by running "<code>cBridge --log --ccScript <scriptfilename> --testCompile</code>"		* check if that script file works by running "<code>cBridge --log --ccScript <scriptfilename> --testCompile</code>"
	:: if required, make a copy of one of the script files (the one you think is best to start with) and fix any path inside. If required, add echo statements to show what is going on. Keep the original script and create a new one.		:: if required, make a copy of one of the script files (the one you think is best to start with) and fix any path inside. If required, add echo statements to show what is going on. Keep the original script and create a new one.

Cg: /* Ensure that the cBridge is reachable from expecco */

2026-03-19T13:24:47Z

Ensure that the cBridge is reachable from expecco

← Nächstältere Version		Version vom 19. März 2026, 13:24 Uhr
Zeile 102:		Zeile 102:
	:: enter CBridge Host and Port as "<code>localhost</code>" and the above port number (default is 8855)		:: enter CBridge Host and Port as "<code>localhost</code>" and the above port number (default is 8855)
	* close the settings dialog (without saving the settings for now, when asked)		* close the settings dialog (without saving the settings for now, when asked)
	* open a new project ~~(the~~ default project will ~~contains~~ a sample "Hello World" C-action, which can be used for the smoke test.		* open a new project.<br>The default project will contain a sample "Hello World" C-action, which can be used for the smoke test.
	* in the expecco tree, find the "<code>Simple Elementary Action (C)</code>" (under the "Activities" group).		* in the expecco tree, find the "<code>Simple Elementary Action (C)</code>" (under the "Activities" group).
	* run it		* run it

Cg: /* Step-by-Step Problem Finding/Fixing */

2026-03-19T13:23:30Z

Step-by-Step Problem Finding/Fixing

← Nächstältere Version		Version vom 19. März 2026, 13:23 Uhr
Zeile 90:		Zeile 90:
	* start the bridge with "<code>cBridge --log</code>"		* start the bridge with "<code>cBridge --log</code>"
	:: it should output some messages, the last being "<code>... listening on port xxxx</code>"		:: it should output some messages, the last being "<code>... listening on port xxxx</code>"
	* if the cBridge is to run on a machine different from the one expecco is running on, make sure that the firewall allows for connections between the two machines (at the ~~desied~~ port nr)		* if the cBridge is to run on a machine different from the one expecco is running on, make sure that the firewall allows for connections between the two machines (at the desired port nr)
	* if required, use another port (i.e. run it with "<code>cBridge --log --port <Nr></code>")		* if required, use another port (i.e. run it with "<code>cBridge --log --port <Nr></code>")
	:: now we have a cBridge running, ready to accept connections from expecco at the given port nr.		:: now we have a cBridge running, ready to accept connections from expecco at the given port nr.

Cg: /* Ensure that the cBridge executable is present and can be executed */

2026-03-19T13:22:00Z

Ensure that the cBridge executable is present and can be executed

← Nächstältere Version		Version vom 19. März 2026, 13:22 Uhr
Zeile 87:		Zeile 87:
	* open a shell- or cmd window (and navigate there).		* open a shell- or cmd window (and navigate there).
	* type "<code>cBridge --help</code>" (with powershell: "<code>.\cBridge --help</code>")		* type "<code>cBridge --help</code>" (with powershell: "<code>.\cBridge --help</code>")
	:: if that fails (does not output some useful help text), make sure that it can be executed.<br>Maybe your security policy is too strict.		:: if that fails (does not output some useful help text), make sure that it can be executed.<br>Maybe your security policy is too strict ot the installation is incomplete.
	* start the bridge with "<code>cBridge --log</code>"		* start the bridge with "<code>cBridge --log</code>"
	:: it should output some messages, the last being "<code>... listening on port xxxx</code>"		:: it should output some messages, the last being "<code>... listening on port xxxx</code>"

Cg: /* Ensure that the cBridge executable is present and can be executed */

2026-03-19T13:21:22Z

Ensure that the cBridge executable is present and can be executed

← Nächstältere Version		Version vom 19. März 2026, 13:21 Uhr
Zeile 85:		Zeile 85:
	=== Ensure that the cBridge executable is present and can be executed ===		=== Ensure that the cBridge executable is present and can be executed ===
	* goto the expecco installation folder (typically somewhere under "<code>c:\Program Files\exept\expecco\</code>"), and look for files named "<code>cBridge.exe</code>" or "<code>cBridge32.exe</code>" or "<code>cBridge</code>" (under Unix/Linux). It is typically found in a sub folder named "<code>packages/expecco/bridgeFramework/cBridge</code>".		* goto the expecco installation folder (typically somewhere under "<code>c:\Program Files\exept\expecco\</code>"), and look for files named "<code>cBridge.exe</code>" or "<code>cBridge32.exe</code>" or "<code>cBridge</code>" (under Unix/Linux). It is typically found in a sub folder named "<code>packages/expecco/bridgeFramework/cBridge</code>".
	* open a shell- or cmd window.		* open a shell- or cmd window (and navigate there).
	* type "<code>cBridge --help</code>" (with powershell: "<code>.\cBridge --help</code>")		* type "<code>cBridge --help</code>" (with powershell: "<code>.\cBridge --help</code>")
	:: if that fails (does not output some useful help text), make sure that it can be executed.<br>Maybe your security policy is too strict.		:: if that fails (does not output some useful help text), make sure that it can be executed.<br>Maybe your security policy is too strict.

Cg: /* Ensure that the cBridge executable is present and can be executed */

2026-03-19T13:20:59Z

Ensure that the cBridge executable is present and can be executed

← Nächstältere Version		Version vom 19. März 2026, 13:20 Uhr
Zeile 84:		Zeile 84:

	=== Ensure that the cBridge executable is present and can be executed ===		=== Ensure that the cBridge executable is present and can be executed ===
	* goto the expecco installation folder (typically somewhere under "<code>c:\Program Files\exept\expecco\</code>"), and look for files named "<code>cBridge.exe</code>" or "<code>cBridge32.exe</code>" or "<code>cBridge</code>" (under Unix/Linux). It is typically found in a sub folder named "packages/expecco/bridgeFramework".		* goto the expecco installation folder (typically somewhere under "<code>c:\Program Files\exept\expecco\</code>"), and look for files named "<code>cBridge.exe</code>" or "<code>cBridge32.exe</code>" or "<code>cBridge</code>" (under Unix/Linux). It is typically found in a sub folder named "<code>packages/expecco/bridgeFramework/cBridge</code>".
	* open a shell- or cmd window.		* open a shell- or cmd window.
	* type "<code>cBridge --help</code>" (with powershell: "<code>.\cBridge --help</code>")		* type "<code>cBridge --help</code>" (with powershell: "<code>.\cBridge --help</code>")