From: Charles Wilson <cwilson@ece.gatech.edu>
To: cygwin@cygwin.com
Subject: Re: GTK on cygwin
Date: Mon, 20 May 2002 06:04:00 -0000 [thread overview]
Message-ID: <3CE8BBEA.7030709@ece.gatech.edu> (raw)
In-Reply-To: <20020520064117.GA18463@redhat.com>
Christopher Faylor wrote:
> Just to add to the thread, I assume that if GTK+ can be built using mingw,
> it should be pretty easy to build it for native cygwin. Have you tried
> just building it with Cygwin's gcc?
It's a really long story. Short version:
windows port is on a separate branch from the trunk, and follows its own
release cycle.
Long version:
Most people grab the "real" gtk+ (e.g. the unix one) and try to build
that -- expecting the cygwin build to use MS graphics. AFAIK, the
windows stuff has not been merged.
The windows branch can build in three ways: msvc makefiles, mingw
makefiles (unmaintained), and mingw configury script (MSYS?). Tor uses
the third option. However, it's unclear how well his native graphics
stuff will merge with normal unixy event loops. I'm not sure how
divergent the mainline and winbranch are.
Finally, there's the whole "which version" problem. There's 1.2.x,
1.3.x, and now pre-2.0. Which one are you talking about? mainline is
real close to 2.0; winbranch is back on 1.3.x somewhere. But most
people who attempt to build gtk/glib on cygwin use the 1.2.x branch
(Steven O'Brien, etc) -- and do an X build.
Personally, I'd like to see an X-based version first -- that seems
easiest. Then perhaps a cygwin port of the windows branch -- but Tor
doesn't seem too thrilled about that enterprise. This would probably
work better once the windows branch is merged back into the mainline
code -- but I dunno when that will happen.
As far as 2.0 goes, which requires pkgconfig and iconv....well,
pkgconfig is already an official cygwin package (many recent changes to
pkgconfig were instigated by Tor to make the MSYS/mingw configury
better). iconv has been available on my testing site for weeks now, but
after all the blather and complaining, nobody has volunteered to
maintain it. And NO, it will not be me.
--Chuck
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
WARNING: multiple messages have this Message-ID
From: Charles Wilson <cwilson@ece.gatech.edu>
To: cygwin@cygwin.com
Subject: Re: GTK on cygwin
Date: Mon, 20 May 2002 06:05:00 -0000 [thread overview]
Message-ID: <3CE8BBEA.7030709@ece.gatech.edu> (raw)
Message-ID: <20020520060500.6aV46911oOKLn-_z0ZBjxwE4kUfZVbcsp5W7QRGANcU@z> (raw)
In-Reply-To: <20020520064117.GA18463@redhat.com>
Christopher Faylor wrote:
> Just to add to the thread, I assume that if GTK+ can be built using mingw,
> it should be pretty easy to build it for native cygwin. Have you tried
> just building it with Cygwin's gcc?
It's a really long story. Short version:
windows port is on a separate branch from the trunk, and follows its own
release cycle.
Long version:
Most people grab the "real" gtk+ (e.g. the unix one) and try to build
that -- expecting the cygwin build to use MS graphics. AFAIK, the
windows stuff has not been merged.
The windows branch can build in three ways: msvc makefiles, mingw
makefiles (unmaintained), and mingw configury script (MSYS?). Tor uses
the third option. However, it's unclear how well his native graphics
stuff will merge with normal unixy event loops. I'm not sure how
divergent the mainline and winbranch are.
Finally, there's the whole "which version" problem. There's 1.2.x,
1.3.x, and now pre-2.0. Which one are you talking about? mainline is
real close to 2.0; winbranch is back on 1.3.x somewhere. But most
people who attempt to build gtk/glib on cygwin use the 1.2.x branch
(Steven O'Brien, etc) -- and do an X build.
Personally, I'd like to see an X-based version first -- that seems
easiest. Then perhaps a cygwin port of the windows branch -- but Tor
doesn't seem too thrilled about that enterprise. This would probably
work better once the windows branch is merged back into the mainline
code -- but I dunno when that will happen.
As far as 2.0 goes, which requires pkgconfig and iconv....well,
pkgconfig is already an official cygwin package (many recent changes to
pkgconfig were instigated by Tor to make the MSYS/mingw configury
better). iconv has been available on my testing site for weeks now, but
after all the blather and complaining, nobody has volunteered to
maintain it. And NO, it will not be me.
--Chuck
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
next prev parent reply other threads:[~2002-05-20 9:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-19 14:51 GTK on CYGWIN Torsten Giebl
2002-05-19 15:45 ` Gerrit P. Haase
2002-05-20 4:29 ` S. L.
2002-05-20 4:45 ` GTK on cygwin Christopher Faylor
2002-05-20 5:45 ` S. L.
2002-05-20 6:04 ` Charles Wilson [this message]
2002-05-20 6:05 ` Charles Wilson
2002-05-20 7:56 ` S. L.
2002-05-20 8:06 ` S. L.
2002-05-20 5:55 ` GTK on CYGWIN Gerrit P. Haase
2002-05-20 7:43 ` S. L.
2002-05-20 8:18 ` Gerrit P. Haase
2002-05-19 15:07 Dockeen
2002-05-20 17:54 Nicholas Wourms
2003-11-03 22:57 gtk on cygwin U Fleku
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=3CE8BBEA.7030709@ece.gatech.edu \
--to=cwilson@ece.gatech.edu \
--cc=cygwin@cygwin.com \
/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).