| To: | scsh hackers <scsh-hackers@lists.sourceforge.net> |
|---|---|
| Subject: | [Scsh-hackers] "precompiled" libraries |
| From: | bernauer@informatik.uni-tuebingen.de |
| Date: | Fri Nov 14 13:32:05 2003 |
| List-id: | Discussion among the implementors <scsh-hackers.lists.sourceforge.net> |
| Mail-followup-to: | scsh hackers <scsh-hackers@lists.sourceforge.net> |
| Sender: | scsh-hackers-admin@lists.sourceforge.net |
Hi, as we discuss the packaging of libraries, I remembered a feature about libraries that I would like to have besides of having it installed in a structured way. I am not sure, if this issue has been discussed earlier: I'd like to have the possibility of "precompiled" libraries. I don't understand why scsh has to read in and interpret the source file of a library file every time I start a script. E.g. I have never changed the srfi-files and I'll probably never do it. Is there a way to avoid this I am not aware of or is there any effort going into this direction? Can this be incorporated into the library installation procedure somehow? Thank you for your input. Andreas.
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [Scsh-hackers] Library to ease package installation, bernauer |
|---|---|
| Next by Date: | Re: [Scsh-hackers] Library to ease package installation, Anthony Carrico |
| Previous by Thread: | [Scsh-hackers] Library to ease package installation, Michel Schinz |
| Next by Thread: | Re: [Scsh-hackers] "precompiled" libraries, Anthony Carrico |
| Indexes: | [Date] [Thread] [Top] [All Lists] |