X-Recipient:	archive-cygwin AT delorie DOT com
DomainKey-Signature:	a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:mime-version:in-reply-to:references:from:date
	:message-id:subject:to:content-type; q=dns; s=default; b=LxeDcSR
	vzGDEPrsCvCuz/9a10BASlTPB4QCrrDUd0G4WYDNlUV4Er+ZC5/4MrQdMJaVMKv7
	lnJJseR8BeGZ3nQF5wVgrNMZ/4GGllQahmK8kS3dTqNUQ/P+duSOlrT1NC6kuobj
	jmQ7vRNF1VJjv8mUFFS2fInbRZXGiJqYYEDU=
DKIM-Signature:	v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:mime-version:in-reply-to:references:from:date
	:message-id:subject:to:content-type; s=default; bh=D5Tbeieo3Ff3o
	sy8HZ/U/Te25HQ=; b=ZM1No+gRq/j0P5HBu0XlLsk9DLgXUR/7EREtmIPXCFGmr
	5E9PknzDEfCp9aZ+/yYR25K3DSsv8NOxhIKf86I9QOpLsCpcv6CPU+NUtE6vKb9K
	WvRGpJRBtKBBBtUchQVp0hMcnuLJrobhFOSiwkCT9/+8RIKBOtWtAhm4Zbf9uw=
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.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
X-Spam-SWARE-Status:	No, score=-4.1 required=5.0 tests=BAYES_00,KHOP_THREADED,RCVD_IN_DNSWL_LOW,RCVD_IN_HOSTKARMA_YE,SPF_PASS autolearn=ham version=3.3.1
X-Google-DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:sender:x-originating-ip:in-reply-to:references:from :date:x-google-sender-auth:message-id:subject:to:content-type :x-gm-message-state; bh=5M9HwxjbTbTeHTTed6vQ4shAhoZFeE10utjB33sOVBo=; b=Wqzwgyfm+B2VAgCuMgsQs5PCKtCjHIDWcZsS8jymo2l8W4dk9y4lL/iqwpPYIKKrpN 1BIsFKxGHKU2VH7CWaog9zf7Pxs+ZXxrZaIKe8XfHtcAglAmlVz1uf/bGTh1D7r5FCzG ZV/3nBnWaTXUocVd4zW5dsR9hk2qtW64twldQCVDNFv1k2ti3Wktyb4RxxY1hrbArmHe kbWYK536Yfa0FUpE6fOcqOQUSwe+cgO89PowEvs74AMi7pgUfPWpq9ellCFfkTs0ZJ62 rXLkDVsd0ikDRI4oJGJAPAPHLMPrHSrS1KugQLM5m70BUvqtEbkHoWdxSx5iLCYXZSVV cI8Q==
X-Received:	by 10.229.4.205 with SMTP id 13mr4451331qcs.149.1369320410739; Thu, 23 May 2013 07:46:50 -0700 (PDT)
MIME-Version:	1.0
In-Reply-To:	<20130523090154.GF22259@calimero.vinschen.de>
References:	<CALgEz7rPZLJmg6nBacALfvdhkRUT5st+hMEciSuQd9y46xRuYQ AT mail DOT gmail DOT com> <CALgEz7qWEicXk5SQAbYuoiK-7PEeq-HRAJ59Gwt=kVzjKL9RTw AT mail DOT gmail DOT com> <CALgEz7p9EUX5XevA6mGk9c6JN_x0u0Jb1Cswi9-J20TDKvey=Q AT mail DOT gmail DOT com> <20130522084711 DOT GU2406 AT calimero DOT vinschen DOT de> <20130522145813 DOT GC8150 AT ednor DOT casa DOT cgf DOT cx> <20130522152450 DOT GA22259 AT calimero DOT vinschen DOT de> <519D8889 DOT 5070206 AT cygwin DOT com> <20130523090154 DOT GF22259 AT calimero DOT vinschen DOT de>
From:	Robert Pendell <shinji+cygwin AT elite-systems DOT org>
Date:	Thu, 23 May 2013 10:46:20 -0400
Message-ID:	<CAAeCd-N8rWNUU3wrLahqtHmA9w7qzkA4ODQuusR9j-R3WuG16Q@mail.gmail.com>
Subject:	Re: Including full path to shared library in the executable file
To:	cygwin AT cygwin DOT com
X-Gm-Message-State:	ALoCoQlAcmeiF1w8r454uvW9aizV87+W2c50ZJHN7YPxq+nly6ZruVSQ8p6G4Al1QiogT638WVjg

On Thu, May 23, 2013 at 5:01 AM, Corinna Vinschen <> wrote:
>
> On May 22 23:10, Larry Hall (Cygwin) wrote:
> > On 5/22/2013 11:24 AM, Corinna Vinschen wrote:
> > >On May 22 10:58, Christopher Faylor wrote:
> > >>On Wed, May 22, 2013 at 10:47:11AM +0200, Corinna Vinschen wrote:
> > >>>On May 21 21:43, Balaji Venkataraman wrote:
> > >>>>On Tue, May 21, 2013 at 9:19 PM, Balaji Venkataraman wrote:
> > >>>>
> > >>>>>My question is whether there is a way to include the full path to the .dll
> > >>>>>while creating the .exe - much like how cmake "link_directories" or
> > >>>>>"target_link_libraries" allows you to - for e.g. on Linux (an ldd on the
> > >>>>>executable file shows the full path to the .so file and thus
> > >>>>>precludes the need to explicitly set LD_LIBRARY_PATH). While this is not a
> > >>>>>cmake question (or a cmake mailing list) if you have experience solving
> > >>>>>this problem using cmake, would appreciate those insights as well.
> > >>>>
> > >>>>I found this while looking for cygwin RPATH:
> > >>>>http://www.cmake.org/pipermail/cmake/2007-October/017267.html. Perhaps
> > >>>>the lack of RPATH support on Windows/Cygwin is the reason?
> > >>>
> > >>>RPATH is an ELF feature.  Full paths to DLLs are not supported by the
> > >>>PE/COFF executable format.  Also, Cygwin DLLs are still loaded by the
> > >>>Windows loader, so POSIX paths won't work, and full Windows paths won't
> > >>>make much sense, given that Cygwin is not always installed into
> > >>>C:\cygwin.
> > >>>
> > >>>The solution for this would be an ELF loader in Cygwin and a Cygwin
> > >>>linker which produces ELF DLLs by default.  But that's quite a big
> > >>>project on its own and nobody seemed to have fun, time, or money, to
> > >>>implement this.
> > >>
> > >>So, maybe *next* Thursday then?
> > >
> > >Alas, I still have no cat...
> >
> > Can someone *please* donate a cat for Corinna?
>
> Oh, please, no!
>
>
> Corinna

*Mails a litter of kittens to Corinna*

Robert Pendell
A perfect world is one of chaos.

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

- Raw text -