> From: John Vandenberg <jayvdb@...>
> On 8/10/05, Charlie Savage <cfis@...> wrote:
> > Hi John,
> > Ah, I see. What confused the issue in my mind is that I originally =
> > the bug when running a make file from the Eclipse IDE (using the C++
> > support). So msys was nowhere in site. But upon further =
> > Eclipse is running the msys version of make, not a mingw version of
> > make. Thus what you say below applies.
> CDT looks interesting. What version of CDT are you using: 2.1.1 or
> CDT 3.0 - RC3 ? Have you tried both? What is the open source project
> you are trying to build using CDT? Has this project already been
> tested to work using the same set of tools you have installed (e.g.
> versions of said project, CDT, msys, eclipse, mingw; roughly in order
> of relevance)? (sorry about the 20 questions! :)
> I would expect CDT works for others, so maybe your local configuration
> is causing the problem, or if nobody else has tried using that
> particular open source project with CDT on Windows, maybe the project
> makefiles need a bit of tweaking to work around this problem. As Tor
> has pointed out, it is strange that the same physical location is
> being duplicated in the linker paths using both DOS and Unix =
> The relevent project mailing list may be able to help more.
CDT 2.1.1 works for me in Eclipse 3.1, using MinGW directly (i.e., no
msys). I haven't actually tried using msys, it just seemed unnatural
somehow to have msys things called by native apps, rather than in the
msys shell window. I did have to change the name of the make command
to "mingw32-make" from "make," though. I also checked "PE Windows
Parser" in the "binary parsers" tab, fwiw. Simple projects, hand-
written Makefiles, MinGW 4.1.1.