Cross compiling standalone packages for the camera - Revision history

Andrey.filippov at 04:13, 22 January 2019

2019-01-22T04:13:37Z

← Older revision		Revision as of 04:13, 22 January 2019
Line 1:		Line 1:
	{{Legacy}}		{{Legacy}}
	This page describes software for [[353_legacy]] - legacy Model 353 cameras		This page describes software for [[353_legacy]] - legacy Model 353 cameras.

	This procedure is intended to		This procedure is intended to
	* test software before including it in the cvs,		* test software before including it in the cvs,

Andrey.filippov at 04:13, 22 January 2019

2019-01-22T04:13:11Z

← Older revision		Revision as of 04:13, 22 January 2019
Line 1:		Line 1:
			{{Legacy}}
			This page describes software for [[353_legacy]] - legacy Model 353 cameras
	This procedure is intended to		This procedure is intended to
	* test software before including it in the cvs,		* test software before including it in the cvs,

Luxigo: /* Setting environment variables */

2010-06-20T04:05:48Z

Setting environment variables

← Older revision		Revision as of 04:05, 20 June 2010
Line 26:		Line 26:
	export CXX=${TOOLCHAIN}/bin/crisv32-axis-linux-gnu-g++		export CXX=${TOOLCHAIN}/bin/crisv32-axis-linux-gnu-g++
	export CPP=${TOOLCHAIN}/bin/crisv32-axis-linux-gnu-cpp		export CPP=${TOOLCHAIN}/bin/crisv32-axis-linux-gnu-cpp
			export AR=${TOOLCHAIN}/bin/crisv32-axis-linux-gnu-ar
			export RANLIB=${TOOLCHAIN}/bin/crisv32-axis-linux-gnu-ranlib

	# options		# options

Luxigo at 03:38, 20 June 2010

2010-06-20T03:38:47Z

← Older revision		Revision as of 03:38, 20 June 2010
Line 50:		Line 50:
	=When the software is not packaged using autoconf and automake=		=When the software is not packaged using autoconf and automake=
	Edit the Makefile		Edit the Makefile

			=Install the software on the camera=
			The first time, create a symbolic link for crisv32 directory in /usr/local, eg:
			ssh root@cam ln -s . /usr/local/crisv32

			Copy the software to the camera /usr/local directory, eg:
			tar c /usr/local/crisv32/. \| ssh root@cam tar xv -C /
			(you may want to strip binaries and remove documentation before)

			To run the software on the camera you may have to define:
			export PATH=/usr/local/bin:$PATH
			export LD_LIBRARY_PATH=/usr/local/lib:$LD_LIBRARY_PATH

Luxigo: /* When the software is packaged using autoconf and automake */

2010-06-20T03:30:23Z

When the software is packaged using autoconf and automake

← Older revision		Revision as of 03:30, 20 June 2010
Line 47:		Line 47:
	make		make
	make install		make install

	~~and mount or copy the resulting /usr/local/crisv32 to the camera~~
	~~(you may want to strip binaries and remove documentation before)~~

	~~Then to run the software on the camera you may have to define:~~
	~~export PATH=/usr/local/crisv32/bin:$PATH~~
	~~export LD_LIBRARY_PATH=/usr/local/crisv32/lib:$LD_LIBRARY_PATH~~

	=When the software is not packaged using autoconf and automake=		=When the software is not packaged using autoconf and automake=
	Edit the Makefile		Edit the Makefile

Luxigo: /* Setting environment variables */

2010-06-20T03:23:51Z

Setting environment variables

← Older revision		Revision as of 03:23, 20 June 2010
Line 10:		Line 10:

	You must source init_env from the Elphel firmware source directory, eg:		You must source init_env from the Elphel firmware source directory, eg:
	ELPHEL_SOURCEDIR=/usr/local/src/~~elphel~~-~~cvs/353~~/elphel353		ELPHEL_SOURCEDIR=/usr/local/src/elphel353-8.0.7/elphel353
	cd $ELPHEL_SOURCEDIR		cd $ELPHEL_SOURCEDIR
	source init_env		source init_env
Line 18:		Line 18:
	# toolchain		# toolchain
	TOOLCHAIN=/usr/local/cris		TOOLCHAIN=/usr/local/cris
			export PATH=/usr/local/crisv32/bin:$PATH
	export PATH=${TOOLCHAIN}/crisv32-axis-linux-gnu/bin:$PATH		export PATH=${TOOLCHAIN}/crisv32-axis-linux-gnu/bin:$PATH
	export PATH=${TOOLCHAIN}/bin:$PATH		export PATH=${TOOLCHAIN}/bin:$PATH

Luxigo at 16:24, 10 March 2009

2009-03-10T16:24:59Z

