Messaged compilation - Revision history

Dcunningham at 00:09, 30 May 2025

2025-05-30T00:09:13Z

← Older revision		Revision as of 00:09, 30 May 2025
Line 2:		Line 2:

	To check what version might already be installed run <code>go version</code>. If the version is less than 1.20 you should definitely upgrade.		To check what version might already be installed run <code>go version</code>. If the version is less than 1.20 you should definitely upgrade.

			Compiling messaged on a system with a newer version of GLIBC can mean that it won't run on systems with an older version, so it's better to compile messaged on older versions. Voisonics uses dev-4-2 for this.

	=== Installing go ===		=== Installing go ===

2024-07-01T01:06:50Z

← Older revision		Revision as of 01:06, 1 July 2024
Line 1:		Line 1:
			=== Check what's installed ===

			To check what version might already be installed run <code>go version</code>. If the version is less than 1.20 you should definitely upgrade.

	=== Installing go ===		=== Installing go ===

2023-06-09T01:10:24Z

← Older revision		Revision as of 01:10, 9 June 2023
Line 23:		Line 23:
	Run: <code>make</code>		Run: <code>make</code>

	If subsequent runs of make don't do anything ~~you~~ ~~can~~ ~~instead run:~~ <code>~~go build cmd/~~messaged</code>		If subsequent runs of make don't do anything, delete the compiled <code>messaged</code> first and then try again.

	Note that the 4.1 code was copied to 4.0 in ticket #8215 to take advantage of the better compilation system.

2023-06-09T01:03:37Z

← Older revision		Revision as of 01:03, 9 June 2023
Line 15:		Line 15:
	Then <code>cd</code> into the root directory of the git clone.		Then <code>cd</code> into the root directory of the git clone.

	=== Compiling messaged in 4.0 and below ===		=== Compiling messaged in 3.15 and below ===

	You should be able to run <code>go build</code>, but it may not work with recent versions of Go.		You should be able to run <code>go build</code>, but it may not work with recent versions of Go.

	=== Compiling messaged in 4.1 and above ===		=== Compiling messaged in 4.0 and above ===

	Run: <code>make</code>		Run: <code>make</code>

	If subsequent runs of make don't do anything you can instead run: <code>go build cmd/messaged</code>		If subsequent runs of make don't do anything you can instead run: <code>go build cmd/messaged</code>

			Note that the 4.1 code was copied to 4.0 in ticket #8215 to take advantage of the better compilation system.

2023-06-07T03:08:48Z

← Older revision		Revision as of 03:08, 7 June 2023
Line 21:		Line 21:
	=== Compiling messaged in 4.1 and above ===		=== Compiling messaged in 4.1 and above ===

	Run <code>make</code>.		Run: <code>make</code>

	If subsequent runs of ~~<code>~~make~~</code>~~ don't do anything you can run <code>go build cmd/messaged</code> ~~instead.~~		If subsequent runs of make don't do anything you can instead run: <code>go build cmd/messaged</code>

2023-06-07T03:08:13Z

← Older revision		Revision as of 03:08, 7 June 2023
Line 11:		Line 11:
	The Enswitch messaged program is held in the git repository.		The Enswitch messaged program is held in the git repository.

	Check out the branch for the Enswitch version you're working on, for example: <code>git checkout -b 4.2 <username>@git.integrics.com:enswitch</code>.		Check out the branch for the Enswitch version you're working on, for example: <code>git checkout -b 4.2 <username>@git.integrics.com:enswitch</code>

	Then <code>cd</code> into the root directory of the git clone.		Then <code>cd</code> into the root directory of the git clone.

2023-06-07T03:08:01Z

← Older revision		Revision as of 03:08, 7 June 2023
Line 7:		Line 7:
	Install into /usr/local: <code>tar -C /usr/local -xvf <file downloaded></code>		Install into /usr/local: <code>tar -C /usr/local -xvf <file downloaded></code>

	=== ~~Compiling~~ ~~messaged~~ ===		=== Getting the source code ===

	The Enswitch messaged program is held in the git repository.		The Enswitch messaged program is held in the git repository.
Line 13:		Line 13:
	Check out the branch for the Enswitch version you're working on, for example: <code>git checkout -b 4.2 <username>@git.integrics.com:enswitch</code>.		Check out the branch for the Enswitch version you're working on, for example: <code>git checkout -b 4.2 <username>@git.integrics.com:enswitch</code>.

	Then ~~from~~ the root directory of the git clone ~~you can run <code>make</code>~~.		Then <code>cd</code> into the root directory of the git clone.

			=== Compiling messaged in 4.0 and below ===

			You should be able to run <code>go build</code>, but it may not work with recent versions of Go.

			=== Compiling messaged in 4.1 and above ===

			Run <code>make</code>.

	If subsequent runs of <code>make</code> don't do anything you can run <code>go build cmd/messaged</code> instead.		If subsequent runs of <code>make</code> don't do anything you can run <code>go build cmd/messaged</code> instead.

2023-06-06T00:02:52Z

← Older revision		Revision as of 00:02, 6 June 2023
Line 15:		Line 15:
	Then from the root directory of the git clone you can run <code>make</code>.		Then from the root directory of the git clone you can run <code>make</code>.

	If subsequent runs of <code>make</code> don't do anything you can run <code>go build ./cmd/messaged</code> instead.		If subsequent runs of <code>make</code> don't do anything you can run <code>go build cmd/messaged</code> instead.

2023-05-24T02:17:51Z

← Older revision		Revision as of 02:17, 24 May 2023
Line 11:		Line 11:
	The Enswitch messaged program is held in the git repository.		The Enswitch messaged program is held in the git repository.

	Check out the branch for the Enswitch version you're working on, for example: <code>git checkout -b 4.2 ~~git~~@git.integrics.com:enswitch</code>.		Check out the branch for the Enswitch version you're working on, for example: <code>git checkout -b 4.2 <username>@git.integrics.com:enswitch</code>.

	Then from the root directory of the git clone you can run <code>make</code>.		Then from the root directory of the git clone you can run <code>make</code>.

2023-05-24T01:47:34Z

← Older revision		Revision as of 01:47, 24 May 2023
Line 11:		Line 11:
	The Enswitch messaged program is held in the git repository.		The Enswitch messaged program is held in the git repository.

	Check out the branch for the Enswitch version you're working on, for example: <code>git checkout 4.2</code>.		Check out the branch for the Enswitch version you're working on, for example: <code>git checkout -b 4.2 git@git.integrics.com:enswitch</code>.

	Then from the root directory of the git clone you can run <code>make</code>.		Then from the root directory of the git clone you can run <code>make</code>.