| MinGW or CDT problem? [message #1061903] |
Tue, 04 June 2013 15:37 |
 Mike Henry
Messages: 1
Registered: June 2013 |
Junior Member |
|
|
Hi!
Thanks everybody who are working to make CDT such a great C/C++ development environment!
I am working on a GNU Autotools based C++ project that builds well on Linux and Mac OS X, but which fails on a couple of points on Windows 7 with Eclipse/CDT using MinGW. I have scoured the net in search of a solution but haven't find anything that addresses these problems.
I am not sure whether this is an Eclipse/CDT issue, or a Windows/MinGW issue, but maybe there are knowledgable people here that can point me in the right direction?
1) I use "autoreconf" to generate configure-scripts, Makefiles, etc. When this is done in Eclipse (or directly on the command-line), the result is:
Invoking autoreconf in C:/MinGW/msys/1.0/home/toolshed
sh -c "autoreconf -if"
cvs init: CVSROOT may only specify a positive, non-zero, integer port (not `\MinGW\msys\1.0\home\toolshed\').
cvs init: Perhaps you entered a relative pathname?
cvs [init aborted]: Bad CVSROOT: `C:\MinGW\msys\1.0\home\toolshed\/tmpcvs3904'.
cvs checkout: CVSROOT may only specify a positive, non-zero, integer port (not `\MinGW\msys\1.0\home\toolshed\').
cvs checkout: Perhaps you entered a relative pathname?
cvs [checkout aborted]: Bad CVSROOT: `C:\MinGW\msys\1.0\home\toolshed\/tmpcvs3904'.
FIND: Felaktigt parameterformat
FIND: Felaktigt parameterformat
FIND: Felaktigt parameterformat
autopoint: *** infrastructure files for version 0.18.1 not found; this is autopoint from GNU gettext-tools 0.18.1
autopoint: *** Stop.
autoreconf-2.68: autopoint failed with exit status: 1
If I run the command 'sh -c "autoreconf -if"' in the MSYS shell it succeeds, but not if I run it in Eclipse or CMD.exe. Question is also why 'cvs' is invoked, and why gettext can't be found..?
2) Having run autoreconf manually in MSYS shell the project builds with Eclipse, up until the linking of the executable.
...
/bin/sh ../libtool --tag=CXX --mode=link g++ -g -O2 -o toolshed.exe options.o readline.o toolshed.o main.o /mingw/lib/libintl.dll.a /mingw/lib/libiconv.dll.a -L/mingw/lib ../common/libcommon.la ../debug/libdebug.la ../derivation/libderivation.la ../engine/libengine.la ../machine/libmachine.la
libtool: link: g++ -g -O2 -o .libs/toolshed.exe options.o readline.o toolshed.o main.o /mingw/lib/libintl.dll.a /mingw/lib/libiconv.dll.a -L/mingw/lib ../common/.libs/libcommon.a ../debug/.libs/libdebug.a ../derivation/.libs/libderivation.a ../engine/.libs/libengine.a C:\MinGW/msys/1.0/home/toolshed/derivation/.libs/libderivation.a C:\MinGW/msys/1.0/home/toolshed/machine/.libs/libmachine.a ../machine/.libs/libmachine.a C:\MinGW/msys/1.0/home/toolshed/common/.libs/libcommon.a
g++.exe: error: C:MinGW/msys/1.0/home/toolshed/derivation/.libs/libderivation.a: No such file or directory
make[2]: Leaving directory `/usr/home/toolshed/shell'
make[1]: Leaving directory `/usr/home/toolshed'
g++.exe: error: C:MinGW/msys/1.0/home/toolshed/machine/.libs/libmachine.a: No such file or directory
g++.exe: error: C:MinGW/msys/1.0/home/toolshed/common/.libs/libcommon.a: No such file or directory
make[2]: *** [toolshed.exe] Error 1
make[1]: *** [all-recursive] Error 1
make: *** [all] Error 2
As can be seen, libraries are linked in multiple times, and with erroneous path's. A path with "C:\" gets generated and then stripped, causing the link to fail. Is this an autotools problem or Windows/MinGW problem? This won't link in the MSYS shell either..
Any hints, comments or even solutions are highly appreciated!
Thanks,
-Mike
|
|
|
Powered by
FUDForum. Page generated in 0.03353 seconds
] 
Search
Help
Register
Login
Home
