# sharplispers/cormanlisp

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.

# Corman Lisp 3.1 has been released! #41

Open
opened this Issue Dec 30, 2018 · 18 comments

Projects
None yet
6 participants
Member

### arbv commented Dec 30, 2018 • edited

 As it was announced earlier, Corman Lisp 3.1 has been released! The release can be found in the project's download section alongside the release notes. Compared to the last release candidate it contains the following changes: important installer fixes and optimisations; documentation updates; new logo. Happy New Year!

Closed

### phoe commented Dec 30, 2018

 Is it possible to release the binaries in a .zip version without a MSI installer?
Member

### arbv commented Dec 30, 2018

 Shameless plug. My personal notes about the release.
Member

### arbv commented Dec 30, 2018

 @phoe Thank you for your interest in Corman Lisp! The official releases are distributed as MSI installers. You can manually unpack the MSI without installing it. Example: msiexec /a CormanLisp-3.1.2.msi /qb TARGETDIR=full\path\to\directory
Member

### arbv commented Dec 30, 2018 • edited

 @phoe As Corman Lisp includes some components which carry the different licensing terms, I believe it is better to distribute it in the form of an installer which shows a user all the necessary licensing terms during the installation process.

### phoe commented Dec 30, 2018

 @arbv I have just tried running Corman Common Lisp under Wine in Linux, running the MSI installer using Wine's msiexec implementation, and the resulting executable seems to be a 16-bit one: └─▪ file CormanLisp.exe CormanLisp.exe: MS-DOS executable, MZ for MS-DOS  Is this intended?
Member

### arbv commented Dec 30, 2018 • edited

 @phoe CormanLisp.exe is a 32-bit application. Every Windows executable file contains 16-bit MS-DOS stub at the beginning which prints "This program can not be run in DOS mode." if one tries to run the executable from DOS. The file utility reports incomplete information.

### ninejaguar commented Dec 30, 2018

 Thank you all for your hard work! I'll be referring Windows users new to Common Lisp to this implementation to get started with.

Member

### arbv commented Dec 30, 2018

 @phoe @ninejaguar, fair points. I have provided the ZIP archive as a fallback option.

### ninejaguar commented Dec 30, 2018

 @phoe @ninejaguar, fair points. I have provided the ZIP archive as a fallback option. Thank you!

### cameyo42 commented Dec 31, 2018

 Thanks for your hard work !!! Happy New Year
Member

### luismbo commented Dec 31, 2018

 Congrats to @arbv and the rest of the team. 🎉

### alandipert commented Jan 1, 2019 • edited

 Thank you, I downloaded and installed on Windows 10 and have had fun playing around with it! Update: I was able to make a standalone application with (save-application "life.exe" #'life-gui :static t) I did run into a problem with SAVE-APPLICATION, but I'm not sure if it's broken or if I'm just doing it wrong. Loaded life-gui.lisp example (defun main () (threads:create-thread #'life-gui)) (save-application "life.exe" #'main) When I execute life.exe in C:\Users\aland\Documents\Corman Lisp\life.exe this happens:
Member

### arbv commented Jan 2, 2019

 @alandipert I am glad you have resolved the issue manually. It seems you have installed Corman Lisp without adding it to Path (or used the ZIP archive instead of the installer). In general, you want to use SAVE-APPLICATION with :static t most of the time. Otherwise, you need to distribute CormanLispServer.dll alongside your application.

### alandipert commented Jan 2, 2019

 @arbv cool, makes sense, thank you. FWIW I did use the installer and didn't change any options.
Member

### arbv commented Jan 2, 2019

 @alandipert I need to post some clarifications. I have looked into the code. The applications which depend on the CormanLispServer.dll specifically look for the library in the same directory where they are located. It actually makes sense, as it helps to avoid possible conflicts when multiple CormanLispServer.dll versions are available in 'Path'.
Member

### arbv commented Jan 2, 2019

 I have updated the release to include the fixes for two small, yet annoying issues (#45, #48). These are small to make a new release but could annoy new users.
Member

### arbv commented Jan 2, 2019 • edited

 I have updated the release once again to include the fixes for Y-OR-N-P and YES-OR-NO-P (#48) because their wrong behaviour might be very annoying as well, especially for newbies trying to write an interactive program. Hopefully, that's all for this round. The all subsequent fixes will go into the next maintenance release. Sorry for the inconvenience.
to join this conversation on GitHub. Already have an account? Sign in to comment