From: Jonathan Naylor <jonathan.naylor@ggaweb.ch>
To: Linux Hams <linux-hams@vger.kernel.org>
Subject: Re: wxGTK-2.4.0
Date: Wed, 15 Jan 2003 22:12:05 +0100 [thread overview]
Message-ID: <200301152212.05203.jonathan.naylor@ggaweb.ch> (raw)
Hi again
I've had a very enjoyable day building different version of wxGTK-2.4.0
and building LinWSJT and finding what does and doesn't work with it !
LinWSJT does work with wxGTK-2.4.0 but not with all build types:
It will work with wxGTK-2.4.0 built with GTK+ 1.x.y (in my case 1.2.10),
this is achieved by using "./configure --with-gtk" for wxGTK.
It will sort of work with wxGTK-2.4.0 and GTK+ 2 (in my case 2.2.0) but
without Unicode support by "./configure --with-gtk --enable-gtk2". When
I means "sort of works", I mean that the numbers on the spectrum graph
(the square graph on the right) do not appear, but otherwise FSK441
operates correctly, JT44 is perfectly OK.
The currently released LinWSJT will not build as Unicode, the next
release is Unicode compliant but suffers from the same problems as
above. I think this is a bug in wsGTK-2.4.0 and I will report it to the
bug tracking database. If I build wxGTK for debugging I get an
assertion failure when dealing with Pango.
So I recommend using wxGTK-2.4.0 with GTK+ 1.x.y and you should be fine,
of course you may have to install pkg-config to get it to build in the
first place.
Jonathan HB9DRD/G4KLX
next reply other threads:[~2003-01-15 21:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-15 21:12 Jonathan Naylor [this message]
2003-01-16 10:33 ` wxGTK-2.4.0 (3) Wilbert Knol
2003-01-16 10:52 ` Wilbert Knol
-- strict thread matches above, loose matches on Subject: below --
2003-01-23 12:05 wxGTK-2.4.0 Jonathan Naylor
2003-01-14 21:04 wxGTK-2.4.0 Jonathan Naylor
2003-01-14 9:50 wxGTK-2.4.0 Wilbert Knol
2003-01-14 12:12 ` wxGTK-2.4.0 Aleksandar Ilic
2003-01-14 12:19 ` wxGTK-2.4.0 Tomi Manninen
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=200301152212.05203.jonathan.naylor@ggaweb.ch \
--to=jonathan.naylor@ggaweb.ch \
--cc=g4klx@qsl.net \
--cc=linux-hams@vger.kernel.org \
/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