← Older revision		Revision as of 16:24, 10 March 2009
Line 1:		Line 1:
	This procedure is intended to test software before ~~taking time to include~~ it in the ~~firmware build~~,		This procedure is intended to
			* test software before including it in the cvs,
	or to build software that would be too big to fit into the firmware image.		* to build software that would be too big to fit into the firmware image,
			* to build standalone packages you just dont want to include into the firmware image.

	=First=		=First=

Luxigo at 16:17, 10 March 2009

2009-03-10T16:17:19Z

← Older revision		Revision as of 16:17, 10 March 2009
Line 3:		Line 3:
	or to build software that would be too big to fit into the firmware image.		or to build software that would be too big to fit into the firmware image.


			=First=
	ELPHEL_SOURCEDIR and TOOLCHAIN values below are installation dependent, check if it match yours.		ELPHEL_SOURCEDIR and TOOLCHAIN values below are installation dependent, check if it match yours.

	=~~First~~=		=Setting environment variables=

	You must source init_env from the Elphel firmware source directory, eg:		You must source init_env from the Elphel firmware source directory, eg:
	ELPHEL_SOURCEDIR=/usr/local/src/elphel-cvs/353/elphel353		ELPHEL_SOURCEDIR=/usr/local/src/elphel-cvs/353/elphel353
Line 11:		Line 14:
	source init_env		source init_env

	~~=Setting environment variables=~~		and set the following variables:
	~~(check ./configure --help~~ and the ~~Makefile to see if more is needed)~~

	# toolchain		# toolchain
Line 36:		Line 38:
	export CFLAGS="${CFLAGS} -I/usr/local/crisv32/include"		export CFLAGS="${CFLAGS} -I/usr/local/crisv32/include"
	export CXXFLAGS=${CFLAGS}		export CXXFLAGS=${CFLAGS}

			(check ./configure --help and the Makefile to see if more is needed)

	=When the software is packaged using autoconf and automake=		=When the software is packaged using autoconf and automake=

Luxigo at 16:14, 10 March 2009

2009-03-10T16:14:05Z

← Older revision		Revision as of 16:14, 10 March 2009
Line 2:		Line 2:

	or to build software that would be too big to fit into the firmware image.		or to build software that would be too big to fit into the firmware image.

			ELPHEL_SOURCEDIR and TOOLCHAIN values below are installation dependent, check if it match yours.

	=First=		=First=
	~~you have to~~ source init_env from the ~~elphel~~ firmware source directory, eg:		You must source init_env from the Elphel firmware source directory, eg:
	~~source~~ /usr/local/src/elphel-cvs/353/elphel353/init_env		ELPHEL_SOURCEDIR=/usr/local/src/elphel-cvs/353/elphel353
			cd $ELPHEL_SOURCEDIR
			source init_env

	=Setting environment variables=		=Setting environment variables=

Luxigo at 16:00, 10 March 2009

2009-03-10T16:00:00Z

New page

This procedure is intended to test software before taking time to include it in the firmware build,

or to build software that would be too big to fit into the firmware image.

=First=
you have to source init_env from the elphel firmware source directory, eg:
source /usr/local/src/elphel-cvs/353/elphel353/init_env

=Setting environment variables=
(check ./configure --help and the Makefile to see if more is needed)

# toolchain
TOOLCHAIN=/usr/local/cris
export PATH=${TOOLCHAIN}/crisv32-axis-linux-gnu/bin:$PATH
export PATH=${TOOLCHAIN}/bin:$PATH

# binaries
export CC=${TOOLCHAIN}/bin/crisv32-axis-linux-gnu-gcc
export CXX=${TOOLCHAIN}/bin/crisv32-axis-linux-gnu-g++
export CPP=${TOOLCHAIN}/bin/crisv32-axis-linux-gnu-cpp

# options
export CFLAGS=-I${TOOLCHAIN}/include
export CFLAGS="${CFLAGS} -I${TOOLCHAIN}/crisv32-axis-linux-gnu/sys-include"
export CXXFLAGS=${CFLAGS}
export CPPFLAGS=${CFLAGS}
export LDFLAGS=-L${TOOLCHAIN}/lib
export LDFLAGS="${LDFLAGS} -L${TOOLCHAIN}/crisv32-axis-linux-gnu/lib/"

# user includes and libraries
export LDFLAGS="${LDFLAGS} -L/usr/local/crisv32/lib"
export CFLAGS="${CFLAGS} -I/usr/local/crisv32/include"
export CXXFLAGS=${CFLAGS}

=When the software is packaged using autoconf and automake=
You normally just have to run:
./configure --host=crisv32-axis-linux-gnu --prefix=/usr/local/crisv32 [ other options ]
make
make install

and mount or copy the resulting /usr/local/crisv32 to the camera
(you may want to strip binaries and remove documentation before)

Then to run the software on the camera you may have to define:
export PATH=/usr/local/crisv32/bin:$PATH
export LD_LIBRARY_PATH=/usr/local/crisv32/lib:$LD_LIBRARY_PATH

=When the software is not packaged using autoconf and automake=
Edit the Makefile