Dear All,
After three years of development we are closing to a new release. During this time many important features and fixes has been made. We also have a new co-maintainer of the project – Marius Gerbershagen, what is a fantastic news (especially from a bus-factor perspective :-).
If you have spare machines (especially on uncommon architectures/ operating systems), it would be very helpful if you could help with testing. I'm tracking testing progress here:
https://gitlab.com/embeddable-common-lisp/ecl/issues/333
there is no need to limit yourself to the mentioned platforms and it is possible that we will omit some listed there, so please treat it more like a wishlist than an actual roadmap. We are especially interested in regressions (that is issues which are not present in 16.1.3 but occur in the current develop branch) - of course if you encounter other problems please report them too, but they will be most likely addressed after the release. Thank you for your help; I hope that we will be able to release the new version on January 2020.
As a side note, I've been invited to give a talk at the European Lisp Symposium this year about ECL. Currently I'm working on the compiler documentation and refactoring as well as the IR visualizer, but these changes will be proposed after there release.
Best regards, Daniel
-- Daniel Kochmański ;; aka jackdaniel | Przemyśl, Poland TurtleWare - Daniel Kochmański | www.turtleware.eu
"Be the change that you wish to see in the world." - Mahatma Gandhi
On 12/30/19, Daniel Kochmański daniel@turtleware.eu wrote:
Dear All,
After three years of development we are closing to a new release. During this time many important features and fixes has been made. We also have a new co-maintainer of the project – Marius Gerbershagen, what is a fantastic news (especially from a bus-factor perspective :-).
If you have spare machines (especially on uncommon architectures/ operating systems), it would be very helpful if you could help with testing. I'm tracking testing progress here:
Just for future reference, here is how I tested on android (assuming you already have a cross-compiled ECL):
adb push bin/ecl /data/local/tmp/ adb push lib/libecl.so /data/local/tmp/ adb push lib/ecl-xx.x.x/encodings /data/local/tmp/ adb push lib/ecl-xx.x-x/*.doc /data/local/tmp/ adb push lib/ecl-xx.x.x/*.asd /data/local/tmp/ adb push lib/ecl-xx.x.x/*.fas /data/local/tmp/
edit last line of '<ecl>/src/tests/doit.lsp' changing #+(or) to #+(and), then do
adb push <ecl>/src/tests /data/local/tmp/ adb shell $ cd /data/local/tmp $ export LD_LIBRARY_PATH=/data/local/tmp $ chmod a+x ecl $ ./ecl
(ext:install-bytecodes-compiler) (load "tests/doit.lsp")
Paul
there is no need to limit yourself to the mentioned platforms and it is possible that we will omit some listed there, so please treat it more like a wishlist than an actual roadmap. We are especially interested in regressions (that is issues which are not present in 16.1.3 but occur in the current develop branch) - of course if you encounter other problems please report them too, but they will be most likely addressed after the release. Thank you for your help; I hope that we will be able to release the new version on January 2020.
As a side note, I've been invited to give a talk at the European Lisp Symposium this year about ECL. Currently I'm working on the compiler documentation and refactoring as well as the IR visualizer, but these changes will be proposed after there release.
Best regards, Daniel
-- Daniel Kochmański ;; aka jackdaniel | Przemyśl, Poland TurtleWare - Daniel Kochmański | www.turtleware.eu
"Be the change that you wish to see in the world." - Mahatma Gandhi
-
Daniel Kochmański -
PR