Compiling Toolpack - Revision history

Allyntree at 14:40, 9 September 2022

2022-09-09T14:40:53Z

← Older revision		Revision as of 10:40, 9 September 2022
Line 1:		Line 1:
	Toolpack is provided with most of ~~it's~~ source code, so developers ~~can~~ develop their own applications, use example code, and even debug problems ~~within~~ the Toolpack framework if necessary.		{{DISPLAYTITLE:Compiling Toolpack}}
			Toolpack is provided with most of its source code, to enable developers to develop their own applications, use example code, and even debug problems in the Toolpack framework if necessary.
	The following procedure explains how to compile Toolpack.		The following procedure explains how to compile Toolpack.

	== Note ==		== Note ==
	The following procedure ~~provide~~ examples for package 2.5.53 for centos5 64 bits. Please adapt the procedure below for your platform and build number.		The following procedure provides examples for package 2.5.53 for centos5 64 bits. Please adapt the procedure below for your platform and build number.

	== Prerequisites ==		== Prerequisites ==
Line 9:		Line 10:

	== Download source code and pre-compiled libraries ==		== Download source code and pre-compiled libraries ==
	A couple of packages need to be downloaded. Some that contain source code, ~~other~~ that contain pre-compiled binaries and libraries for your platform.		A couple of packages need to be downloaded. Some that contain source code, and others that contain pre-compiled binaries and libraries for your platform.

	Please download the following source code packages:		Please download the following source code packages:
Line 15:		Line 16:
	* tbcmc_2.5.53_common.tgz		* tbcmc_2.5.53_common.tgz

	Please download the following binary packages (where 2.X.X is the version you wish to compile, and [platform] is your platform, ~~like~~ "x86_64-linux64_centos5_release"):		Please download the following binary packages (where 2.X.X is the version you wish to compile, and [platform] is your platform, such as "x86_64-linux64_centos5_release"):
	* tb640_2.5.53_x86_64-linux64_centos5_release.tgz		* tb640_2.5.53_x86_64-linux64_centos5_release.tgz
	* tbcmc_2.5.53_x86_64-linux64_centos5_release.tgz		* tbcmc_2.5.53_x86_64-linux64_centos5_release.tgz

	You can also download documentation package:		You can also download a documentation package:
	* tb-doc.zip		* tb-doc.zip

Lucas Trottier at 10:57, 28 June 2012

2012-06-28T10:57:46Z

← Older revision		Revision as of 06:57, 28 June 2012
Line 48:		Line 48:
	* lib/debug/x86_64-linux64/		* lib/debug/x86_64-linux64/
	Makefiles, when linking, will first use the libraries you compiled (if present), otherwise the official libraries. This allow compiling only applications, or only some libraries of the package, without having to recompile the whole thing.		Makefiles, when linking, will first use the libraries you compiled (if present), otherwise the official libraries. This allow compiling only applications, or only some libraries of the package, without having to recompile the whole thing.

			== Windows Platform ==
			* Only 32bit is supported (don't use X86_64=1 flag)
			1) Compile the library directory
			* cd tb/src/libraries
			* make all
			2) Compile toolpack
			* cd tb/src
			* make all

	[[Category:Tdev_OAM&P\|Compiling]]		[[Category:Tdev_OAM&P\|Compiling]]

Luc Morissette at 18:35, 25 February 2011

2011-02-25T18:35:47Z

← Older revision		Revision as of 14:35, 25 February 2011
Line 36:		Line 36:
	== Compile in debug ==		== Compile in debug ==
	To compile in debug (use X86_64=1 flag only for 64 bits packages):		To compile in debug (use X86_64=1 flag only for 64 bits packages):
	* '''For ~~elease~~ 2.4 and less only: mv lib/release lib/debug'''		* '''For release 2.4 and less only: mv lib/release lib/debug'''
	* cd src		* cd src
	* make all DBG=1 X86_64=1		* make all DBG=1 X86_64=1

