Re: why the switch to wxWindows 2.5?

Vadim Zeitlin <[email protected]>
Newsgroups gmane.mail.mahogany.user
Message-ID <[email protected]>
On Sat, 31 Jan 2004 15:13:55 -0500 Brian Sammon <[email protected]> wrote:

BS> Is there an explanation posted somewhere of why the developers decided
BS> to move mahogany development to the beta release of wxWindows?

 No, but it's really very simple: some new features need support present
only in 2.5.

BS> As someone who is very reluctant to switch to a beta version of
BS> wxWindows

 You can perfectly well have 2.5 alongside with 2.4. In fact, I still have
all of 2.2, 2.4 and 2.5 installed here.

BS> This is a major change.  I think this merits a larger change in the
BS> version number and mention on the website (which would have saved me
BS> the wasted time of downloading a 3 MB file I won't use)

 Here is how you can use it without doing anything to your existing 2.4
installation (I assume you're using wxGTK under Unix):

1. download wxGTK 2.5 or get it from the cvs and put it in, say,
   /usr/local/src/wxWindows
2. cd /usr/local/src/wxWindows; mkdir gtk; cd gtk
3. ../configure --whatever-options-you-need-but-usually-nothing
4. make but do *not* make install
5. cd /usr/local/src/mahogany-0.66; mkdir gtk; cd gtk
6. ../configure --with-wxdir=/usr/local/src/wxWindows/gtk
7. make && make install as usual

 If you experience any problems you should rebuild with debug, that is use
the following steps instead:

2'. mkdir gtk-debug; cd gtk-debug
3'. ../configure --enable-debug
...
5'. mkdir gtk-debug; cd gtk-debug
6'. ../configure --with-wxdir=/usr/local/src/wxWindows/gtk-debug --enable-debug

 HTH,
VZ



-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.