X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Message-ID: <6910a60802180801q3b3b7fdbs71be7cf7dbe53805@mail.gmail.com> Date: Mon, 18 Feb 2008 17:01:19 +0100 From: "Reini Urban" To: cygwin AT cygwin DOT com Subject: Re: how to build gsl dll In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: X-Google-Sender-Auth: be523315762284b3 X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com 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/