this file is generated automatically on each time you run configure.
It is fine to keep the config.w32.h.in as dummy template (it is not
used), so we have a file in cvs with all possible values, just like a
autoconf's configurefile.
Ah no, you've misunderstood it. The config.w32.h.in file is
On Mon, Jul 7, 2008 at 3:18 PM, Steph Fox [EMAIL PROTECTED] wrote:
this file is generated automatically on each time you run configure.
It is fine to keep the config.w32.h.in as dummy template (it is not
used), so we have a file in cvs with all possible values, just like a
autoconf's
I will update the js again and add some comments to avoid confusions
in the future (HEAD and 5.3, please also apply any of your commits to
both branches).
Eh, just the one leetle old laptop with not much space or memory. One day
5.3, next day HEAD. I don't mind doing my own MFB, it's just
On Mon, 31 Mar 2008, Marcus Boerger wrote:
Monday, March 31, 2008, 5:09:23 PM, you wrote:
On Mon, 31 Mar 2008, Marcus Boerger wrote:
this doesn't work! When allowing to wotk with 0.13.3 then you will end up
in a broken .c. Since we have the stuff checked in there really is no need
