Local and remote modules

There are two ways to compile a module:

  • As an executable (remote module): each module package creates an independent executable stored in "/path/to/aldebaran-sdk/bin/". At startup you need to specify the IP and port of the running NAOqi.

    $~ cd /path/to/aldebaran-sdk/bin/ $~ ./my-module --pip <IP> --pport <PORT>

  • As a library: each module package creates a dynamic library stored in "/path/to/aldebaran-sdk/lib/naoqi/" (next to the other modules).
  • To make the mainBroker load your module at startup, the autoload.ini file (in /path/to/aldebaran-sdk/preferences/) needs to be updated with the base name of your project. If your module is compiled as a shared library put it in the [extra] section, else add a [remote] section an put your module beneath. Your executable will be launched by NAOqi at startup.

You can choose if your module is going to be executable or remote by configuring a CMake variable named MY_MODULE_IS_REMOTE. This variable should appear in the CMake Gui.





Copyright © 2010 Aldebaran-Robotics - All rights reserved