Skip to main content



      Home
Home » Language IDEs » C / C++ IDE (CDT) » Configuration - CDT and Cygwin
Configuration - CDT and Cygwin [message #140910] Tue, 15 March 2005 18:56 Go to next message
Eclipse UserFriend
Originally posted by: me.my.com

I've seen my problem posed in many places, and various answers given, some
of which worked for the OP but that don't for me.

I've installed the Eclipse Platform SDK 3.0.1 on a Win98 machine that has
Cygwin installed. Over this I've added CDT 2.1.

I've set up my C:\Cygwin\bin in first spot on my path in my autoexec.bat
file (remember those? ;-)). Cygwin all works fine from a shell - MSDos or
BASH - however, no matter how many - and I mean many - things I have tried
already, I just can't get Eclipse then to 'see' it on the path.

Everything's where it needs to be on my system, the cygwin bin is on the
path, yet Eclipse falters at startup with 'cygwin1.dll' not found. Then,
when it starts up and I work through creating a managed-make project, it's
no surprise that it fails with errors: echo command not found, rm not
found, that kind of stuff.

It's all there in the bin, however, and the bin's on the path, and . . .

At the moment I'm looking at how bash manages (converts) this path. In
DOS, it starts

PATH=C:\CYGWIN\BIN;C:\WINDOWS;C:\WINDOWS\COMMAND;C:\OLDMSDOS , etc.

Then, from bash, this becomes

PATH='/usr/bin:/cygdrive/c/WINDOWS:/cygdrive/c/WINDOWS/COMMA ND:/cygdrive/c/OLDM
SDOS, etc.

And it seems to be this conversion that is part of the problem. The other
elements of the path /cygdrive/c/Windows all function properly, and I've
been trying to get a way to have the Cygwin bin in the path rendered also
as /cygdrive/c/Cygwin/bin, and I've achieved this in a roundabout way, but
it still doesn't work.

And I can't figure out either how it seems, during a build, to be able to
find make all right, it's just that after that make can find the rest of
the stuff it needs.

This has had well over a week of my time already, and I've just about run
dry of new ideas.

How I wish Eclipse just had a property field where you specified your
Cygwin (etc) path, and that was it.

Any working solution would be gladly received, however much of a
workaround it might be.

Cheers

PB
Re: Configuration - CDT and Cygwin [message #140921 is a reply to message #140910] Tue, 15 March 2005 20:22 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: ddaoust.ca.ibm.com

In the CDT FAQ it states that CDT will not run on Windows98

http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/cdt- home/user/faq.html?cvsroot=Tools_Project#general_60

- Dave


"Shaq" <me@my.com> wrote in message news:d17smg$f26$1@www.eclipse.org...
> I've seen my problem posed in many places, and various answers given, some
> of which worked for the OP but that don't for me.
>
> I've installed the Eclipse Platform SDK 3.0.1 on a Win98 machine that has
> Cygwin installed. Over this I've added CDT 2.1.
>
> I've set up my C:\Cygwin\bin in first spot on my path in my autoexec.bat
> file (remember those? ;-)). Cygwin all works fine from a shell - MSDos or
> BASH - however, no matter how many - and I mean many - things I have tried
> already, I just can't get Eclipse then to 'see' it on the path.
>
> Everything's where it needs to be on my system, the cygwin bin is on the
> path, yet Eclipse falters at startup with 'cygwin1.dll' not found. Then,
> when it starts up and I work through creating a managed-make project, it's
> no surprise that it fails with errors: echo command not found, rm not
> found, that kind of stuff.
>
> It's all there in the bin, however, and the bin's on the path, and . . .
>
> At the moment I'm looking at how bash manages (converts) this path. In
> DOS, it starts
>
> PATH=C:\CYGWIN\BIN;C:\WINDOWS;C:\WINDOWS\COMMAND;C:\OLDMSDOS , etc.
>
> Then, from bash, this becomes
>
>
PATH='/usr/bin:/cygdrive/c/WINDOWS:/cygdrive/c/WINDOWS/COMMA ND:/cygdrive/c/O
LDM
> SDOS, etc.
>
> And it seems to be this conversion that is part of the problem. The other
> elements of the path /cygdrive/c/Windows all function properly, and I've
> been trying to get a way to have the Cygwin bin in the path rendered also
> as /cygdrive/c/Cygwin/bin, and I've achieved this in a roundabout way, but
> it still doesn't work.
>
> And I can't figure out either how it seems, during a build, to be able to
> find make all right, it's just that after that make can find the rest of
> the stuff it needs.
>
> This has had well over a week of my time already, and I've just about run
> dry of new ideas.
>
> How I wish Eclipse just had a property field where you specified your
> Cygwin (etc) path, and that was it.
>
> Any working solution would be gladly received, however much of a
> workaround it might be.
>
> Cheers
>
> PB
>
>
Re: Configuration - CDT and Cygwin [message #140952 is a reply to message #140921] Wed, 16 March 2005 04:39 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: me.my.com

Well that solves that one, David. Many thanks. It'll teach me not to read
the FAQ properly. Having said that, I have managed to get it to work of a
fashion with MinGW. It can't handle the managed makes, and I have to use
absolute paths in the makefile, but I have at least got some simple
programs to build and run.

PB

David Daoust wrote:

> In the CDT FAQ it states that CDT will not run on Windows98

>
http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/cdt- home/user/faq.html?cvsroot=Tools_Project#general_60

> - Dave
Re: Configuration - CDT and Cygwin [message #140985 is a reply to message #140910] Wed, 16 March 2005 08:18 Go to previous message
Eclipse UserFriend
Originally posted by: Serge.Iovleff.univ-lille1.fr

I have the same configuration. I solve partly the problem.
If the first time you want to compile (make all), you have the message "g++ command not found" error...
- save your work, exit the platform
- launch the platform again, compile
- this should work !

If you launch a C/C++ application from the platform, you will experiment a 'cygwin1.dll' not found
the only way I found is to copy the cygwin1.dll in the project.

Serge

Shaq a écrit :
> I've seen my problem posed in many places, and various answers given,
> some of which worked for the OP but that don't for me.
>
> I've installed the Eclipse Platform SDK 3.0.1 on a Win98 machine that
> has Cygwin installed. Over this I've added CDT 2.1.
> I've set up my C:\Cygwin\bin in first spot on my path in my autoexec.bat
> file (remember those? ;-)). Cygwin all works fine from a shell - MSDos
> or BASH - however, no matter how many - and I mean many - things I have
> tried already, I just can't get Eclipse then to 'see' it on the path.
>
> Everything's where it needs to be on my system, the cygwin bin is on the
> path, yet Eclipse falters at startup with 'cygwin1.dll' not found. Then,
> when it starts up and I work through creating a managed-make project,
> it's no surprise that it fails with errors: echo command not found, rm
> not found, that kind of stuff.
>
> It's all there in the bin, however, and the bin's on the path, and . . .
> At the moment I'm looking at how bash manages (converts) this path. In
> DOS, it starts
> PATH=C:\CYGWIN\BIN;C:\WINDOWS;C:\WINDOWS\COMMAND;C:\OLDMSDOS , etc.
>
> Then, from bash, this becomes
>
> PATH='/usr/bin:/cygdrive/c/WINDOWS:/cygdrive/c/WINDOWS/COMMA ND:/cygdrive/c/OLDM
>
> SDOS, etc.
>
> And it seems to be this conversion that is part of the problem. The
> other elements of the path /cygdrive/c/Windows all function properly,
> and I've been trying to get a way to have the Cygwin bin in the path
> rendered also as /cygdrive/c/Cygwin/bin, and I've achieved this in a
> roundabout way, but it still doesn't work.
>
> And I can't figure out either how it seems, during a build, to be able
> to find make all right, it's just that after that make can find the rest
> of the stuff it needs.
>
> This has had well over a week of my time already, and I've just about
> run dry of new ideas.
>
> How I wish Eclipse just had a property field where you specified your
> Cygwin (etc) path, and that was it.
>
> Any working solution would be gladly received, however much of a
> workaround it might be.
>
> Cheers
>
> PB
>
>
Previous Topic:Help: ld: cannot find -l.... any library
Next Topic:Noob: Build Error (Exec error:Launching failed)
Goto Forum:
  


Current Time: Sun Jul 27 12:55:49 EDT 2025

Powered by FUDForum. Page generated in 0.04515 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top