Eclipse Community Forums: C / C++ IDE (CDT) » Exec error: Launching failed

Home » Language IDEs » C / C++ IDE (CDT) » Exec error: Launching failed

Exec error: Launching failed [message #82757]

Thu, 09 October 2003 21:40

Eclipse User

Originally posted by: john.mlist.arrizza.com

I just created by second eclipse project. First one went beautifully after I
added mingw to the PATH.

Second project got the same error "Exec error: Launching failed". Hmmm.

It looks like I have to add "mingw32-make -f makefile" to the Build Command
under projects for every single project I ever write.

Is there a way to set these kind of properties to my own defaults once and
for all?

Thanks,
John

---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.521 / Virus Database: 319 - Release Date: 9/23/2003

Re: Exec error: Launching failed [message #83017 is a reply to message #82757]

Tue, 14 October 2003 19:34

Eclipse User

Originally posted by: alain.nowhere.com

JohnA wrote:

> I just created by second eclipse project. First one went beautifully after I
> added mingw to the PATH.

> Second project got the same error "Exec error: Launching failed". Hmmm.

> It looks like I have to add "mingw32-make -f makefile" to the Build Command
> under projects for every single project I ever write.

> Is there a way to set these kind of properties to my own defaults once and
> for all?

You do not have to set "-f makefile" by default any posix
make should look for "makefile, Makefile" in this order of course
for case insensitive file system ... it is the same file 8-)

Set in your User profile the path to the mingwin/cygwin tools
The problem is that Runtime.getRuntime().exec("mingw32-make ...")
failed, since there is probably no "mingw32-make" in the default path.

Somebody on this newsgroup was also saying that you have to set
the DLL path for cygwin etc ...

Re: Exec error: Launching failed [message #83078 is a reply to message #83017]

Wed, 15 October 2003 00:48

Eclipse User

Originally posted by: john.mlist.arrizza.com

I believe I've cloudied the issue, my question is:
I have to add the "mingw32-make" every time I create a *new* project. Is
there any way to make this my default build command?

That way I create a new project and the build command is automatically set
to "mingw32-make" for me.

JohnA

"alain" <alain@nowhere.com> wrote in message
news:bmi166$omn$1@eclipse.org...
> You do not have to set "-f makefile" by default any posix
> make should look for "makefile, Makefile" in this order of course
> for case insensitive file system ... it is the same file 8-)
Aaah yes, Win32 is grand.

> Set in your User profile the path to the mingwin/cygwin tools
> The problem is that Runtime.getRuntime().exec("mingw32-make ...")
> failed, since there is probably no "mingw32-make" in the default path.
Did this.

> Somebody on this newsgroup was also saying that you have to set
> the DLL path for cygwin etc ...
Didn't need to do this.

---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.525 / Virus Database: 322 - Release Date: 10/9/2003

Re: Exec error: Launching failed [message #83123 is a reply to message #83078]

Wed, 15 October 2003 09:48

Eclipse User

For standard make project see
"Window->Preferences->C/C++->New Make Projects"
you can specify the defaults for new project here.

JohnA wrote:
> I believe I've cloudied the issue, my question is:
> I have to add the "mingw32-make" every time I create a *new* project. Is
> there any way to make this my default build command?
>
> That way I create a new project and the build command is automatically set
> to "mingw32-make" for me.
>
> JohnA
>
> "alain" <alain@nowhere.com> wrote in message
> news:bmi166$omn$1@eclipse.org...
>
>>You do not have to set "-f makefile" by default any posix
>>make should look for "makefile, Makefile" in this order of course
>>for case insensitive file system ... it is the same file 8-)
>
> Aaah yes, Win32 is grand.
>
>
>>Set in your User profile the path to the mingwin/cygwin tools
>>The problem is that Runtime.getRuntime().exec("mingw32-make ...")
>>failed, since there is probably no "mingw32-make" in the default path.
>
> Did this.
>
>
>>Somebody on this newsgroup was also saying that you have to set
>>the DLL path for cygwin etc ...
>
> Didn't need to do this.
>
>
>
>
> ---
> Outgoing mail is certified Virus Free.
> Checked by AVG anti-virus system (http://www.grisoft.com).
> Version: 6.0.525 / Virus Database: 322 - Release Date: 10/9/2003
>
>

Re: Exec error: Launching failed [message #83267 is a reply to message #83123]

Wed, 15 October 2003 20:31

Eclipse User

Originally posted by: john.mlist.arrizza.com

"David Inglis" <dinglis@qnx.com> wrote in message
news:bmjj5s$54n$1@eclipse.org...
> For standard make project see
> "Window->Preferences->C/C++->New Make Projects"
> you can specify the defaults for new project here.

Thanks.

It seems that "New Make Projects" is not under C/C++.
I'm using eclipse 2.1.1 and CDT 1.1.0, are you using something newer?

John

---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.525 / Virus Database: 322 - Release Date: 10/10/2003

Re: Exec error: Launching failed [message #83296 is a reply to message #83267]

Wed, 15 October 2003 21:09

Eclipse User

Originally posted by: alain.nowhere.ca

JohnA wrote:

> "David Inglis" <dinglis@qnx.com> wrote in message
> news:bmjj5s$54n$1@eclipse.org...
> > For standard make project see
> > "Window->Preferences->C/C++->New Make Projects"
> > you can specify the defaults for new project here.

> Thanks.

> It seems that "New Make Projects" is not under C/C++.
> I'm using eclipse 2.1.1 and CDT 1.1.0, are you using something newer?

Yes, CDT-1.2
RC0, RC1, ... etc was out
The GA should be on its way.

Previous Topic:	Scanner Exceptions in Make Project - 1.2RC0
Next Topic:	Eclipse 3, Tomcat 4.1, SYSDEO Plugin problem

Goto Forum:

-=] Back to Top [=-

Current Time: Sat Apr 26 00:03:44 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter