Hi Francesco,
Thanks for responding.
>> It doesn't even create
>> VS2008 projects. How can it be so far out of date?
>it does generate them. I tried running bakefile_gen in components\mmwx
>and I got MSVS 2008 project files... which bakefile version are you
>using? do you get errors when running bakefile_gen?
No, it creates vc8 files, which I think you'll find are VS2005 files. VS2008 is
VS9. The first thing VS2008 does is convert the project/solution to the latest
version.
Bakefile 0.28.
>I just had to add a line "<set var="USE_UNSTABLE_VERSION">1</set>"
>just before "<include file="presets/wxcode.bkl"/>" in mmwx.bkl to make
>it work (and that's not related to VS08 but rather to the fact that
>the wx default version is currently set to 29 which is the "unstable"
>branch).
Right. I'll give that a try but it looks like that would tell it to use the
unstable version, would it? That's not what I need. I'm using 2.8.10, as are
most wx users, as 2.9 is still experimental.
Having the option is great but I suggest that defaulting to that is a bad idea.
Either way, how do I use 2.8.10?
>> I have VS but don't have
>> a suitable wx build.
>sorry, I'm not sure to understand what you mean here... can you
>explain it better?
I don't have a version of wx set up in, or built by, VS and I don't intend to
go through the pain necessary to get there. ;-)
>>I tried running configure and make but that fails and
>> seems to be configured for unix paths.
>configure needs to run on Linux/Unix/Mac/Cygwin/MSYS environments, not
>on Windows... that's why configure uses / as path separator.
I've built wx in Windows using configure, make, make install many times. You
have to use a Unix command line, of course. In this case it was MSys.
I'm not referring to separators, I'm referring to the fact that it was looking
for user/local/lib or whatever it was.
>>If I do "mingw32-make makefile.gcc"
>> it fails. For example,when run on the kwic package:
>>
>> $ mingw32-make.exe ./makefile.gcc all
>> mingw32-make: Nothing to be done for `makefile.gcc'.
>> g++ -c -o gccmsw/kwic_lib_slider.o -O0 -g -W -Wall -I../include `wx-config
>> --cx
>> flags --debug=yes --unicode=yes --static=yes --toolkit=msw --version=2.8`
>> -MT
>> ccmsw/kwic_lib_slider.o -MF`echo gccmsw/kwic_lib_slider.o | sed -e
>> 's,\.o$,.d,'
>> ?-MD ../src/slider.cpp
>> ../src/slider.cpp: In member function 'void
>> kwxLinearReg::DrawLimits(wxDC&)':
>> ../src/slider.cpp:354: error: no matching function for call to
>> 'wxString::Print
>> (const char [3], int&)'
>this kind of error is because you are building against a Unicode build
>of wxWidgets and kwic component does not seem to be Unicode-aware (it
>does not use wxT() probably).
Really? Well I'll have to fix that. wx itself defaults to Unicode and, from 2.9
IIRC, it's enforced. However, there a numerous builds available for kwic and
half of them are unicode builds. Perhaps I need to specifify a different one.
>> Note that I always get "Nothing to be done for `makefile.gcc'." even if
>> other activity follows. That looks like a bug.
>not a bug, it's just that makefile.gcc is very misleading.
>makefile.gcc should be used _only_ with MinGW, not with MSYS or
>Cygwin.
>We could change its name to "makefile.mingw" but then it would be
>confusing to have wxWidgets' mingw makefile named "makefile.gcc" and
>wxCode ones named "makefile.mingw"...
I don't now what this means. How can you run MinGW without MSys or Cygwin? MSys
is the execution environment provided WITH MinGW.
>> When I try to build mmwx the same way it just hangs. I suspect this is
>> because I can't run the final step in the tute, which is acregen.sh. That
>> fails with:
>>
>> $ ./acregen.sh
>> ./acregen.sh: line 24: aclocal: command not found
>I don't remember if MSYS ships with aclocal but you need to install it
>if you want to run acregen.sh...
My point is that I can run the configure/make sequence to build wx so I'm sure
I have it. It might be one of the other issues above that's causing problems so
I think I need to sort that out first.
>> I'd appreciate it if someone could download the SVN and have a look. Why
>> would acregen fail? I build wx with configure and make successfully.
>acregen.sh needs additional tools to update the configure script... if
>you cannot install them through MSYS (and you really want to use GCC
>also on Windows -- I strongly suggest you to use VS2008 on Windows)
>I'd suggest to go with Cygwin which surely allows to install them.
That's never going to happen. I need to be able to build with Code::Blocks. One
option might be to create the projects with premake which, unlike bakefile,
supports Code::Blocks and others.
I will definitely need some help to understand what's required to do that,
though. The other requirement is that I, and others, can build it with MinGW,
which I would say means MSys.
So, to summarise, the only Windows build files provided are for VS. Is that
right?
Secondly, can you provide any info. regarding what I'm going to need to do to
build things with MSys and Code::Blocks?
Meanwhile, I'll see if there is some way to import bakefile setup files into
premake. That would be very nice. Anything I come up with will be donated back
to help broaden wxCode's user base.
As you've probably guessed, I haven't spent a lot of time with command line
builds. I don't mind knowing how to get around it when I have to but doing it
as a matter of course drives me nuts.
That's 60s technology and not good enough for me these days. ;-)
All help appreciated.
Cheers,
Gary.
------------------------------------------------------------------------------
_______________________________________________
wxCode-users mailing list
wxCode-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wxcode-users
