Jonathan,
I have to admit that I don't quite understand your original question either.
However, it seems like you're interested in understanding some of the
internals of Cygwin's gcc and the -mno-cygwin switch.
First of all, a quick response: when you specify -mno-cygwin to the
compiler, __CYGWI
Here's a method that I have used successfully:
- Build your Cygwin DLL. Whether you build the DLL with dlltool, dllwrap, or
libtool, a .def file should be produced in the process.
- Use MSVC's command line tool "lib" with the /def option and your .def file
to generate an MSVC-style .lib import l
I'll take a guess...
Perhaps when FoxPro uses a DLL, it's similar to when Visual Basic uses one.
With VB, the functions that you export from your DLL must following the
standard calling convention __stdcall, opposed to the C calling convention
__cdecl. If FoxPro is the same, then it's calling you
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf
> Of Earnie Boyd
> Sent: Monday, January 14, 2002 5:43 AM
> To: Robert Collins
> Cc: Jon Leichter; [EMAIL PROTECTED]; [EMAIL PROTECTED]
> Subject: Re: Compiling apps to Mingw32 with c
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf
> Of Robert Collins
> Sent: Sunday, January 13, 2002 12:31 PM
> To: Jon Leichter; Earnie Boyd
> Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]
> Subject: Re: Compiling apps t
lto:[EMAIL PROTECTED]]On Behalf
> Of Robert Collins
> Sent: Saturday, January 12, 2002 3:28 PM
> To: Earnie Boyd; Jon Leichter
> Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]
> Subject: Re: Compiling apps to Mingw32 with cygwin
>
> - Original Message -
> From: "Earnie
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf
> Of Earnie Boyd
> Sent: Friday, January 11, 2002 4:01 AM
> To: Jon Leichter
> Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]
> Subject: Re: Compiling apps to Mingw32 with cygwin
&
> -Original Message-
> From: Robert Collins [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, January 10, 2002 6:25 PM
> To: Jon Leichter
> Cc: [EMAIL PROTECTED]
> Subject: Re: Compiling apps to Mingw32 with cygwin
>
> - Original Message -----
> From: "
> -Original Message-
> From: Robert Collins [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, January 10, 2002 6:16 PM
> To: Jon Leichter
> Cc: [EMAIL PROTECTED]
> Subject: Re: Compiling apps to Mingw32 with cygwin
>
>
> - Original Message -
> From: &q
;, but it WILL work.
This whole thread went off on a tangent suggesting that my solution was
wrong. So tell me. If my solution works more often than the "proper" one,
how is it wrong?
Jon
> -----Original Message-
> From: Robert Collins [mailto:[EMAIL PROTECTED]]
> Se
> -Original Message-
> From: Robert Collins [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, January 10, 2002 5:45 PM
> To: Jon Leichter
> Cc: [EMAIL PROTECTED]
> Subject: Re: Compiling apps to Mingw32 with cygwin
>
> - Original Message -----
> From: "
> -Original Message-
> From: Robert Collins [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, January 10, 2002 5:27 PM
> To: Jon Leichter
> Cc: [EMAIL PROTECTED]
> Subject: Re: Compiling apps to Mingw32 with cygwin
>
>
> - Original Message -
> From: &q
Ok. I need to return to asking some questions with my new understanding
of --build, --host, and --target (which I'm incredibly grateful for and
happy about).
I have returned to working with OpenLDAP. The configure script is generated
with autconf-2.13.1. It uses AC_CANONICAL_SYSTEM, which you say
PM
> To: Jon Leichter
> Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]
> Subject: Re: Compiling apps to Mingw32 with cygwin
>
>
> - Original Message -
> From: "Jon Leichter" <[EMAIL PROTECTED]>
>
> > > No. Specify --host. The meaning is clearly docume
> -Original Message-
> From: Earnie Boyd [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, January 10, 2002 2:31 PM
> To: Jon Leichter
> Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]
> Subject: Re: Compiling apps to Mingw32 with cygwin
>
> Using `gcc -mno-cygwin' is sw
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf
> Of Robert Collins
> Sent: Thursday, January 10, 2002 1:44 PM
> To: [EMAIL PROTECTED]
> Cc: [EMAIL PROTECTED]
> Subject: Re: Compiling apps to Mingw32 with cygwin
>
> Autoconf 2.13 supports these options -
Earnie Boyd wrote:
> Your wrapper script is a good idea but has the wrong name as has been
> pointed out already. It needs to be named i386-pc-mingw32-gcc and a
> copy as mingw32-gcc so that when specifying the --host=mingw32 or
> --host=i386-pc-mingw32 the configure script will find it appropria
for GNU
Libtool, as I have mentioned. I use a wrapper script: CC=mgcc. What do you
think of this Earnie?
Jon
> -Original Message-
> From: Earnie Boyd [mailto:[EMAIL PROTECTED]]
> Sent: Monday, January 07, 2002 6:29 AM
> To: CU List
> Cc: Jon Leichter; J. Henning Schwentn
For the most part, I agree with you. Autoconf and Libtool should be fixed.
The motto of the groups seems to be: "patches gratefully accepted". Thus,
unless you, me, or someone else that uses Cygwin GCC for MinGW wants to make
these changes, I wouldn't count on them coming around any time soon.
On
Hi Henning.
You can use Cygwin's GCC. It's just a little more involved. Here's a short
answer. When you configure, do so like this:
$ env CC="gcc -mno-cygwin" ./configure --host=i386-pc-mingw32
Notice that your --host specification was a little off. The way that I have
specified it is t
Seeing how G:\CYGWIN\BIN is further in your path than some other significant
directories, I'm wondering if you're executing the correct 'chmod' binary.
>From a bash shell, show us the output of the following:
$ type chmod
===
Jon
> -Original Message-
> From: [EMAIL PROTECTED]
> - Original Message -
> From: "Jon Leichter" <[EMAIL PROTECTED]>
> > > However , once gcc's specs are changedm linking with the libraries
> they
> > > provide will fail - which is what I was talking about.
> >
> > Hmm...
> -Original Message-
> From: Robert Collins [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, December 27, 2001 6:35 PM
> To: Jon Leichter
> Cc: [EMAIL PROTECTED]
> Subject: Re: Potential problems with Cygwin GCC and -mno-cygwin switch
>
> However , once gcc's sp
depend on
DLLs accessible via the PATH, which are NOT relocated from /usr/bin.
Jon
> -Original Message-
> From: Robert Collins [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, December 27, 2001 6:23 PM
> To: Jon Leichter
> Cc: [EMAIL PROTECTED]
> Subject: Re: Potential problems w
Sorry Chris... just some final words...
> -Original Message-
> From: Robert Collins [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, December 27, 2001 5:28 AM
> To: Jon Leichter; [EMAIL PROTECTED]
> Subject: Re: Potential problems with Cygwin GCC and -mno-cygwin switch
>
Hello all.
It's been a long time since I was active on this list. I have not used
Cygwin for over a year, until recently. I see that Cygwin has been updated
quite a bit since I last used it. It's very nice to see these new features.
I have a couple of issues to discuss about Cygwin GCC and it's
26 matches
Mail list logo
