DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:reply-to:mime-version:to
	:subject:references:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=Y96LfX7JYyck+w1n
	mAK/oERovQaCa2DzKoZmcOyNZVOhWpkB+4ElwFURhDLjYnaCGbwIg+Ayx0MwxEX5
	Fydo386AGHzI7NM4Wp5qy4iZTHuNAz2Sa7YNnqiowgRiWtqdEtTcm651WeRot1VH
	eaETXg9fo3sac40fpVGr2PnGWz8=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Message-id: <519D8889.5070206@cygwin.com>
Date: Wed, 22 May 2013 23:10:01 -0400
From: "Larry Hall (Cygwin)" <reply-to-list-only-lh@cygwin.com>
Reply-to: cygwin@cygwin.com
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-version: 1.0
To: cygwin@cygwin.com
Subject: Re: Including full path to shared library in the executable file
References: <CALgEz7rPZLJmg6nBacALfvdhkRUT5st+hMEciSuQd9y46xRuYQ@mail.gmail.com> <CALgEz7qWEicXk5SQAbYuoiK-7PEeq-HRAJ59Gwt=kVzjKL9RTw@mail.gmail.com> <CALgEz7p9EUX5XevA6mGk9c6JN_x0u0Jb1Cswi9-J20TDKvey=Q@mail.gmail.com> <20130522084711.GU2406@calimero.vinschen.de> <20130522145813.GC8150@ednor.casa.cgf.cx> <20130522152450.GA22259@calimero.vinschen.de>
In-reply-to: <20130522152450.GA22259@calimero.vinschen.de>
Content-type: text/plain; charset=ISO-8859-1; format=flowed
Content-transfer-encoding: 7bit

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?

-- 
Larry

_____________________________________________________________________

A: Yes.
 > Q: Are you sure?
 >> A: Because it reverses the logical flow of conversation.
 >>> Q: Why is top posting annoying in email?

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