[prev in list] [next in list] [prev in thread] [next in thread] 

List:       orocos-dev
Subject:    [Orocos-Dev] [Bug 1019] Precedence of ROS packages over regular files when using the import function
From:       meyer () fsr ! tu-darmstadt ! de (Johannes Meyer)
Date:       2013-02-15 9:52:55
Message-ID: 20130215095255.766.qmail () web01-shared04 ! priorweb ! be
[Download RAW message or body]


http://bugs.orocos.org/show_bug.cgi?id=1019

--- Comment #3 from Johannes Meyer <meyer at fsr.tu-darmstadt.de> 2013-02-15 10:52:54 CET ---
Created attachment 853
  --> http://bugs.orocos.org/attachment.cgi?id=853
only interpret a package name as filename if it is a loadable library

I would like to propose an alternative patch for this issue, that just adds an
additional check to the ComponentLoader::import(package) function without
changing the precedence of package being interpreted as library, ROS package or
RTT package. With the patch, the package name is only loaded as library
directly if a file with the given name exists (is_regular_file) and if it has
the correct extension (isLoadableLibrary). This also solves the problem of
having executables with the same name as a package in the current working
directory. The loadInProcess() call would fail anyway if isLoadableLibrary()
return false.

I think this patch would not break existing use cases as component libraries
loaded with import("path/to/libxyz.so") in the deployer always have the correct
extension.

-- 
Configure bugmail: http://bugs.orocos.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
You are the assignee for the bug.

[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic