OS X Eclipse C++ Launch Failed - Binary Not Found

Question

I am quite troubled as this shouldn\'t be causing me such a headache. I\'ve downloaded the most recent Eclipse Indigo and all CDT C++ plugins for MAC OS X 10.7.1/<

Answer 1

I was having the same problem. The answer can be hard to find as the "binary not found" issue has cropped up several times before, with different causes and solutions (selecting the 64-bit parser, etc.).

It turns out that, in my case, the fix was simple: you have to do a manual build, just once, for every new project you create. After that, works as usual.

Details: using a fresh fresh install of Eclipse Indigo Service Release 1 on Mac OS 10.7.2.

Answer 2

I had the same problem, even when i had set the artifact to executable. It was because the shared lib setting was ticked and this causes a dylib to be made even though you have specified an executable.

Answer 3

For those of you that are new to programming/eclipse/IDEs and get the same error but the solutions above don't work, I solved my "Launch Failed. Binary Not Found." error by doing the following: Simply be sure to build your project ("Project" > "Build All") before attempting to run or debug. I was thinking that the IDE would do the building when I clicked debug or run, but that is not the case (obviously, in retrospect). Newbie lesson learned. Once you build you should see a "Binaries" and "Debug" folder under the root directory of the project.

I was using OS X 10.7.3, if it matters, though I assume the mistake I made is fundamental and any eclipse distro would give the same error.

Answer 4

I go this to run by setting the Builder Type to Internal Builder on the C/C++ Build tab, in the project properties dialog.

Answer 5

I had the similar issue but code was different. In File.h file make sure

virtual ~Destructor () {}; //Don't forget Curly braces {}

Above statement shows destructor initialized () and defined with curly braces { } . In my code I forgot to define Destructor. Hope this helps

Answer 6

No matter which approach to take to solve this issue on your workspace, this problem seemed to have become native to the project that I had created. Neither using the arguments or making sure the gcc version for linking did not work. I did find an intuitive solution. Here it is:to the "...binary not available..." error. Do the following:(remember the following steps are after you have taken either of the above routes and none of those have solved the issue.

1.) delete everything - the project and the files. 2.) create new project and source files