In 3.2.X you could disable the player plugin build during the ccmake stage by changing the BUILD_PLAYER_PLUGIN variable to OFF.
I am sure 4.0.X would also have the same option.

About writing stage controllers, studying examples/ctrl/wander.cc and examples/ctrl/wander_pioneer.cc had helped me very much.


On 17 October 2011 22:27, Richard Vaughan <vaughan@sfu.ca> wrote:
On Mon, Oct 17, 2011 at 9:52 AM, Arkapravo Bhaumik
<arkapravobhaumik@gmail.com> wrote:
> Hello Prof. Vaughan, Rich
> Had 2 questions, any help would be most welcome;
> How can I design a Stage Controller (viz. wander, fasr etc) ? I guess that
> it will not be an easy job - is there a tutorial ?

You have the source code for them, in <stage>/examples/ctrl/  - read the code.

See also a minimal example in my paper about Stage in the Journal of
Swarm Intelligence.

> I have worked with Stage 3.2.X and for installation Player had to be
> installed prior to commencing the Stage installation as the Stage
> installation script used to 'look for' the player. Is Stage 4.X.X a
> standalone installation - can be installed all by itself, no need of Player

Stage only needs Player preinstalled if you want to use Player/Stage.
If you want Stage by itself, there is no need for Player. The cmake
script will look for it, report that it is not found, and carry on
happily building Stage.

- rtv

> Kind regards
> Arkapravo
> --
> Arkapravo Bhaumik
> E-mail : arkapravobhaumik@gmail.com
> Blogs : http://mobotica.blogspot.com/, http://3chevrons.blogspot.com/
> Twitter : @abhaumik
> Facebook : arkapravo@facebook.com
> Skype : arkapravo

All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
Playerstage-users mailing list