delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/2008/02/17/19:51:14

X-Recipient: archive-cygwin AT delorie DOT com
X-Spam-Check-By: sourceware.org
Message-ID: <d990efca0802171650p7a9c70afvec4ce80b798eafa2@mail.gmail.com>
Date: Sun, 17 Feb 2008 19:50:22 -0500
From: "Mirko Vukovic" <mirko DOT vukovic AT gmail DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: how to build gsl dll
In-Reply-To: <47B888D6.40037BBA@dessent.net>
MIME-Version: 1.0
References: <d990efca0802171021v4d90e1a9yeab45fd2cc88afab AT mail DOT gmail DOT com> <47B888D6 DOT 40037BBA AT dessent DOT net>
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

On Sun, Feb 17, 2008 at 2:19 PM, Brian Dessent <brian AT dessent DOT net> wrote:
> Mirko Vukovic wrote:
>
>  > I am trying to build a dll for gsl.  I want to link it to clisp.
>
>  Why?  The Cygwin gsl packages already contains everything you need,
>  including both shared and static versions.  Install the 'gsl' package
>  for the runtime files (the DLL) and install 'gsl-devel' for the
>  developer files (headers, import library, static library, libtool
>  library.)  You don't have to do anything.
>
>
>  > On the other hand the gsl executable contains the *.a, *.dll.a and
>  > *.la files. Is there a way to convert them to the dll.a
>
>  That doesn't make any sense.  There is no need to convert anything, not
>  that that's even possible.
>
>
>  > Frankly, I started dealing with libraries only about a week ago, and
>  > while I understand the .a, .so, .dll types (I think), I'm not sure
>  > about dll.a and .la.
>
>  For a package 'foo' cygfoo-n.dll is the shared library, it goes in
>  /usr/bin since it must be in the PATH.  This is the only file that is
>  actually used at runtime[1], as opposed to link time.  n is the ABI
>  version, if present.  libfoo.dll.a is the import library for
>  cygfoo-n.dll and it goes in /usr/lib.  An import library is just an aide
>  for the linker, it contains no actual code.  libfoo.a is the static
>  version of the library, and also goes in /usr/lib.  Sometimes import
>  libraries are also named libfoo.a too but this practice is discouraged,
>  it's mostly legacy things like all the w32api import libs that are still
>  named this way.  Import libraries can also be renamed as foo.lib if they
>  are to be used by the MS toolchain.  libfoo.la is the libtool library,
>  it's just a text file that describes aspects of the library and is used
>  by libtool if you use that to link.
>
>  Brian
>
>  [1] Okay technically the libtool .la file could be read at runtime if
>  the library is dlopened with libltdl, but that's probably not relevant
>  here.
>

Thank you.  I found it: cyggsl-0.dll, cyggslcblas-0.dll in /usr/bin.
Thank you very much for the explanation.

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/
>
>

--
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/

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019