Re: Addition of .ASD to cvs tree
Raymond Toy <[email protected]> Tue, 04 Jan 2005 09:52:52 -0500
| Newsgroups | gmane.lisp.matlisp.user |
|---|---|
| Message-ID | <[email protected]> |
>>>>> "Robert" == Robert Sedgewick <[email protected]> writes: Robert> 1. (*) text/plain ( ) text/html Robert> On Dec 22, 2004, at 9:21 AM, Raymond Toy wrote: >>>>>>> "Denis" == Denis Bueno <[email protected]> writes: >> Denis> Could a committer add the following, matlisp.asd, to the >> cvs tree? Denis> It's quite convenient to use. >> >> Is there something that this asd file does that mk-defsys doesn't do? >> I'm not really keen on maintaining two defsystems for matlisp. Robert> Well, the asd file takes care of compiling the fortran sources, while Robert> the mk-defsys solution needs a makefile for that. Also, asdf is Robert> integrated with slime (I don't think mk-defsys is). For the asd file to work properly, I think it needs to be generated from configure so that the right options are given to the Fortran compiler. At one point mk-defsys file could also compile the Fortran sources, but I don't know if I ever committed the changes or if it even works anymore. If one of you wants to maintain the asd file, then I can commmit it. But you'll have to make it so that it's either created by configure or you punt and have a makefile build the Fortran sources. Ray ------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt