[Bug 1019] Precedence of ROS packages over regular files when using the import function

Peter Soetens <[email protected]>
Newsgroups gmane.science.robotics.orocos.devel
Message-ID <[email protected]>
http://bugs.orocos.org/show_bug.cgi?id=1019

Peter Soetens <[email protected]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|ASSIGNED                    |RESOLVED
         Resolution|                            |FIXED

--- Comment #4 from Peter Soetens <[email protected]> 2013-04-18 00:16:18 CEST ---
(In reply to comment #3)
> Created attachment 853 [details]
> 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.

Thanks. Pushed to toolchain-2.6.

Peter

-- 
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.
-- 
Orocos-Dev mailing list
[email protected]
http://lists.mech.kuleuven.be/mailman/listinfo/orocos-dev
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.