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:date :message-id:subject:from:to:content-type; q=dns; s=default; b=Wk gx7LDnHC4PyLLIzXiFUt3vOzzBllT0xIUW3SrhBjw/4Ic2hqv6t6DXtrlia/7zgT jM/Hnfd3oknkszx56WTK5MM3nl/fP444o9xxaLUYzSx2BM2OaUhBLmHon2LIuaqI IRX+OQBjK1HfA5vIpBWk6VBcZdJkAL/4ViRnWkQVk= 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:date :message-id:subject:from:to:content-type; s=default; bh=9clgw3Oc F0O5RPV89yJx5gizGTg=; b=Mu0Dw/fUHzjMNUgVLFbKOmzKGhYGD00IWF2zvOus lB0T3Sqq4P+/8xA9S/+XwjsawjBMtp/8dY2zZfSvR7ACZGAuwJE/t5/wF4/PKBaL eOh+nNO9/KWI64VdfY3eItCvy6EUCMBnj5IQHBTOCsV/M6USaAIcbTejI17ztM48 a94= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: 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 X-Spam-SWARE-Status: No, score=-0.9 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,KHOP_THREADED,RCVD_IN_DNSWL_LOW,RCVD_IN_HOSTKARMA_YE,SPF_PASS autolearn=ham version=3.3.1 MIME-Version: 1.0 X-Received: by 10.15.108.6 with SMTP id cc6mr14274504eeb.28.1369196368397; Tue, 21 May 2013 21:19:28 -0700 (PDT) In-Reply-To: References: Date: Tue, 21 May 2013 21:19:28 -0700 Message-ID: Subject: Fwd: Including full path to shared library in the executable file From: Balaji Venkataraman To: cygwin AT cygwin DOT com Content-Type: text/plain; charset=ISO-8859-1 Hi - I've tried searching online and in mailing list archives but I couldn't find what I'm looking for. As I understand it, a Cygwin binary compiled with a shared library (my own lib), will run only if the .dll file can be found in $PATH, or in the current working directory from where the executable is run or in the same directory as the executable. Hope I haven't missed any other variations. 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. TIA, Balaji -- 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