-
Notifications
You must be signed in to change notification settings - Fork 104
New issue
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.
Already on GitHub? Sign in to your account
Support building without binaries in the clone #5
Comments
Also, it would be nice if rebuilding would not overwrite the binaries used to rebuild. |
@informatimago It is the Lisp kernel's makefile that overwrites the binaries. It could be parametrized in order to accept a new name for the resulting binary and its matching Lisp image. |
More than one thing is at issue here. The first is that the lisp kernel executable needs to find a heap image to load. By default, the executable looks in its own directory for an image. Next, we need to know where the sources are. That's the "ccl:" directory (set via Finally, because the CCL sources use the The interface databases are the troublesome thing, it seems to me. I could imagine a new environment variable like To avoid putting binaries in the clone, we'd be looking at some directory structure like this, probably:
Then, you'd set Anyway, all this is just thinking out loud, so to speak. If it weren't for the interface database, we could almost do this today: set |
It’s inconvenient to have to merge a binary distribution into a cloned repository in order to build it. It should be possible to build CCL without having binaries in the same directory, as long as
ccl
orccl64
is in thePATH
.The text was updated successfully, but these errors were encountered: