On Wed, Sep 16, 2009 at 18:34, <breno [..] ...> wrote:
> Hi, well I inserted by hand on application.cpf the following lines:
>
>
>  <simple name="Import"
> type="string"><value>/usr/local/lib/libusecase-automatic-gnulinux.so<value><simple>
>  <simple name="Import"
> type="string"><value>/usr/local/lib/libusecase-controller-gnulinux.so<value><simple>
>  <simple name="Import"
> type="string"><value>/usr/local/lib/libusecase-joystick-gnulinux.so<value><simple>
>  <simple name="Import"
> type="string"><value>/usr/local/lib/libusecase-modeswitch-gnulinux.so<value><simple>
>  <simple name="Import"
> type="string"><value>/usr/local/lib/libusecase-plant-gnulinux.so<value><simple>

Normally, the exercise should not be installed. It can be run from the
build directory. But installing and adding these lines works too.

>
>
> So all Errors messages has disappeared but I still have warning messages:
>
>  0.015 [ Warning][DeploymentComponent::loadComponents] Forcing priority
> (0) of thread with !SCHED_OTHER policy to 1.
> 0.016 [ Warning][DeploymentComponent::loadComponents] Forcing priority (0)
> of thread with !SCHED_OTHER policy to 1.
> 0.016 [ Warning][DeploymentComponent::loadComponents] Forcing priority (0)
> of thread with !SCHED_OTHER policy to 1.
> 0.017 [ Warning][DeploymentComponent::loadComponents] Forcing priority (0)
> of thread with !SCHED_OTHER policy to 1.
> 0.018 [ Warning][DeploymentComponent::loadComponents] Forcing priority (0)
> of thread with !SCHED_OTHER policy to 1.
> 0.019 [ Warning][SingleThread] Forcing priority (0) of thread with
> !SCHED_OTHER policy to 1.
>
>
> Is that normal?

If you run as root (sudo or su) these will go away.You can not run in
the FIFO scheduler as a normal user.

>
> I'd like to know how you handle with the installations of new releases. Do
> you leave the old ones? Create a new dir.? The libs from different
> versions are gathered on tha same place? Could you give some advice?

The libraries of multiple versions may remain in /usr/lib, but only
the headers of one version may be installed, because they all end up
in /usr/include, thus overwriting each other.
For OCL, the binaries (deployer-gnulinux,...) can only exist for one
version, because they also overwrite each other in /usr/bin.

Practically it means you can only 'develop' against a single version
(the one installed in /usr/include), but can run applications for all
versions at the same time, given that they don't need the OCL
deployer.

Peter