(ignoring for a moment that MinGW does have autotools)
MinGW does not have automake, you can use automake with MSYS though.
I meant MSYS, sorry... Actually I meant "a real shell" :-)
However, we don't seriously consider building Code::Blocks with MSYS, do we
Why not ? I don't see why it shouldn't (eventually) work
MinGW has no such thing as sed or any other non-compiler-non-linker tool coming with a standard installation. How do you implement parsing svn's output and writing out a header file with gcc, as, and ld being your only tools? Enter autorevision. That was the whole reason why it ever came into existence
You don't, you write a program... C++, Perl, whatever. (no argument there)
And autotools is good for generating e.g. codeblocks.spec and codeblocks.plist, unless you wanted to do those in C++ as well ?
Meknows nothing of specs and plists, but since these are RPM stuff, so Linux only, autotools is of course the right thing to use for that.
They are not RPM/Linux only, they are just text files with a @REVISION@ value that wants to get replaced ?
i.e. codeblocks.spec.in => codeblocks.spec, codeblocks.plist.in => codeblocks.plist, etc. etc.
On a side note, I think the wx-config.cpp addition will be great too.
Great for what? I don't understand what we should need it for (apart from the fact that I was told it does not work)?
Great so that I can use the same
`wx-config --cxxflags --libs` everywhere, without having to write one thing for the GNU tools, one thing for Windows and one thing for Mac OS X ? Too bad that you say it doesn't work, though. (I was really hoping for a solution to my current wxWidgets-on-Windows-without-MSYS problem)