Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[Cdt-launch-inbox] [Bug 113949] New: C++ Compiler Integration : total lack of "It just works!" philosophy - VERY BAD 
https://bugs.eclipse.org/bugs/show_bug.cgi?id=113949

           Summary: C++ Compiler Integration : total lack of "It just
                    works!" philosophy - VERY BAD
           Product: CDT
           Version: 3.0
          Platform: All
        OS/Version: Windows 2000
            Status: NEW
          Severity: critical
          Priority: P3
         Component: cdt-launch
        AssignedTo: cdt-launch-inbox@xxxxxxxxxxx
        ReportedBy: Timothy.Clutten@xxxxxxxxx


I am a developer with 20 years of C and C++ experience mostly in embedded 
or telecoms.  Eclipse is new to me, so too is CDT.  
This issue is so important that I deliberatly AMPLIFY MY ANGER AND FRUSTRATION,
because many people will simply trash the Eclipse+CDT as another project that
does not work and NOT REPORT THIS BUT TELL THEIR FRIENDS HOW CRAP CDT IS. 

So please do not take my anger personally - and yes I will beta test any
solutions you have - just email me Timothy.Clutten@xxxxxxxxx     OK?

Failure to respond to this will make this IDE a no-hoper even compared with
"C++ Builder" and it can never catch up to Visual Studio or Borland C++.
Respond to this to achieve an automatic, better and sweeter and quicker
integration with existing compilers such as MinGW will remove the angry 
frustration that is associated with a CDT all over the world; a CDT that when
fully installed simply does not compile any C++ or C at all!  That is very very
bad for your image.  

First of all the simplest solution is to cover the most common C++ compilers:
that is GCC on Linux AND MinGW/GCC on Windows and (YES PLEASE) Visual Studio C++
(VS8 beta2)!!!!!! All FREE even Microsoft C++!.    You can:
***  Use automatic integration AND/OR 
***  Provide a CDT+MINGW.zip combined download "READY TO GO".  
***  AND Provide integration support tools for each compiler 
***  AND Provide a CDT compler test script that: compiles, runs and verifies the
output. Thus confirming to the user that they have a basic IDE WITH 
(NOT WITHOUT) A WORKING C++ COMPILER!  
REMEMBER ECLIPSE RUNS A JAVA PROJECT RIGHT OUT OF THE BOX SO WHY NOT A C++ PROJECT?

YOUR CURRENT CDT SOLUTION IS "READY TO FAIL" or "IT WILL FAIL UNLESS YOU KNOW
SOME KIND OF SECRET COMBINATION OF INSTRUCTIONS!".

There is no excuse for not automatically searching for a compiler and when none
is found asking the user - perhaps suggesting to the user a free compiler or a
not so free compiler. Yes there are lots of compilers and lots of platforms but
detection of a compiler at startup OR instilation IS NOT THAT HARD - the user
can guide the install app' a little : given the choice between GCC/MinGW and
intel C++ and Cygwin etc - user choses MinGW - .  CDT then checks to see if
MinGW is usable with a simple test make file (compile and run script)!!! - When
finding it is not usable  getting the user to download the CDT+MinGW.zip that is
READY TO GO. Then at startup running the make file (with the compile and run
script).  OK?   
   
  ** Note also if more than 1 C++ compiler is found CHOSE THE COMPILER PROJECT
BY PROJECT JUST LIKE VS8 CHOSES C# or C++ or Basic or Fortran OR MANAGED or
UNMANAGED .NET  PROJECT-BY-PROJECT ETC!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

This bug report contains several issues, the main issue is the
lack of "It Just Works" for compiler integration especially GCC and MinGW.
Why is this not automatic and where the hell are the instructions to integrate?
Contrast this to "C++ Builder" or Visual Studio Beta2 where you  
install, type in a helloworld.cpp example, compile, run - no problem 
it ALL just works right out of the box!  NOT WITH Eclipse/CDT - NO, BACK TO 1975
and PUNCHING YOUR OWN PUNCH CARDS AND CHANGING SETTINGS BY SWITCHING BANKS OF
STEEL TOGGLE SWITCHES REPRESENTING BIT FLAG CONFIGURATION.  Then in anger
searching the internet for Eclipse C++ integration information.  

