On Thu, Jan 1, 2009 at 5:47 PM, Brandon Van Every <bvanev...@gmail.com> wrote:
> On Thu, Jan 1, 2009 at 11:05 AM, Brandon Van Every <bvanev...@gmail.com> 
> wrote:
> I tried MSYS again, starting Eclipse from inside MSYS.  The Eclipse
> Autotools plugin simply doesn't work properly with it.  It calls out
> to sh using ordinary Windows pathnames.  The \ are eliminated as the
> arguments are passed, resulting in errors.  Bottom line is the Eclipse
> Autotools plugin is not ready for prime time with MSYS.  I'm going to
> try building Freeciv outside of Eclipse, then just debugging the final
> installed civclient.exe.  At this point I'm really only trying to
> trace Freeciv to see how it works.
> Running config.status
> sh C:\Users\bvanevery\workspace\freemsys\build\config.status
> C:\Users\bvanevery\workspace\freemsys\build\config.status: line 890:
> cd: C:Usersbvaneveryworkspacefreemsys: No such file or directory
> C:\Users\bvanevery\workspace\freemsys\build\config.status: line 891:
> cd: C:Usersbvaneveryworkspacefreemsys: No such file or directory
> config.status: creating Makefile
> config.status: error: cannot find input file: Makefile.in
> Configuration failed with error

I investigated this problem and created a ticket with possible patches
for the Autotools plugin at the eclipse.org bug tracker:


An easy way to work around this problem (without patching the
Autotools plugin) with MSYS 1.0.11 is to define


in the Project Properties (Properties->C/C++ Build->Settings->Tool
Settings->configure->Features and
packages->User specified configuration options)

Or you could use my MinGW toolchain from january this year:


It still contains MSYS 1.0.10 which comes with a dirname.exe that is
broken, but that for this reason also prevents the problems with the
colons and the backslashes when trying to build Freeciv. With a
separate build directory inside the source directory the PWD variable
needs to be undefined in the Project Properties. When building
directly in the source directory this step is not necessary.

Freeciv-dev mailing list

Reply via email to