[GRASS-dev] Make/Configure Issue using Eclipse/Windows

[Glynn Clements]

peter.loewe at gmx.de wrote:

> > > I am trying to get GRASS compiled in a Eclipse/CDT environment on a
> > Windows machine.
> > > The approach includes wrapping the "configure / make /make install"
> > -process in an ant file and works very well behaved on linux boxes.
> > > 
> > > On a windows box (using msys) "something" is going wrong regarding the
> > header files. This is the first error produced by make, the follow-up errors
> > are similar:
> > > 
> > > 
> > > 
> > >      [exec] gcc
> > >      -I/d/Nutzer/ploewe/workspace/neo63/dist.i686-pc-mingw32/include
> > >      -IC:\msys\1.0\local\include -g -O2 -IC:\msys\1.0\local\include
> > >      -DPACKAGE=\""grasslibs"\" -D_FILE_OFFSET_BITS=64
> > >      -DPACKAGE=\""grasslibs"\"
> > >      -I/d/Nutzer/ploewe/workspace/neo63/dist.i686-pc-mingw32/include
> > >      -o OBJ.i686-pc-mingw32/auto_mask.o -c auto_mask.c
> > >      [exec] In file included from auto_mask.c:17:
> > >      [exec] G.h:2:23: rpc/types.h: No such file or directory
> > >      [exec] G.h:3:21: rpc/xdr.h: No such file or directory
> > >      [exec] In file included from auto_mask.c:17:
> > >      [exec] G.h:42: error: syntax error before "XDR"
> > >      [exec] G.h:42: warning: no semicolon at end of struct or union
> > >      [exec] G.h:47: error: syntax error before '}' token
> > >      [exec] make[3]: *** [OBJ.i686-pc-mingw32/auto_mask.o] Error 1
> > > 
> > > The GRASS sources have been downloaded from the SVN, so all files are
> > available. 
> > > 
> > > Suggestions, anyone ?
> > 
> > Did you perform this step:
> > 
> > 	http://www.webalice.it/marco.pasetti/grass/BuildFromSource.html#Xdr
> > 
> > I.e. does C:\msys\1.0\local\include\rpc\ exist?
> > 
> 
> Yes it does.

How are the MSys paths getting there, and how are they used?

If the command line is being parsed by a Unix-style shell, the
backslash characters will be "eaten", and probably need to be forward
slashes instead, i.e. "C:/msys/...". You may even need to use e.g. 
"/c/msys/..." instead of "C:". If MSys' bash shell is being used, the
path should just be "/usr/local/include".

OTOH, if MSys' bash shell *isn't* being used, then /d/Nutzer/... 
probably won't work; Windows itself isn't going to understand that
path.

-- 
Glynn Clements <glynn at gclements.plus.com>