X-Recipient: archive-cygwin@delorie.com X-Spam-Check-By: sourceware.org Message-ID: Date: Mon, 18 Feb 2008 12:04:02 -0500 From: "Mirko Vukovic" To: cygwin@cygwin.com Subject: Re: how to build gsl dll In-Reply-To: <6910a60802180801q3b3b7fdbs71be7cf7dbe53805@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <6910a60802180801q3b3b7fdbs71be7cf7dbe53805@mail.gmail.com> X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com On Mon, Feb 18, 2008 at 11:01 AM, Reini Urban wrote: > Hi Mirko > > 2008/2/17, Mirko Vukovic : > > > I am trying to build a dll for gsl. I want to link it to clisp. > > I would suggest not to use a static clisp module, just use the FFI. > This is much simplier, smaller and easier to test. See libsvm or matlab, > or pari for a more optimized binding. > > I want to do this for my gdi module also, but had no time yet. > And we still have no header parser, which could construct the > FFI binding automatically. cffi might be useful. > -- > Reini Urban > http://phpwiki.org/ http://murbreak.at/ > http://spacemovie.mur.at/ http://helsinki.at/ > > > > -- > 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/ > > Reini, The reason why I need cffi is that I am trying to get nlisp to work on clisp+cygwin. And nlisp is using cffi. I have nlisp running at work on linux+sbcl, but my laptop has only cygwin. I posted a message on the cffi mailing list, and Luis is helping me there. Mirko -- 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/