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:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; q=dns; s=
	default; b=y1ZTJxXARfeJtNU4VdixElgaReYOjtC8ZV3CZZ93rpgvB8EANs/fk
	KNGRD4nZ5i5yS4h7eQvJu/IGZ4R80Y529/xkenPg3QPDmU0lCts/XF5mZ64Y4Cq+
	QfPbkRbMKrzVbbUf0j0y6KYv92+SMkmk5bRTWH2sa4PB7ibip/OGhY=
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:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; s=default;
	bh=wBi4r/m73mS5wGH3j8l6WpTVcQg=; b=E1h0Eqo9R9ID8WoxRVGraVyahiAE
	0zglCvTc3QVJ7laGgBOv/Eqbrc12U8aqp/wK9/UZ+eb8fRJSYp84eVtTT2VB4GbA
	wJI1aiJDxCHYk2h43bO6A5IZFJCzT163j9Fe+p9mUCSMtCjCQ6ZFfZ4b/l6g+xma
	pd4m58bluoqTsuo=
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=-1.7 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,RCVD_IN_HOSTKARMA_YE autolearn=ham version=3.3.1
X-Mail-Handler:	Dyn Standard SMTP by Dyn
X-Report-Abuse-To:	abuse AT dyndns DOT com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information)
X-MHO-User:	U2FsdGVkX181Cll4oyYB6Y500K87oWd7
Date:	Wed, 22 May 2013 10:58:13 -0400
From:	Christopher Faylor <cgf-use-the-mailinglist-please AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: Including full path to shared library in the executable file
Message-ID:	<20130522145813.GC8150@ednor.casa.cgf.cx>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
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>
MIME-Version:	1.0
In-Reply-To:	<20130522084711.GU2406@calimero.vinschen.de>
User-Agent:	Mutt/1.5.20 (2009-06-14)

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?

cgf

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