Build Managment: Eclipse Project and Eclipse Managed Make Project

Question

I develop on Windows and use Eclipse with CDT to develop C ++ applications.

Now, to manage the build, I can create a regular C ++ project , and Eclipse can handle the build completely (by invoking the g ++ compiler with the correct arguments), or I can create a Managed Make C ++ project , and Eclipse will manage the Makefile, and then call make on this Makefile (when creating the project), which in turn will complete the build process.

Is there any advantage to using one of these approaches rather than the other?

EDIT : I'm not talking about Managed Make vs Standard Make, but rather I'm talking about Make vs Eclipse. Yesterday I tried to compile a C ++ project under eclipse on a system that does not include Make at all, and the project compiled perfectly, which means that eclipse can fully control its assembly, which introduces the main question: do I need to do it ?; I can only use eclipse.

What is my question ...

Answer 1

: , , , Eclipse? Eclipse, . ++ Java/Eclipse, . Eclipse, Eclipse .

. , ++ die-hards, , Make , (heh) .

Answer 2

, ++, Managed Make ++ make ( , make ). , - , CLI.

, , makefile CDT. , make , Eclipse make .

Answer 3

CDT4.0, . Standard Make .

CDT 4.0.

cdt4.0 changelog, .

Answer 4

/ - , make

Answer 5

IMO, .
, Make ( cygwin/mingw). , - Eclipse Eclipse, . , ( ), , . , Make.

Answer 6

. , Eclipse. Make ( make), . make ( ).

Eclipse . (.. / ), , make .

On the other hand: if it is a development with one or two persons, Eclipse CDT supports accelerated work, since you can skip the installation of a time file that requires a lot of time.