Changes between Version 12 and Version 13 of ALOELinuxGuide

Timestamp:

03/10/10 19:16:45 (16 years ago)

Author:

ismael (IP: 81.184.189.15)

Comment:

--

ALOELinuxGuide

@@ -19 +19 @@
    * swman_apps: Application descriptions.
 
-'''NOTE''': Make sure that swman_execs/linux contains (or links to) your waveform binaries compiled for linux. Distributed objects are configured to be installed at /usr/local/bin, therefore, swman_execs/linux should link to that path.
+'''NOTE''': Make sure that platform directories under swman_execs contains (or links to) your waveform binaries compiled for linux. If compile from the host machine, objects are installed in /usr/local/bin, therefore, platform's executables directories should point there, i.e.:
+   * swman_execs/linux --> /usr/local/bin
+   * swman_execs/linux_64 --> /usr/local/bin
+   * swman_execs/linux_arm --> /usr/local/bin
+
+Otherwise, if you do cross-compiling, each directory should link to the binaries for the target architecture, see ALOELinuxGuide#CrossCompilation
+
 
 ALOE Linux needs to access this repository. Path can be selected permanently in a configuration file or as an argument in the launcher. By default, it is defined in a configuration file and points to 'example-repository/', relative to the current directory. Therefore, ALOE can be launched from the downloaded source directory by simply typing: 
@@ -205 +211 @@
  * '''Increase Kernel time resolution'''. Another measure you can adopt to achieve a higher performance is increasing the kernel timer frequency. To do so, you must recompile your kernel. How to do that is out of the scope of this document, however, if you use ''menuconfig'', the option you have to change is at '''Processor type and features->Timer frecuency''' (CONFIG_HZ). Setting that to 1000 Hz implies a resolution of 1ms which, with at 10ms slot duration should be enough.
 
+== Cross Compilation ==
+
+In a multi-processor environment where node processors have different architecture than manager, you should either perform cross-compilation from the manager host or copy the binaries from the target machine. To perform cross-compilation you should first obtain a tool-chain for the desired target. For example, to compile for the Marvell's ARM processor with the gnueabi tool-chain, run ./configure with the following arguments:
+
+{{{
+ac_cv_func_malloc_0_nonnull=yes ./configure --host=arm-none-linux-gnueabi CFLAGS='-march=armv5te' --prefix=/usr/local/arm/
+}}}
+
+'''NOTE''': Pay attention to the prefix argument. Here you should specify a different directory for every target architecture. Object binaries will be installed there, and that should be the directory where the swman_execs/linux_arm links to, in this case, make sure:
+  * swman_execs/linux_arm --> /usr/local/arm/bin
+
+Then you can just recompile your sources and install, do:
+
+{{{
+make clean
+make
+sudo make install
+}}}
+
+
+
+
 
 [[BR]]