Re: [wxCode-users] wxCode-users Digest, Vol 38, Issue 2

[Francesco <f18...@ya...>]

Hi,

2010/5/8 sdfkjsjlh sdbfgsfsdg <sdf...@ya...>:
>>> 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'm quite sure the one I got are VS2008 (the sln file is called
mmwx_vc2008.sln and when I open it in VS2008 it does not ask for
conversion).
You should be able to generate them as well unless bakefile_gen gives
you some errors.

>>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?
yes

>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?
then just add the line

 <set var="WX_VERSION_DEFAULT">28</set>

just before inclusion of wxcode presets (and re-run bakefile_gen).


>>> 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. ;-)
that's not really a pain (just download wx and run "nmake -f
makefile.vc" in its build\msw folder) but anyway if you don't want to
set it up, then I suspect you will never be able to build something
wx-based against wx with MSVC: MSVC has many settings (like those
related to CRT linking) which must match among all libraries you link
to and that may be difficult to do if you want to use a wx build
compiled by gcc/something else.

>>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.
all my components already build in Unicode as I always use wxtrunk...
anyway I agree Unicode compatibility is really something that each
maintainer should carefully look at.

>>> 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.
if you open an MSDOS prompt, and you add to your PATH env var the
Mingw installation folder\bin, then you can run  the command
"mingw32-make -f makefile.gcc" to use MinGW without using neither MSYS
nor Cygwin.

>>> 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.
no, that's not the same thing... the fact you can run wx's own
configure script only means that you have a shell interpreter which
runs ok.
To be able to _create_ (and not just _run_) a configure script (like
mmwx's one) you'll need additional utilities (IIRC autoconf, aclocal,
automake).
Once you have recreated the configure script of mmwx, you'll be able
to run it even if you uninstall aclocal, autoconf and automake.

>>> 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.
not necessarily. Another suggestion I usually give is to avoid MSYS.
Either use mingw32-make or Cygwin. Msys is an intermediate solution
which always gave me too many troubles.

> So, to summarise, the only Windows build files provided are for VS. Is that
> right?
no. Bakefile can be used with wx-based apps to produce all the following:

    autoconf      GNU autoconf Makefile.in files
    borland       Borland C/C++ makefiles
    gnu           GNU toolchain makefiles (Unix)
    mingw         MinGW makefiles (mingw32-make)
    msvc          MS Visual C++ nmake makefiles
    msvc6prj      MS Visual C++ 6.0 project files
    msvs2003prj   MS Visual Studio 2003 project files
    msvs2005prj   MS Visual Studio 2005 project files
    msvs2008prj   MS Visual Studio 2008 project files
    watcom        OpenWatcom makefiles

> Secondly, can you provide any info. regarding what I'm going to need to do
> to build things with MSys and Code::Blocks?
1) install aclocal,autoconf,automake
2) regen your configure script
3) run it under msys
4) run make

I've never used Code::Blocks so I don't really know how its build
system works...sorry.

> 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.
it would be nice to have not only bakefile wxpresets but something
similar also for CMake and premake, indeed.
I think that if you're so much motivated to produce them, other wxdevs
will agree on putting them in the main wx trunk tree.

> As you've probably guessed, I haven't spent a lot of time with command line
> builds.
yes, but you never posted your bakefile_gen log and the log you posted
about kwic is not really a problem in the makefile but rather in
kwic's sources.

>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. ;-)
For me it's quite easy to get bakefile running, but I can understand
that it maybe difficult for someone which never used it.
If it was for me, bakefile also would have a much faster development
cycle and better docs but unfortunately I have no access to bakefile
svn...

HTH,
Francesco