You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have no experience with running Lisp implementations on Windows and do not have access to a windows machine, so the result would be hard to test. But I am very supportive of the idea.
According to you, what are the basic requirements of such a software that would make a minimal example interesting?
To get started I would see something like:
• Relying on 3rd party libraries provided by the package system, so that a “configuration” step is needed.
• Relying on 3rd party external programs provided by the package system, so that a “configuration” step is needed.
• Depending on platform-specific aspects, to demonstrate adaptability.
• Compiled with different features sets, to demonstrate configurability.
• The end product is a package (PKG on the Mac, DEB on ubuntu) equipped with checksums and maybe GPG signatures.
What other requirements could be interesting?
The text was updated successfully, but these errors were encountered:
• rely on quicklisp libraries
• build a CL binary that runs on a Windows machine. My first goal is to have something that the user can double-click on. Such an app could be a Ltk window or a web server that starts on the terminal and opens the default web browser. If you want an example with dozens of CL dependencies, external ones, and that would help a project, search no more :)
I heard that some test the windows binary on Wine.
A few ideas:
According to you, what are the basic requirements of such a software that would make a minimal example interesting?
To get started I would see something like:
• Relying on 3rd party libraries provided by the package system, so that a “configuration” step is needed.
• Relying on 3rd party external programs provided by the package system, so that a “configuration” step is needed.
• Depending on platform-specific aspects, to demonstrate adaptability.
• Compiled with different features sets, to demonstrate configurability.
• The end product is a package (PKG on the Mac, DEB on ubuntu) equipped with checksums and maybe GPG signatures.
What other requirements could be interesting?
The text was updated successfully, but these errors were encountered: