public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Timothy I. McGinnis" <tmcginnis@synertechsystems.com>
To: tml@iki.fi
Cc: gtk-list@redhat.com, cygwin@sourceware.cygnus.com
Subject: Re: gtk_entry field turning black in cygwin
Date: Wed, 15 Mar 2000 06:19:00 -0000	[thread overview]
Message-ID: <052568A3.004E9C8C.00@stecln02.synertechsystems.com> (raw)

Okay.  :-)

This is my first foray into the win32 world (and outside of Unix) so I am rather
confused.  I took a look at the Readme.win32 and.. was confused.  So being
impatient that I am I just went ahead and tried.  And then bugged you guys.
Sorry.

I will take a closer look at all of this and see if I can figure out what I am
doing wrong.

My apologies to the cygwin list for the off-topic question.

Thanks for making this clearer.

Tim M.

PS  Can you recommend any books, etc. that would help a unix guy learn win32?





Tor Lillqvist <tml@iki.fi> on 03/15/2000 08:52:05 AM


To:   Timothy I. McGinnis/MIS/3605VW/SYNERTECH@SYNERTECH
cc:   cygwin@sourceware.cygnus.com, gtk-list@redhat.com
bcc:
Subject:  Re: gtk_entry field turning black in cygwin



> I am using cygwin B20.1, gtk-win32 20000115 release compiling using
> gcc from the cygwin distribution.

(As the GTk+ port does not use cygwin, and programs using GTk+ thus
shouldn't either (never mix C runtimes), this is really off-topic for
the cygwin list.)

If you really mean you are using the gcc that is included in the B20.1
distribution, you shouldn't. As is said on my webpage for the GTK+ and
GIMP port to Windows, to build programs intended to use the prebuilt
DLLs you can either use MSVC, or gcc 2.95 (or later) with the
-fnative-struct switch.

The reason is that the DLLs are built with gcc-2.95.2 using the
-fnative-struct switch, which makes the struct field allocation and
alignment compatible with MSVC, which is a good thing. (Otherwise
there would have to be separate DLLs for programs built with MSVC and
gcc.) Building with gcc but without the -fnative-struct switch will
cause problems sooner or later, quite possibly like the ones you are
seeing.

Getting a correctly set up gcc can be a bit convoluted. (We want a
version that has -fnative-struct and uses the MSVCRT runtime.)  There
are instructions on one way to do it in the README.win32 file linked
to from the webpage, but people have told me that those instructions
are unnecessarily convoluted. Apparently it is easier using a pure
mingw environment. Possibly some recent mingw gcc release from Mumit
Khan is suitable as is?

--tml





--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

             reply	other threads:[~2000-03-15  6:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-03-15  6:19 Timothy I. McGinnis [this message]
  -- strict thread matches above, loose matches on Subject: below --
2000-03-15  5:52 Tor Lillqvist
2000-03-15  5:05 Timothy I. McGinnis

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=052568A3.004E9C8C.00@stecln02.synertechsystems.com \
    --to=tmcginnis@synertechsystems.com \
    --cc=cygwin@sourceware.cygnus.com \
    --cc=gtk-list@redhat.com \
    --cc=tml@iki.fi \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).