|
Prev: wxGraphicsContext and wxAutoBufferedPaintDC
Next: [wx 2.8.7, WinXP, MinGW-5.1.3 & Msys 1.0] unable to create makefile with configure
From: Vadim Zeitlin on 6 May 2008 18:00 On Tue, 06 May 2008 21:12:40 +0200 Lars Uffmann <aral(a)nurfuerspam.de> wrote: LU> Before I publicly post my guide, I wanted to ask you for permission to LU> mention you guys in the credits, and because I used a couple of LU> instructions from the wxWiki to understand the process myself. There is no problem referring anything I wrote in any of the public mailing lists or newsgroups, although I'd prefer if people didn't do it when I write something wrong ;-) LU> Can I mail you my current version somewhere (tomorrow) so you know what LU> I'm talking about? I'm not sure if I have the time to read and understand it (I don't use Eclipse myself so it risks to be difficult) but you could just put it on the wxWiki (wiki.wxwidgets.org) where people would be able to comment on and correct it in the future. Regards, VZ -- TT-Solutions: wxWidgets consultancy and technical support http://www.tt-solutions.com/
From: Bryan Petty on 7 May 2008 13:11 On Wed, May 7, 2008 at 2:34 AM, Lars Uffmann <aral(a)nurfuerspam.de> wrote: > Good idea, however, there is already a guide for exactly this configuration > there. Mine is just easier and more detailed :) (But also probably less > general). > For example, I invoke the MSYS shell to call compiler and linker, which > means I get to use the wx--config call in backticks, which the existing > guide hasn't. > I also put emphasis on using as few configuration tweaks as possible, i.e. > the user does not have to add any libraries for the linker manually. > > I guess I'll just put an alternative guide in the same section. Disclaimer: I haven't read or followed either of the two guides mentioned. If your guide uses most of the same tools, compiler, etc, is a much more robust and easier to follow guide, and is more up to date, then it's more than appropriate to replace the old guide entirely. If it does use a different set of development tools, or provides an alternate approach where both work, but both provide the ability to do something that the other doesn't, then they should remain as separate guides. It's fine if there's multiple guides on the wiki, even if it is for the same compiler. I also just wanted to note that there is a "Preview" button while editing the wiki. Please make use of it before saving your edits. It's really hard to review your changes when you've made over 100 edits to the same article, and most of them are changes to a single word or a single line. Thanks for your work. Regards, Bryan Petty
From: Bryan Petty on 7 May 2008 14:16
On Wed, May 7, 2008 at 1:40 PM, Lars Uffmann <aral(a)nurfuerspam.de> wrote: > Will know better next time. Is one save operation per section okay? Yes, that is fine, thanks. We just have to review changes to make sure no-one is defacing or spamming the wiki, and it also gives us a chance to spot areas that could be improved before it sees more viewers. Regards, Bryan Petty |