Re: [CM] quicklisp clm
Any chance of changing the asd? The ccrma-ftp clm-5 tarball now has Tito's asdf code. The original clm.asd was apparently written by Rick 10 years ago. ___ Cmdist mailing list Cmdist@ccrma.stanford.edu https://cm-mail.stanford.edu/mailman/listinfo/cmdist
Re: [CM] quicklisp clm
> > If a minimalist approach is good for you, it is quicklispable :) > > (asdf:defsystem "clm" > :description "Common Lisp Music" > :version "3" > :author "William Schottstaedt " > :licence "LLGPL" > :perform (compile-op (o c) > (load (system-relative-pathname "clm" "all.lisp" Yes indeed! (Though it won’t load on lispworks.) Any chance of changing the asd? best, jc ___ Cmdist mailing list Cmdist@ccrma.stanford.edu https://cm-mail.stanford.edu/mailman/listinfo/cmdist
Re: [CM] quicklisp clm
> If a minimalist approach is good for you, it is quicklispable :) > > (asdf:defsystem "clm" > :description "Common Lisp Music" > :version "3" > :author "William Schottstaedt " > :licence "LLGPL" > :perform (compile-op (o c) > (load (system-relative-pathname "clm" "all.lisp" Yes indeed! (Though it won’t load on lispworks.) Any chance of changing the asd? best, jc___ Cmdist mailing list Cmdist@ccrma.stanford.edu https://cm-mail.stanford.edu/mailman/listinfo/cmdist
Re: [CM] quicklisp clm
On Tue, Dec 13, 2016 at 08:40:06PM -0600, Juan Cristobal Cerrillo wrote: > > > On Dec 10, 2016, at 7:22 AM, b...@ccrma.stanford.edu wrote: > > > > ok -- that's fine by me, but I am no longer interested > > in the CL part of that package. I haven't worked on it > > in about 20 years, and no longer have the time or > > energy to provide support -- users of it are on their own. > > Good luck. > > > > Thank you for your reply Bill. > > ¿Is anyone else is interested in collaborating on achieving a quicklisp > loadable cl-clm? > All that is required is separating the different parts of all.lisp so that it > is loadable with asdf:load-system. > I???ve managed to test my ???port??? successfully in ccl, sbcl and lispworks > on osx. > (though I would gladly accept any suggestions/advice that would make it > clearer/better) > > Once this is achieved, the changes could be easily incorporated into the > official distribution (and then available through quicklisp). > > I think it would be wonderful if clm was installable through quicklisp, not > least for historical reasons! If a minimalist approach is good for you, it is quicklispable :) (asdf:defsystem "clm" :description "Common Lisp Music" :version "3" :author "William Schottstaedt " :licence "LLGPL" :perform (compile-op (o c) (load (system-relative-pathname "clm" "all.lisp" ___ Cmdist mailing list Cmdist@ccrma.stanford.edu https://cm-mail.stanford.edu/mailman/listinfo/cmdist
Re: [CM] quicklisp clm
Hi Juan, if you need help, I can offer to test on linux, although Ralf Mattes would obviously be a better choice than me. For quite some time I have been very interested in getting all these great tools quicklisp-loadable and make them cooperate in a more up-to-date environment. -- Orm Am Dienstag, den 13. Dezember 2016 um 20:40:06 Uhr (-0600) schrieb Juan Cristobal Cerrillo: > > > On Dec 10, 2016, at 7:22 AM, b...@ccrma.stanford.edu wrote: > > > > ok -- that's fine by me, but I am no longer interested > > in the CL part of that package. I haven't worked on it > > in about 20 years, and no longer have the time or > > energy to provide support -- users of it are on their own. > > Good luck. > > > > Thank you for your reply Bill. > > ¿Is anyone else is interested in collaborating on achieving a quicklisp > loadable cl-clm? > All that is required is separating the different parts of all.lisp so that it > is loadable with asdf:load-system. > I’ve managed to test my “port” successfully in ccl, sbcl and lispworks on osx. > (though I would gladly accept any suggestions/advice that would make it > clearer/better) > > Once this is achieved, the changes could be easily incorporated into the > official distribution (and then available through quicklisp). > > I think it would be wonderful if clm was installable through quicklisp, not > least for historical reasons! > > all best, > > jc > ___ > Cmdist mailing list > Cmdist@ccrma.stanford.edu > https://cm-mail.stanford.edu/mailman/listinfo/cmdist ___ Cmdist mailing list Cmdist@ccrma.stanford.edu https://cm-mail.stanford.edu/mailman/listinfo/cmdist
Re: [CM] quicklisp clm
> On Dec 10, 2016, at 7:22 AM, b...@ccrma.stanford.edu wrote: > > ok -- that's fine by me, but I am no longer interested > in the CL part of that package. I haven't worked on it > in about 20 years, and no longer have the time or > energy to provide support -- users of it are on their own. > Good luck. > Thank you for your reply Bill. ¿Is anyone else is interested in collaborating on achieving a quicklisp loadable cl-clm? All that is required is separating the different parts of all.lisp so that it is loadable with asdf:load-system. I’ve managed to test my “port” successfully in ccl, sbcl and lispworks on osx. (though I would gladly accept any suggestions/advice that would make it clearer/better) Once this is achieved, the changes could be easily incorporated into the official distribution (and then available through quicklisp). I think it would be wonderful if clm was installable through quicklisp, not least for historical reasons! all best, jc ___ Cmdist mailing list Cmdist@ccrma.stanford.edu https://cm-mail.stanford.edu/mailman/listinfo/cmdist
Re: [CM] quicklisp clm
On Mon, Dec 12, 2016 at 09:27:12AM -0600, Juan Cristobal Cerrillo wrote: > Per Ralf’s suggestions I’ve made some changes. > The asd file now includes a quicklisp directive and includes the original > asdf:defsystem as well. > > I’ve changed the way in that clm-directory was set, removing the > concatenating to my invented clm directory and using ql:where-is-system, agin > with a directive. This allows for correct c compiling without having to copy > any files to the asdf compile directory. Hmm, I think it's time to think about the goals of the port. Since Quicklisp depends on ASDF you might declare that you only support Lisp with ASDF-support. Once this decision is made, dir-setup.lisp can be reduced to: (defparameter *clm-src-dir* (asdf:component-pathname (asdf:find-system :clm)) "Directory holding CLM source files") (defparameter clm-directory *clm-src-dir*) (defparameter clm-bin-directory *clm-src-dir*) > If quicklisp is not detected, all should work as it did originally with asdf. In general, quicklisp should not show up in any of the files, it's only a system to distribute code and manage code dependencies. ASDF is all you need. Once ASDF works Quicklisp works as well. As a side note, I'm always a bit queazy having build parameters in the global namespace. Why not put "package.lisp" on the first palce in the list of components in "clm.asd". Then you could move "dir-setup.lisp" et al. into the CLM package. Cheers, RalfD ___ Cmdist mailing list Cmdist@ccrma.stanford.edu https://cm-mail.stanford.edu/mailman/listinfo/cmdist
Re: [CM] quicklisp clm
Per Ralf’s suggestions I’ve made some changes. The asd file now includes a quicklisp directive and includes the original asdf:defsystem as well. I’ve changed the way in that clm-directory was set, removing the concatenating to my invented clm directory and using ql:where-is-system, agin with a directive. This allows for correct c compiling without having to copy any files to the asdf compile directory. If quicklisp is not detected, all should work as it did originally with asdf. I am now able to load CLM with asdf:load-system, and quicklisp, in CCL and SBCL. Best, jc > On Dec 11, 2016, at 1:41 PM, Ralf Mattes wrote: > > On Sun, Dec 11, 2016 at 06:16:21PM +0100, anders.vin...@nmh.no wrote: >>> "R" == Ralf Mattes writes: Good luck. >> >>R> Looking at the state of the code I think that's really needed. >> >> I use the CL version of CLM from time to time, using sbcl and lw, and i >> beleive some others also use CL/CLM at times. What is it with the state >> of the code you find problematic? > > Just as a quick reply, not neccessarily in order of importance (and > _not_ meant as a critique): > > - a rather baroque way to build/install (that makes distribution via > quicklisp rather unölikely). > - build-customization via *features* (again, not really working for > Quicklisp) > - implementation specific loading of libraries (there's no real need to > maintain a list of *shared-object-extension* any more. Delegate all > of this to cffi). In general, a lot of the code could be factored out > to "general" libraries provided by Quicklisp (btw, the same is true > for CM as well). > - That extra strange mixture of autoconf and (c source) compilation > from lisp. I was trying to load CLM from the git repository but > compilation of the library failed (missing symbols). With a proper > makefile I would have been able to start to compile outside of lisp > and debug the build. > > Now, non of this is impossible or even hard to fix, but it needs to be > done and it's quite some work. I'm glad to see people work on that code, > but, in my very humble, personal and probably grummpy opinion, it needs > to be done by systematically cleaning up the code and not by adding > another layer of fixups - that only makes the system even more brittle. > Just one quick example: dir-setup.lisp uses > quicklisp:*local-project-directories* and concatenates it with a string > "/clm". Hmm, now we've lost the possibility to load CLM from asdf. And > we can't install it with Quicklisp either (iff it's picked up by > quicklisp at some point in the future). There's fine support to find the > source code location in ASDF/UIOP. Why not use that? > And don't assume quicklisp directories are writeable ... ;-) > I hope I've made my poit clear. I did not intend to lessen anyones > valuable work. > > Cheers, Ralf Mattes > > > > > > - >> -anders >> >> ___ >> Cmdist mailing list >> Cmdist@ccrma.stanford.edu >> https://cm-mail.stanford.edu/mailman/listinfo/cmdist >> > ___ > Cmdist mailing list > Cmdist@ccrma.stanford.edu > https://cm-mail.stanford.edu/mailman/listinfo/cmdist ___ Cmdist mailing list Cmdist@ccrma.stanford.edu https://cm-mail.stanford.edu/mailman/listinfo/cmdist
Re: [CM] quicklisp clm
On Sat, Dec 10, 2016 at 05:22:03AM -0800, b...@ccrma.stanford.edu wrote: > ok -- that's fine by me, but I am no longer interested > in the CL part of that package. I haven't worked on it > in about 20 years, and no longer have the time or > energy to provide support -- users of it are on their own. > Good luck. So, would you prefer that the package's maintainer email is changed? Who would be willing to step up? Cheers, RalfD > ___ > Cmdist mailing list > Cmdist@ccrma.stanford.edu > https://cm-mail.stanford.edu/mailman/listinfo/cmdist > ___ Cmdist mailing list Cmdist@ccrma.stanford.edu https://cm-mail.stanford.edu/mailman/listinfo/cmdist
Re: [CM] quicklisp clm
On Sat, Dec 10, 2016 at 12:27:22AM -0600, Juan Cristobal Cerrillo wrote: > https://github.com/jccerrillo/clm Do you want feedback here on the list or via issues/pull requests on Github? Cheers, Ralf Mattes > > On Dec 10, 2016, at 12:26 AM, Juan Cristobal Cerrillo > > wrote: > > > > Hello, > > > > I’ve made a quicklisp-loadable version of clm-5. > > For the moment it only loads on ClozureCL, but it shouldn’t be that > > difficult to get it working on sbcl at least. > > Hope some find this useful… > > > > all best, > > > > juan cristóbal > > ___ > > Cmdist mailing list > > Cmdist@ccrma.stanford.edu > > https://cm-mail.stanford.edu/mailman/listinfo/cmdist > > > ___ > Cmdist mailing list > Cmdist@ccrma.stanford.edu > https://cm-mail.stanford.edu/mailman/listinfo/cmdist ___ Cmdist mailing list Cmdist@ccrma.stanford.edu https://cm-mail.stanford.edu/mailman/listinfo/cmdist
Re: [CM] quicklisp clm
On Sun, Dec 11, 2016 at 06:16:21PM +0100, anders.vin...@nmh.no wrote: > > "R" == Ralf Mattes writes: > >> Good luck. > > R> Looking at the state of the code I think that's really needed. > > I use the CL version of CLM from time to time, using sbcl and lw, and i > beleive some others also use CL/CLM at times. What is it with the state > of the code you find problematic? Just as a quick reply, not neccessarily in order of importance (and _not_ meant as a critique): - a rather baroque way to build/install (that makes distribution via quicklisp rather unölikely). - build-customization via *features* (again, not really working for Quicklisp) - implementation specific loading of libraries (there's no real need to maintain a list of *shared-object-extension* any more. Delegate all of this to cffi). In general, a lot of the code could be factored out to "general" libraries provided by Quicklisp (btw, the same is true for CM as well). - That extra strange mixture of autoconf and (c source) compilation from lisp. I was trying to load CLM from the git repository but compilation of the library failed (missing symbols). With a proper makefile I would have been able to start to compile outside of lisp and debug the build. Now, non of this is impossible or even hard to fix, but it needs to be done and it's quite some work. I'm glad to see people work on that code, but, in my very humble, personal and probably grummpy opinion, it needs to be done by systematically cleaning up the code and not by adding another layer of fixups - that only makes the system even more brittle. Just one quick example: dir-setup.lisp uses quicklisp:*local-project-directories* and concatenates it with a string "/clm". Hmm, now we've lost the possibility to load CLM from asdf. And we can't install it with Quicklisp either (iff it's picked up by quicklisp at some point in the future). There's fine support to find the source code location in ASDF/UIOP. Why not use that? And don't assume quicklisp directories are writeable ... ;-) I hope I've made my poit clear. I did not intend to lessen anyones valuable work. Cheers, Ralf Mattes - > -anders > > ___ > Cmdist mailing list > Cmdist@ccrma.stanford.edu > https://cm-mail.stanford.edu/mailman/listinfo/cmdist > ___ Cmdist mailing list Cmdist@ccrma.stanford.edu https://cm-mail.stanford.edu/mailman/listinfo/cmdist
Re: [CM] quicklisp clm
> "R" == Ralf Mattes writes: >> Good luck. R> Looking at the state of the code I think that's really needed. I use the CL version of CLM from time to time, using sbcl and lw, and i beleive some others also use CL/CLM at times. What is it with the state of the code you find problematic? -anders ___ Cmdist mailing list Cmdist@ccrma.stanford.edu https://cm-mail.stanford.edu/mailman/listinfo/cmdist
Re: [CM] quicklisp clm
On Sat, Dec 10, 2016 at 05:22:03AM -0800, b...@ccrma.stanford.edu wrote: > ok -- that's fine by me, but I am no longer interested > in the CL part of that package. I haven't worked on it > in about 20 years, and no longer have the time or > energy to provide support -- users of it are on their own. Thank's for that clear statement. Just one question: was clm's source code maintained in a soure/revision control system? It would be nice to have the version history of the code and import it into git. > Good luck. Looking at the state of the code I think that's really needed. Cheers, Ralf Mattes > > ___ > Cmdist mailing list > Cmdist@ccrma.stanford.edu > https://cm-mail.stanford.edu/mailman/listinfo/cmdist > ___ Cmdist mailing list Cmdist@ccrma.stanford.edu https://cm-mail.stanford.edu/mailman/listinfo/cmdist
Re: [CM] quicklisp clm
ok -- that's fine by me, but I am no longer interested in the CL part of that package. I haven't worked on it in about 20 years, and no longer have the time or energy to provide support -- users of it are on their own. Good luck. ___ Cmdist mailing list Cmdist@ccrma.stanford.edu https://cm-mail.stanford.edu/mailman/listinfo/cmdist
Re: [CM] quicklisp clm
https://github.com/jccerrillo/clm > On Dec 10, 2016, at 12:26 AM, Juan Cristobal Cerrillo > wrote: > > Hello, > > I’ve made a quicklisp-loadable version of clm-5. > For the moment it only loads on ClozureCL, but it shouldn’t be that difficult > to get it working on sbcl at least. > Hope some find this useful… > > all best, > > juan cristóbal > ___ > Cmdist mailing list > Cmdist@ccrma.stanford.edu > https://cm-mail.stanford.edu/mailman/listinfo/cmdist ___ Cmdist mailing list Cmdist@ccrma.stanford.edu https://cm-mail.stanford.edu/mailman/listinfo/cmdist
[CM] quicklisp clm
Hello, I’ve made a quicklisp-loadable version of clm-5. For the moment it only loads on ClozureCL, but it shouldn’t be that difficult to get it working on sbcl at least. Hope some find this useful… all best, juan cristóbal ___ Cmdist mailing list Cmdist@ccrma.stanford.edu https://cm-mail.stanford.edu/mailman/listinfo/cmdist
