TypekitPlugin.hpp File Reference

#include <string>
#include <vector>
#include "../rtt-config.h"
#include "TypekitRepository.hpp"

Go to the source code of this file.

Classes
class	RTT::types::TypekitPlugin
	This interface defines how additional typekits are loaded into Orocos. More...

Namespaces
	RTT
	Contains TaskContext, Activity, OperationCaller, Operation, Property, InputPort, OutputPort, Attribute.
	RTT::types
	Classes for typekits for describing and handling user data types.

Macros
#define	ORO_TYPEKIT_PLUGIN(TYPEKIT)
	Once you defined your TypekitPlugin or TransportPlugin class, you can use this macro to make it available as a plugin. More...

Macro Definition Documentation

#define ORO_TYPEKIT_PLUGIN

(

TYPEKIT

)

Value:

namespace RTT { class TaskContext; } \
    extern "C" {                      \
        RTT_EXPORT bool loadRTTPlugin(RTT::TaskContext* tc); \
        bool loadRTTPlugin(RTT::TaskContext* tc) { \
            if (tc == 0) { \
                RTT::types::TypekitRepository::Import( new TYPEKIT() ); \
                return true; \
            } \
            return false; \
        } \
        RTT_EXPORT std::string getRTTPluginName(); \
        std::string getRTTPluginName() { \
        TYPEKIT tk; \
        return tk.getName(); \
        } \
        RTT_EXPORT std::string getRTTTargetName(); \
        std::string getRTTTargetName() { \
            return OROCOS_TARGET_NAME; \
        } \
    }

Once you defined your TypekitPlugin or TransportPlugin class, you can use this macro to make it available as a plugin.

Note

Do not use this macro inside a namespace ! For example: ORO_TYPEKIT_PLUGIN ( KDL::KDLTypekit ) where KDL::KDLTypekit is a classname, derived from RTT::types::TypekitPlugin or RTT::types::TransportPlugin

Definition at line 127 of file TypekitPlugin.hpp.

Referenced by RTT::mqueue::MQLibPlugin::getName(), RTT::corba::CorbaLibPlugin::getName(), and RTT::types::RealTimeTypekitPlugin::getName().