Re: accessing cygwin functions from non-cygwin app

2002-11-27 Thread Christopher Faylor
On Wed, Nov 27, 2002 at 06:48:35AM -0800, Joshua Daniel Franklin wrote: >--- Jan Beulich <[EMAIL PROTECTED]> wrote: >> Thanks for the answer, but you mainly missed the point: I want to dynamically >> load cygwin1.dll (if at all present on the system) and call a single function >> in it. The problem

Re: accessing cygwin functions from non-cygwin app

2002-11-27 Thread Joshua Daniel Franklin
--- Jan Beulich <[EMAIL PROTECTED]> wrote: > Thanks for the answer, but you mainly missed the point: I want to dynamically > load cygwin1.dll (if at all present on the system) and call a single function > in it. The problem is not the process of loading the DLL and calling the > function (I'm not a

Re: accessing cygwin functions from non-cygwin app

2002-11-27 Thread Soren A
"Jan Beulich" <[EMAIL PROTECTED]> wrote around 26 Nov 2002 [EMAIL PROTECTED]:">news:[EMAIL PROTECTED]: > All I intended was translating a coupld of filenames from cygwin to > Win32 notation in an otherwise Win32-only app. I quickly realized that > cygwin1.dll does not do all the necessary initial

Re: accessing cygwin functions from non-cygwin app

2002-11-27 Thread Guy Harrison
On Tue, 26 Nov 2002 11:13:20 +0100, "Jan Beulich" <[EMAIL PROTECTED]> wrote: >Hello, > >while I was trying to understand this on my own I'm ready to give up. All >I intended was translating a coupld of filenames from cygwin to Win32 notation >in an otherwise Win32-only app. I quickly realized that

Re: accessing cygwin functions from non-cygwin app

2002-11-26 Thread Joshua Daniel Franklin
> while I was trying to understand this on my own I'm ready to give up. All I > intended was translating a coupld of filenames from cygwin to Win32 notation > in an otherwise Win32-only app. > I have a problem using it as the application cannot be expected to have > access to the perprocess class

accessing cygwin functions from non-cygwin app

2002-11-26 Thread Jan Beulich
Hello, while I was trying to understand this on my own I'm ready to give up. All I intended was translating a coupld of filenames from cygwin to Win32 notation in an otherwise Win32-only app. I quickly realized that cygwin1.dll does not do all the necessary initialization on its own, i.e. from