On Oct 13, 2010, at 10:57 , Peter Soetens wrote:

> On Wednesday 13 October 2010 14:52:05 Stephen Roderick wrote:
>> On Oct 13, 2010, at 08:47 , Peter Soetens wrote:
>>> On Wednesday 13 October 2010 14:29:56 S Roderick wrote:
>>>> On Oct 12, 2010, at 08:51 , Peter Soetens wrote:
>>>>> On Monday 11 October 2010 10:43:38 Charles Lesire-Cabaniols wrote:
>>>>>> On 07/10/2010 16:54, Peter Soetens wrote:
>>>>>>> * Plugin and component loading are now identical as in 2.x, which
>>>>>>> means,
>>>>>>>
>>>>>>> - support for dynamic applications on Windows
>>>>>>> - support for locating and loading toolkits
>>>>>>> - support for the RTT_COMPONENT_PATH environment variable
>>>>>>
>>>>>> I have just installed RTT and OCL 1.12 and I am facing some disturbing
>>>>>> effect with the RTT_COMPONENT_PATH variable and the Deployer's
>>>>>> 'import' method.
>>>>>> While starting, the deployer correctly looks for the libraries located
>>>>>> in the RTT_COMPONENT_PATH and types/plugins subdirectories.
>>>>>>
>>>>>> When I use the 'import' method to import a specific path, it follows
>>>>>> the same logic:
>>>>>> - libraries in the root of my_path can contain only components
>>>>>> - libraries containing toolkits must be in types/
>>>>>>
>>>>>> I have not found any way to import a library containing a toolkit that
>>>>>> is not in a 'types/' directory...
>>>>>
>>>>> This is not supported for a reason. The RTT does different things for
>>>>> typekits, plugins/services and components. It uses the directory
>>>>> structure to know what it's loading. Your only solution is to make a
>>>>> symlink from a types/libfoo.so subdirectory to your typekit library or
>>>>> install your typekit in the types/ directory.
>>>>
>>>> RTT v1.12 doesn't seem to load components from dynamic libaries linked
>>>> to an executable, nor from components that are part of an executable.
>>>> This worked in v1.10. Do you have to do anything programmatically to
>>>> load components from dynamic libraries linked with executable?
>>>>
>>>> Demonstrated on gnulinux
>>>
>>> I think it's a backporting problem in the Deployer. The
>>> DeploymentComponent is not looking at the RTT_COMPONENT_PATH. Could you
>>> do a configure() on the deployer and then see if the components are
>>> picked up ?
>>>
>>> Peter
>>
>> negative
>
> This RTT_COMPONENT_PATH = /opt/sw/orocos/v1-next-logging/install/lib
> is wrong ! It should have been
> RTT_COMPONENT_PATH = /opt/sw/orocos/v1-next-logging/install/lib/orocos
>
> Peter

Sorry about that. I actually went to look it up on the RTT website/wiki, but it's been down all morning for me.

I'll try again with the above when I get home.
S