| delorie.com/archives/browse.cgi | search |
Hi Peter, coming back to this now. > I'm also willing to help port and maintain. Fine. I have to offer two possible scenarios. 1. I have a stripped down standalone libffi package with a shared libffi now. This version is based on the sources from the cygwin release of gcc-3.3.3. You can take this package and maintain it, that means update it when Cygwin GCC is updated and integrate the changes happened in the libffi subdirectory. 2. Include this stripped down libffi version with the SableVM sourcetree and link libffi into the main DLL as a convenience library. IMO it would be easier to keep it uptodate when it is included with the SableVM sources and also distributed this way. So one can continue when you or me are gone. I have a patch I can send you, there is the stripped down libffi integrated in the SablVM build. The standalone libffi is available as separate package from my webserver: http://anfaenger.de/cygwin/cygwin-1.5/libffi-cygwin-standalone/ Ready compiled SableVM binary and source package: http://anfaenger.de/cygwin/cygwin-1.5/saqblevm/ The source package includes also the patch and uses a statically libffi, so it doesn't need a FFI DLL. Could you verify that this SableVM works as expected, please? Classpath is still compiling. Gerrit -- =^..^= http://nyckelpiga.de/donate.html -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
| webmaster | delorie software privacy |
| Copyright © 2019 by DJ Delorie | Updated Jul 2019 |