Request to remove owl-lisp cloning during radamsa build about radamsa HOT 6 CLOSED

Hi,

Good points and thanks for reminding me about this issue. Radamsa.c was included in previous releases specifically to avoid these issues and extra dependency on owl, but Google Code shut down, Radamsa migrated to Github, and I hadn't figured out when releasing 0.4 how to add separate tarballs or binaries to/as the release.

A temporary solution was to put the downloads with signatures to http://haltp.org/download, and you can also do $ make build_radamsa, which by default uses /usr/bin/ol, to avoid a local build.

Radamsa 0.5 should come out soonish after the current IO changes are done in Owl, an easy solution would be to include and update the prebuilt C code at each release. The Makefile is written so that owl is cloned only if radamsa.c needs to be rebuilt, so checking out with a release tag or downloading a prebuilt package would then cause no owl cloning.

Doing a quick build of owl is also a good idea. If you are using a local checkout, you probably don't want to do a full build. E.g., by using:

local_radamsa:
   -git clone https://github.com/aoh/owl-lisp.git
   -cd owl-lisp && git pull 
   cd owl-lisp && make bin/vm
   owl-lisp/bin/vm owl-lisp/fasl/init.fasl -O2 -o radamsa.c rad/main.scm

it takes about 8 seconds to build Radamsa on my machine.

from radamsa.

Radamsa now fetches a tagged version of owl and only does a minimal build. Will have to remember to add the prebuilt C code for next release, but this issue is now fixed.

Thanks for filing the issue. Let me know if you run into issues with the fix.

from radamsa.

v0.5 was released today and I gave it a look. I noticed that there is no artifact attached to the release which contains a prebuilt C code file for Radamsa. Is there interest in uploading a tarball which contains the release as well as a pre-generated radamsa.c file?

Thank you for your consideration.

from radamsa.

Github releases might be a solution to this. I didn't have time to check out how they work yesterday though, so the current release tarball is just autogenerated from the tag for now.

from radamsa.

Yes, it seems to be easy to add custom tarballs along with releases. The default radamsa-0.5.tar.gz download now has radamsa.c again, so the build does not depend on owl. If the actual sources are altered, only then the correct version of owl is loaded and radamsa.c is rebuilt.

from radamsa.

Awesome! Thanks!

from radamsa.