Now please email me a work arround to get CDT working because it simply
does not work.  The run and compile all come to DEAD ENDS!  PLEASE NOTE
A WORK ARROUND IS NOT; I REPEAT, IT IS NOT A BUG FIX OR A SOLUTION; 
NO NEVER A BUG FIX.  The idea that It Just Works is miles better because
the whole point of a computer is that it make stuff automatic and saves labor,
saves repetition and saves thousands of angry frustrating hours all over the
world with people all with similar problems.

Environment for C++ develompent:
================================
First of all I was forced to use the cdt.zip to install over the top of
/eclipse/. no instructions or confirmation if doing this is OK. Just dumped it
over the top of exlipse.
Note that the "eclipse search and update" feature is great except javaw.exe must
have permission through the firewall but because it is javaw rather than just an
app no right minded firewall will let that permission happen because to do so
would blow wide open security holes.  PLEASE MAKE THAT FRIENDLY UPDATE PART OF
ECLIPSE.exe and NOT part of javaw.exe (SEPERATE BUGZILLA NUMBER ????).

MinGW installed at C:\MinGW long before eclipse installed. Path set to
C:\MinGW\bin; MinGW bin listing is at the end of this error report.

Created C++ managed make project with simple class (new class)
Created file with main() entry point. 

Error Messages:
===============
NOTE I DO NOT USE CYGWIN SO WHY THE CYGPATH CRAP?
Severity	Description	Resource	In Folder	Location	Creation Time	Id
1	Error launching 'cygpath' command	hello			27 October 2005 10:07:38	4

 Directory of C:\MinGW\bin
===========================
07/09/2005  21:03       <DIR>          .
07/09/2005  21:03       <DIR>          ..
27/08/2005  09:41              456,704 addr2line.exe
27/08/2005  09:40              424,960 ar.exe
27/08/2005  09:42              640,000 as.exe
24/05/2005  09:17               90,624 c++.exe
27/08/2005  09:41              455,168 c++filt.exe
24/05/2005  09:17               90,112 cpp.exe
27/08/2005  09:40              498,688 dlltool.exe
27/08/2005  09:41               32,768 dllwrap.exe
24/05/2005  09:17               90,624 g++.exe
24/05/2005  09:17               88,064 gcc.exe
23/05/2005  20:31               16,580 gccbug
24/05/2005  09:17               26,112 gcov.exe
17/02/2003  09:44            1,814,528 gdb.exe
27/08/2005  09:42              517,120 gprof.exe
27/08/2005  09:43              677,888 ld.exe
23/05/2005  23:00               90,624 mingw32-c++.exe
23/05/2005  23:00               90,624 mingw32-g++.exe
23/05/2005  20:32               88,064 mingw32-gcc-3.4.4
23/05/2005  20:32               88,064 mingw32-gcc.exe
19/06/2003  10:52            1,069,568 mingw32-make.exe
13/08/2005  13:46              763,927 mingwm10.dll
27/08/2005  09:41              467,456 nm.exe
27/08/2005  09:40              601,600 objcopy.exe
27/08/2005  09:40              655,360 objdump.exe
27/08/2005  09:40              424,960 ranlib.exe
27/08/2005  09:41              218,624 readelf.exe
27/08/2005  09:40              410,624 size.exe
27/08/2005  09:40              410,624 strings.exe
27/08/2005  09:41              601,600 strip.exe
04/02/2003  10:09              615,936 tcl84.dll
04/02/2003  10:09               15,360 tcldde12.dll
04/02/2003  10:09                6,656 tclpip84.dll
04/02/2003  10:09               15,360 tclreg11.dll
04/02/2003  09:10               11,264 tclsh84.exe
04/02/2003  11:29              864,768 tk84.dll
27/08/2005  09:41              507,392 windres.exe
04/02/2003  11:29               12,288 wish84.exe
              37 File(s)     13,950,683 bytes
               2 Dir(s)   3,807,502,336 bytes free



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Back to the top