-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Broken on Trusty (because of ASDF 3) #17
Comments
Thanks, @gaya- I'll look into it, tonight. |
I had a look at the code, but am not 100% sure (from reading) whether split-string is actually necessary functionality for us. Right now, I don't have roslisp_repl installed on my 14.04 system. I will experiment with this on my 12.04 system with printouts on Monday morning. |
I'm further digging into this. First observations:
|
I attempted a first fix. You can find it here: airballking/roslisp@c980434 With this in place, |
The fix looks good. I like your check for ASDF version. In some slime code I have seen a compile-time version of this checks (e.g. https://github.com/slime/slime/blob/master/contrib/swank-asdf.lisp#L56), which could be even more efficient. On a more global scale, it looks like #+asdf1
(defun some-function ...)
#+asdf2
(defun some-function ...)
#+asdf3
(defun some-function ...) The thing that bothers me the most is the way roslisp works with the ASDF source registry. It uses the interface from ASDF 1 ( In addition to that, if there really is much code that actually isn't used at all on modern platforms with modern ROS versions, it would be nice to either completely get rid of it, or deprecate it, or label it with @moesenle, you seem to be the only person who has a comprehensive knowledge about what's happening in |
I tested your fix and seems to work. I have not tested more complex stuff because I don't have my projects ported to indigo yet but it looks very promising... |
Agreed! Things turned out much simpler than I expected. |
@gaya- Sure! I think a couple of days are no problem at all. |
Ok, I tested it on more complex projects, works well. I do get linkage errors from CFFI on really complex rosbuild packages but I'm pretty certain it has nothing to do with roslisp. Let's merge the fix. |
Done. @Gaya thanks for testing! |
So, I just tested roslisp on Trusty.
First of all,
ros-load-manifest
doesn't compile anymore.Reason: it uses
asdf:split-string
, which is not external in ASDF 3 anymore.The compilation error looks like this:
I took a quick look and found two occurrences of
asdf:split-string
inros_load_manifest/load-manifest.lisp
.As far as I understood, not all the functionality of
load-manifest.lisp
is actually used right now and many things are there only for backwards compatibility with really old systems. So, I'm not even sure if that particular piece of code is actually needed.Unfortunately, I won't have time to look into this until Monday night.
@airballking, FYI.
The text was updated successfully, but these errors were encountered: