Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm 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 Reply-To: Cygwin List Message-Id: <6.0.1.1.0.20040406115543.037c68e8@127.0.0.1> X-Sender: Date: Tue, 06 Apr 2004 11:56:09 -0400 To: "Jay West" , From: Larry Hall Subject: Re: Will using cygwin help with back-linking? In-Reply-To: <010201c41beb$013a9ee0$033310ac@kwcorp.com> References: <010201c41beb$013a9ee0$033310ac AT kwcorp DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" At 11:22 AM 4/6/2004, you wrote: >I've googled and searched the cygwin FAQ, if my question is already answered >there perhaps someone can at least tell me what term to search for as >"back-linking" didn't seem to offer germane tips? > >I'm new to cygwin. I have a Unix application I'd like to go through and make >sure it can also compile and run on a windows machine with cygwin. The Unix >application relies on "back-linking" with regards to dlopen'able modules. >Specifically, any dlopen'able module needs to have access to any variables >defined globally in the calling application. On Unix, when the module is >dlopened by the main program, it's references to global variables in the >main program are all resolved then. > >>From my googling and reading, I am told Windows does not support this >concept of "back-linking". So I was wondering if loading cygwin on the >machine will provide this feature, or am I left with totally restructuring >the application to stuff the global variable definitions into a library? > >Any tips in the right direction are most appreciated! Did you see this? -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 838 Washington Street (508) 893-9889 - FAX Holliston, MA 01746 -- 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/