Cbilodeau: add category

2011-02-17T14:32:15Z

add category

← Older revision		Revision as of 10:32, 17 February 2011
Line 48:		Line 48:
	* lib/debug/x86_64-linux64/		* lib/debug/x86_64-linux64/
	Makefiles, when linking, will first use the libraries you compiled (if present), otherwise the official libraries. This allow compiling only applications, or only some libraries of the package, without having to recompile the whole thing.		Makefiles, when linking, will first use the libraries you compiled (if present), otherwise the official libraries. This allow compiling only applications, or only some libraries of the package, without having to recompile the whole thing.

			[[Category:Tdev_OAM&P\|Compiling]]

Jcharest at 16:11, 16 February 2011

2011-02-16T16:11:47Z

← Older revision		Revision as of 12:11, 16 February 2011
Line 6:		Line 6:

	== Prerequisites ==		== Prerequisites ==
	Before compiling Toolpack's source code, make sure your host has all [[Toolpack_installation_2-5\|Toolpack prerequisites]]		Before compiling Toolpack's source code, make sure your host has all [[Toolpack_installation_2-5\|Toolpack prerequisites]]. In this case the "Toolpack Development Prerequisite" are NOT optional

	== Download source code and pre-compiled libraries ==		== Download source code and pre-compiled libraries ==

Abrassard: Created page with 'Toolpack is provided with most of it's source code, so developers can develop their own applications, use example code, and even debug problems within the Toolpack framework if n…'

2011-02-16T16:09:56Z

Created page with 'Toolpack is provided with most of it's source code, so developers can develop their own applications, use example code, and even debug problems within the Toolpack framework if n…'

New page

Toolpack is provided with most of it's source code, so developers can develop their own applications, use example code, and even debug problems within the Toolpack framework if necessary.
The following procedure explains how to compile Toolpack.

== Note ==
The following procedure provide examples for package 2.5.53 for centos5 64 bits. Please adapt the procedure below for your platform and build number.

== Prerequisites ==
Before compiling Toolpack's source code, make sure your host has all [[Toolpack_installation_2-5|Toolpack prerequisites]]

== Download source code and pre-compiled libraries ==
A couple of packages need to be downloaded. Some that contain source code, other that contain pre-compiled binaries and libraries for your platform.

Please download the following source code packages:
* tb640_2.5.53_common.tgz
* tbcmc_2.5.53_common.tgz

Please download the following binary packages (where 2.X.X is the version you wish to compile, and [platform] is your platform, like "x86_64-linux64_centos5_release"):
* tb640_2.5.53_x86_64-linux64_centos5_release.tgz
* tbcmc_2.5.53_x86_64-linux64_centos5_release.tgz

You can also download documentation package:
* tb-doc.zip

== Unzip all packages ==
Unzip all the packages above in the same folder (say "yes" when asked to replace duplicated files):
* tar -zxf tb640_2.5.53_common.tgz
* tar -zxf tb640_2.5.53_x86_64-linux64_centos5_release.tgz
* tar -zxf tbcmc_2.5.53_common.tgz
* tar -zxf tbcmc_2.5.53_x86_64-linux64_centos5_release.tgz

== Compile in release ==
To compile in release (use X86_64=1 flag only for 64 bits packages):
* cd tb/src
* make all X86_64=1

== Compile in debug ==
To compile in debug (use X86_64=1 flag only for 64 bits packages):
* '''For elease 2.4 and less only: mv lib/release lib/debug'''
* cd src
* make all DBG=1 X86_64=1

== Compilation results ==
The libraries pre-compiled from the packages are located in
* lib/official/x86_64-linux64/
The libraries you compiled yourself are located in
* lib/release/x86_64-linux64/
or
* lib/debug/x86_64-linux64/
Makefiles, when linking, will first use the libraries you compiled (if present), otherwise the official libraries. This allow compiling only applications, or only some libraries of the package, without having to recompile the whole thing.