RobotWereld/README at master · MustafaSabur/RobotWereld · GitHub

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126


Note: 	- "\" means that the actual command line continues with the next line!
		- All command sequences start from the root of the project, $ROBOTWORLD_ROOT in the examples
		- The exact name of the platform compilation directories are irrelevant but using mingw(native/cross), linux or mac is advised.
		- Adjust all paths to taste
		- Adjust for any Boost and wxWidgets versions
		- On Windows, use a MinGW MSys command shell, *NOT* a Windows cmd shell.
		- Use an "Empty Makefile" project as project template for Eclipse and change the build directory
		  to the platform compilation directory in the project settings
		- If the configure script is missing or out of sync with the installed MSys files, run the following commands in the root of the project (or use the autogen.sh script):
			libtoolize --force --copy
			aclocal -I ./m4
			autoconf -I ./m4
			automake --force-missing --copy --add-missing --foreign


1. Compilation

*** Compilation on Linux ***

On Linux, compiling for Linux if both wxWidgets and Boost are *installed* in the OS in their *default* location,
the configure script finds Boost and wxWidgets automatically:

	cd $ROBOTWORLD_ROOT
	mkdir linux
	cd linux
	../configure
	make

On Linux, compiling for Linux if both wxWidgets and Boost are *installed* in the OS in a *non-default* location,
the configure script must be told where to find Boost and wxWidgets:

	cd $ROBOTWORLD_ROOT
	mkdir linux
	cd linux
	../configure --with-wx-config=/home/jkr/devlib/wxWidgets-3.0.2/bin/wx-config --with-boost=/home/jkr/devlib/boost_1_56_0
	make

NB: 1. adjust the paths to taste
	2. The BOOST_ROOT path should point at the root directory of an installed Boost, having the following structure:
		\include
			\boost-1_56
				\boost (contains headers, e.g. version.hpp,  and the sub-directories of the libraries)
		\lib (contains the libraries)
	3. The --with-wx-config path should point to the wx-config file in the installation directory of wxWidgets


On Linux, compiling for Linux if both wxWidgets and Boost are compiled but *NOT installed* (e.g. development versions of wxWidgets and Boost is staged),
the configure script must be told where to find Boost and wxWidgets:

	cd $ROBOTWORLD_ROOT
	mkdir linux
	cd linux
	export BOOST_ROOT=/home/jkr/src/boost_1_56_0
	../configure 	--with-wx-config=/home/jkr/src/wxWidgets-3.0.2/linux/wx-config	\
					--with-boost
	make


NB: 1. adjust the paths to taste
	2. The BOOST_ROOT path should point at the root directory of a "staged" boost, i.e. with a "staged" directory in it.
	3. The --with-wx-config path should point to the wx-config file in the bin directory of the installation directory of wxWidgets


On Linux, cross compile to Windows with wxWidgets and Boost *installed* in the given directories,
the configure script must be told where to find Boost and wxWidgets and the cross compiler to use:

	cd $ROBOTWORLD_ROOT
	mkdir mingwcross
	cd mingwcross
	../configure 	--host=i686-w64-mingw32	\
					--with-boost=/home/jkr/mingw/boost	\
					--with-wx-config=/home/jkr/mingw/wxwidgets/bin/wx-config
	make

NB: 1. this assumes a fully installed and working i686-w64-mingw32 compiler in the path,
	2. adjust the paths to taste.
	3. adjust the host to taste, according to the mingw cross compiler.

*** Compilation on Windows ***

On Windows, compiling for Windows if both wxWidgets and Boost are *installed* in the OS in their *default* location,
the configure script finds Boost and wxWidgets automatically, using the MinGW command prompt:

	cd $ROBOTWORLD_ROOT
	mkdir mingwnative
	cd mingwnative
	../configure
	make

On Windows, compiling for Windows if both wxWidgets and Boost are *installed* in a *non-default* location,
using the MinGW command prompt:

	cd $ROBOTWORLD_ROOT
	cd mingwnative
		../configure 	--with-wx-config=/drive/path/to/root/of/wxWidgets/bin/wx-config	\
						--with-boost=/drive/path/to/root/of/boost
	make

NB: 1. adjust the paths to taste
	2. The BOOST_ROOT path should point at the root directory of an installed Boost, having the following structure:
		\include
			\boost-1_56
				\boost (contains headers, e.g. version.hpp,  and the sub-directories of the libraries)
		\lib (contains the libraries)
	3. The --with-wx-config path should point to the wx-config file in the bin directory of the installation directory of wxWidgets


On Windows, compiling for Windows if both wxWidgets and Boost are compiled but *NOT installed* (e.g. development versions of wxWidgets and Boost is staged),
the configure script must be told where to find Boost and wxWidgets, using the MinGW command prompt:

	cd $ROBOTWORLD_ROOT
	cd mingwnative
	export BOOST_ROOT=/d/src/boost_1_56_0
	../configure 	--with-wx-config=/d/src/wxWidgets-3.0.2/mingw/wx-config	\
					--with-boost
	make

NB: 1. This assumes a working fully installed gcc compiler in the path.
	2. adjust the paths to taste
	3. The BOOST_ROOT path should point at the root directory of a "staged" boost, i.e. with a "staged" directory in it.
	4. The --with-wx-config path should point to the wx-config file in the compilation directory of wxWidgets