| Issues with CDT 4.0 for Eclipse 3.3RC2 [message #192341] |
Thu, 31 May 2007 11:04  |
Eclipse User |
|
|
|
Originally posted by: unidentified.nomail.com
Greetings,
I faced a lot of problems getting the CDT to work with projects.
1. Build configurations are not inheritable.
Severity: Major
Details:
Build configurations are physically separate modules currently.
Sharing common settings can become cumbersome.
Solution:
Make child configurations inherit from parent configurations.
Master Configuration
|
+-----------------------------------------+-----------...
| |
Release Configuration Debug Configuration ...
2. GNU code formatting rules are incorrect (no spaces, incorrect
indentation, etc.)
Severity: Minor
Example formatted code:
int main(int argc, char *argv[])
{
GtkWidget *window= NULL;
gtk_init (&argc, &argv);
window = gtk_window_new (GTK_WINDOW_TOPLEVEL);
g_signal_connect(G_OBJECT (window), "destroy",
G_CALLBACK (gtk_main_quit), NULL);
gtk_widget_show (window);
gtk_main ();
return EXIT_SUCCESS;
}
Incorrect use of spaces, which the GNU guidelines disallow.
Outermost blocks are never indented one level deep.
Only second level and inner blocks are indented.
GtkWidget *window=NULL;
looks better as
GtkWidget *window = NULL;
Notice the space between window and =.
3. Usability issues with build configuration preferences.
Severity: Major
Problem:
One has to add each library and include directory entry separately
per configuration per project without sharing configuration owing
to the current structure of build configurations and the User
Interface provided. Clicking + to add a single library is a very
*bad* idea. Projects can have hundreds of linker libraries.
No user is going to sit and click + to add each library per
configuration per project.
The CDT should allow editing the entire command line,
which it does not currently.
Suggested Example:
The GTK+ 2.0 libraries. CDT could read the required libraries
and include directories by parsing the output of these commands:
pkg-config --cflags gtk+-2.0
and
pkg-config --libs gtk+-2.0
Adding each of those parameters per configuration, per project
separately is a MAJOR PITA.
4. Header comments code template issue (incorrect file extension for C
template).
Severity: Minor
Problem:
Look at this header comment for a *C* source file created from
a template.
/*
============================================================ ================
Name : Hello.cpp
Author : Yesudeep
Version :
Copyright : Your copyright notice
Description : Hello World in C, Ansi-style
============================================================ ================
*/
The name of the file is Hello.c, yet the file name in the header
comment contains Hello.cpp, which is the name of a C++ source
file.
5. Older version projects do not support autocompletion even after
migration.
Severity: Minor
Problem:
I migrated a sample project from an earlier version of CDT
to CDT 4.0 when CDT prompted me to do so. End result:
No autocomplete available.
I'm digging into it more and will definitely find more issues.
The CDT is far from ready for public release, IMHO.
Regards,
Yesudeep.
|
|
|
| Re: Issues with CDT 4.0 for Eclipse 3.3RC2 [message #192348 is a reply to message #192341] |
Thu, 31 May 2007 11:33  |
| Eclipse User |
|
|
|
I would encourage you to file Bugzilla entries for the issues you found.
Regards,
===========================
Chris Recoskie
Team Lead, IBM CDT Team
IBM Toronto
http://www.eclipse.org/cdt
Yesudeep Mangalapilly wrote:
> Greetings,
>
> I faced a lot of problems getting the CDT to work with projects.
>
> 1. Build configurations are not inheritable.
>
> Severity: Major
>
> Details:
> Build configurations are physically separate modules currently.
> Sharing common settings can become cumbersome.
>
> Solution:
> Make child configurations inherit from parent configurations.
>
> Master Configuration
>
> |
> +-----------------------------------------+-----------...
> | |
> Release Configuration Debug Configuration ...
>
> 2. GNU code formatting rules are incorrect (no spaces, incorrect
> indentation, etc.)
>
> Severity: Minor
>
> Example formatted code:
>
> int main(int argc, char *argv[])
> {
> GtkWidget *window= NULL;
>
> gtk_init (&argc, &argv);
>
> window = gtk_window_new (GTK_WINDOW_TOPLEVEL);
>
> g_signal_connect(G_OBJECT (window), "destroy",
> G_CALLBACK (gtk_main_quit), NULL);
>
> gtk_widget_show (window);
>
> gtk_main ();
>
> return EXIT_SUCCESS;
> }
>
> Incorrect use of spaces, which the GNU guidelines disallow.
> Outermost blocks are never indented one level deep.
> Only second level and inner blocks are indented.
>
> GtkWidget *window=NULL;
>
> looks better as
>
> GtkWidget *window = NULL;
>
> Notice the space between window and =.
>
>
> 3. Usability issues with build configuration preferences.
>
> Severity: Major
>
> Problem:
> One has to add each library and include directory entry separately
> per configuration per project without sharing configuration owing
> to the current structure of build configurations and the User
> Interface provided. Clicking + to add a single library is a very
> *bad* idea. Projects can have hundreds of linker libraries.
> No user is going to sit and click + to add each library per
> configuration per project.
>
> The CDT should allow editing the entire command line,
> which it does not currently.
>
>
> Suggested Example:
> The GTK+ 2.0 libraries. CDT could read the required libraries
> and include directories by parsing the output of these commands:
>
> pkg-config --cflags gtk+-2.0
>
> and
>
> pkg-config --libs gtk+-2.0
>
> Adding each of those parameters per configuration, per project
> separately is a MAJOR PITA.
>
>
> 4. Header comments code template issue (incorrect file extension for C
> template).
> Severity: Minor
>
> Problem:
> Look at this header comment for a *C* source file created from
> a template.
> /*
>
> ============================================================ ================
>
> Name : Hello.cpp
> Author : Yesudeep
> Version :
> Copyright : Your copyright notice
> Description : Hello World in C, Ansi-style
>
> ============================================================ ================
>
> */
>
> The name of the file is Hello.c, yet the file name in the header
> comment contains Hello.cpp, which is the name of a C++ source
> file.
>
> 5. Older version projects do not support autocompletion even after
> migration.
> Severity: Minor
>
> Problem:
> I migrated a sample project from an earlier version of CDT
> to CDT 4.0 when CDT prompted me to do so. End result:
> No autocomplete available.
>
>
> I'm digging into it more and will definitely find more issues.
> The CDT is far from ready for public release, IMHO.
>
> Regards,
> Yesudeep.
|
|
|
Powered by
FUDForum. Page generated in 0.04868 seconds
Home