Eclipse Community Forums: C / C++ IDE (CDT)

Home » Language IDEs » C / C++ IDE (CDT) » cdt 2.0M5 RC1?

Wed, 26 November 2003 09:29

Eclipse User

Hi,

I tried newly released cdt 2.0M5-RC1 with Eclipse 3.0M5. However, there
were a few problems on the process.

1. why org.eclipse.cdt.win32_2.0.0 is finding cdt 1.2? I did clean
installation after deleting previous version of Eclipse and cdt, so I had
no file of cdt 1.2. I saw the product configuration window from Help >
Software updates > Manage Configuration menu of Eclipse. There were a 'not
loaded' mark on 'Eclipse CDT (Windows) 2.0.0'. this item had a subitem of
'Eclipse CDT 1.2.0'. I wonder whether this is right or not. I tried to
modify 1.2.0 to 2.0.0 referring to error log file in my workspace. I
changed two files of features/org.eclipse.cdt.win32_2.0.0/features.xml and
plugins/org.eclipse.cdt.core.win32_2.0.0/fragment.xml. Then the unloaded
mark is disappered and 'Eclipse CDT (Windows) 2.0.0' items can be enabled.
But I don't make sure all works fine.

2. When I make a managed C project and build a helloworld.c file, which
contains only a printf function, then it seems that execution file cannot
be made such as helloworld.exe in release folder. I have an error message
on the way of building like this:

Build error
(Exec error:Launching failed)

I used MinGW on WinXP. This is my environment.

Eclipse: 3.0M5
Eclipse path: C:/GNU/Eclipse
MinGW: 3.1.0-1
MinGW path: C:/GNU/MinGW/bin
MSYS: 1.0.10-rc2
MSYS path: C:/GNU/msys/1.0/bin

Also the last two paths are in %PATH% of Windows environment variable.
When I tried simply 'gcc helloworld.c' on command window, it makes the
a.exe and the file works well.

I did all of configuration procedure in CDT tutorial, but I couldn't
obtain a executable file in Eclipse. I had also tried them in Eclipse
2.1.2 with CDT 1.2.0 with same MinGW packages before and confirmed that
exe file is produced well.
I don't know this is a bug of new CDT or Eclipse.

Thoughts?

Sincerely,

Leo.

Re: cdt 2.0M5 RC1? [message #87541 is a reply to message #87451]

Thu, 27 November 2003 17:21

Eclipse User

Originally posted by: dschaefe.ca.ibm.com

Hi,

Problem number one has been fixed in the new build.

Problem number two points out that the build command failed. Try opening a
DOS window and executing the build command there (probably 'make').

Thanks,
Doug

Jin-serk Baik wrote:

>
> Hi,
>
> I tried newly released cdt 2.0M5-RC1 with Eclipse 3.0M5. However, there
> were a few problems on the process.
>
> 1. why org.eclipse.cdt.win32_2.0.0 is finding cdt 1.2? I did clean
> installation after deleting previous version of Eclipse and cdt, so I had
> no file of cdt 1.2. I saw the product configuration window from Help >
> Software updates > Manage Configuration menu of Eclipse. There were a 'not
> loaded' mark on 'Eclipse CDT (Windows) 2.0.0'. this item had a subitem of
> 'Eclipse CDT 1.2.0'. I wonder whether this is right or not. I tried to
> modify 1.2.0 to 2.0.0 referring to error log file in my workspace. I
> changed two files of features/org.eclipse.cdt.win32_2.0.0/features.xml and
> plugins/org.eclipse.cdt.core.win32_2.0.0/fragment.xml. Then the unloaded
> mark is disappered and 'Eclipse CDT (Windows) 2.0.0' items can be enabled.
> But I don't make sure all works fine.
>
> 2. When I make a managed C project and build a helloworld.c file, which
> contains only a printf function, then it seems that execution file cannot
> be made such as helloworld.exe in release folder. I have an error message
> on the way of building like this:
>
> Build error
> (Exec error:Launching failed)
>
> I used MinGW on WinXP. This is my environment.
>
> Eclipse: 3.0M5
> Eclipse path: C:/GNU/Eclipse
> MinGW: 3.1.0-1
> MinGW path: C:/GNU/MinGW/bin
> MSYS: 1.0.10-rc2
> MSYS path: C:/GNU/msys/1.0/bin
>
> Also the last two paths are in %PATH% of Windows environment variable.
> When I tried simply 'gcc helloworld.c' on command window, it makes the
> a.exe and the file works well.
>
> I did all of configuration procedure in CDT tutorial, but I couldn't
> obtain a executable file in Eclipse. I had also tried them in Eclipse
> 2.1.2 with CDT 1.2.0 with same MinGW packages before and confirmed that
> exe file is produced well.
> I don't know this is a bug of new CDT or Eclipse.
>
>
> Thoughts?
>
>
> Sincerely,
>
> Leo.

Re: cdt 2.0M5 RC1? [message #87629 is a reply to message #87541]

Fri, 28 November 2003 01:44

Eclipse User

Doug Schaefer wrote:

> Hi,

> Problem number one has been fixed in the new build.

> Problem number two points out that the build command failed. Try opening a
> DOS window and executing the build command there (probably 'make').

> Thanks,
> Doug

Thank you. I tried newer version of CDT2.0M5. There was no problem in
compiling a helloworld code. but I found other some problems yet.

1. When I see the Product Configuration in Eclipse3.0, "Eclipse C/C++
Development Tools (Windows) 2.0.0" item is also not configured properly.
When I see the status of that item, it told the reason 'No plug-in:
"org.eclipse.cdt.core.win32" included at runtime.' However, the cdt itself
seems to work fine.

2. When I tried the Eclipse 3.0M5 and CDT 2.0M5 on Windows 2003 Enterprise
server, eclipse can't find gcc. I can't understand why, because gcc and
make works properly in the command window. %PATH% variable also has gcc
and make directory. I tried 'make all' in the release directory of
helloworld project in my workspace, and the compilation make a good exe
file. However, in eclipse, the phenomenon was not changed. on Windows XP
it works fine. What's the different between the OS? I also know eclipse is
not supported on Windows server 2003, however, I guess the bug can be
easily modified.

The message on 'problems' window on eclipse is following:

Severity Description Resource In Folder Location
*** [helloworld.o] Error 127 helloworld line -1

do you have any idea about that line number -1?

I tested them on these conditions:
OS: Windows Server 2003 Enterprise edition
Eclipse : 3.0 M5
Eclipse path: C:\GNU\Eclipse
CDT : 2.0 M5
MinGW : 3.1.0-1
MinGW path: C:\GNU\MinGW\bin
MSYS : 1.0.10-rc2
MSYS path : C:\GNU\msys\1.0\bin

I hope your help once again. Thank you.

Re: cdt 2.0M5 RC1? [message #87678 is a reply to message #87629]

Fri, 28 November 2003 05:22

Eclipse User

Rather paste the output of the C-Build View then the task entry.

Jin-serk Baik schrieb:
> Doug Schaefer wrote:
>
>
>>Hi,
>
>
>>Problem number one has been fixed in the new build.
>
>
>>Problem number two points out that the build command failed. Try opening a
>>DOS window and executing the build command there (probably 'make').
>
>
>>Thanks,
>>Doug
>
>
>
>
> Thank you. I tried newer version of CDT2.0M5. There was no problem in
> compiling a helloworld code. but I found other some problems yet.
>
> 1. When I see the Product Configuration in Eclipse3.0, "Eclipse C/C++
> Development Tools (Windows) 2.0.0" item is also not configured properly.
> When I see the status of that item, it told the reason 'No plug-in:
> "org.eclipse.cdt.core.win32" included at runtime.' However, the cdt itself
> seems to work fine.
>
> 2. When I tried the Eclipse 3.0M5 and CDT 2.0M5 on Windows 2003 Enterprise
> server, eclipse can't find gcc. I can't understand why, because gcc and
> make works properly in the command window. %PATH% variable also has gcc
> and make directory. I tried 'make all' in the release directory of
> helloworld project in my workspace, and the compilation make a good exe
> file. However, in eclipse, the phenomenon was not changed. on Windows XP
> it works fine. What's the different between the OS? I also know eclipse is
> not supported on Windows server 2003, however, I guess the bug can be
> easily modified.
>
> The message on 'problems' window on eclipse is following:
>
> Severity Description Resource In Folder Location
> *** [helloworld.o] Error 127 helloworld line -1
>
> do you have any idea about that line number -1?
>
> I tested them on these conditions:
> OS: Windows Server 2003 Enterprise edition
> Eclipse : 3.0 M5
> Eclipse path: C:\GNU\Eclipse
> CDT : 2.0 M5
> MinGW : 3.1.0-1
> MinGW path: C:\GNU\MinGW\bin
> MSYS : 1.0.10-rc2
> MSYS path : C:\GNU\msys\1.0\bin
>
>
> I hope your help once again. Thank you.
>
>
>
>
>

Re: cdt 2.0M5 RC1? [message #87708 is a reply to message #87678]

Fri, 28 November 2003 06:15

Eclipse User

This is the copy of C-Build view.

make all
make: gcc: Command not found
make: *** [helloworld.o] Error 127
gcc -O3 -gstabs -Wall -c -o helloworld.o ../helloworld.c
Build complete for project helloworld

As looking the messages itself, it seems that the path environment doesn't
have the gcc path. However, when I tried 'make all' in command window, I
can obtain a exe file without any error message.

Sincerely,

Leo

Henning Riedel wrote:

> Rather paste the output of the C-Build View then the task entry.

Re: cdt 2.0M5 RC1? [message #87722 is a reply to message #87708]

Fri, 28 November 2003 08:10

Eclipse User

Go into a console window, and call "set PATH".

Are the MinGW and msys paths really listed?
There should be C:/MinGW/bin and C:/msys/1.0/bin listed.

Check your MinGW installation. Restart Eclipse after setting/changing your PATH
variable,
since started appliactions do not get new path settings forwarded.

Jin-serk Baik schrieb:
> This is the copy of C-Build view.
>
> make all
> make: gcc: Command not found
> make: *** [helloworld.o] Error 127
> gcc -O3 -gstabs -Wall -c -o helloworld.o ../helloworld.c
> Build complete for project helloworld
>
>
> As looking the messages itself, it seems that the path environment doesn't
> have the gcc path. However, when I tried 'make all' in command window, I
> can obtain a exe file without any error message.
>
>
> Sincerely,
>
> Leo
>
>
>
> Henning Riedel wrote:
>
>
>>Rather paste the output of the C-Build View then the task entry.
>
>
>
>

Re: cdt 2.0M5 RC1? [message #87738 is a reply to message #87722]

Fri, 28 November 2003 07:42

Eclipse User

As I wrote, I already checked them.
I think that eclipse or cdt don't understand path variable on windows
server 2003.

I tried reinstallation of MinGW or Eclipse or CDT several times.
All trials show the same result.

Henning Riedel wrote:

> Go into a console window, and call "set PATH".

> Are the MinGW and msys paths really listed?
> There should be C:/MinGW/bin and C:/msys/1.0/bin listed.

> Check your MinGW installation. Restart Eclipse after setting/changing your
PATH
> variable,
> since started appliactions do not get new path settings forwarded.

Re: cdt 2.0M5 RC1? [message #87753 is a reply to message #87738]

Fri, 28 November 2003 09:25

Eclipse User

Maybe you can try setting the paths with backslashs instead of slashs?
C:\MinGW\bin instead of C:/MinGW/bin.
And try to set them system wide instead of User specific. In my Win2k there are two
fields. I got the feeling setting them in the top (per User) does not update the
system wide (maybe until reboot).

I don't think, that setting PATHs in Win2k3 is anything really different than in
Win2k!

Jin-serk Baik schrieb:
> As I wrote, I already checked them.
> I think that eclipse or cdt don't understand path variable on windows
> server 2003.
>
> I tried reinstallation of MinGW or Eclipse or CDT several times.
> All trials show the same result.
>
>
>
> Henning Riedel wrote:
>
>
>>Go into a console window, and call "set PATH".
>
>
>>Are the MinGW and msys paths really listed?
>>There should be C:/MinGW/bin and C:/msys/1.0/bin listed.
>
>
>>Check your MinGW installation. Restart Eclipse after setting/changing your
>
> PATH
>
>>variable,
>>since started appliactions do not get new path settings forwarded.
>
>
>
>

Re: cdt 2.0M5 RC1? [message #87776 is a reply to message #87753]

Fri, 28 November 2003 08:51

Eclipse User

I really appreciate your kind replies. I agree what you thought. But, I
have tried several tests on Win2k3. Also I tried backslashs instead of
slashs, and vice versa. And, system wide variable are also tried (PATH
variable is not a user specific but system wide).
I can't think what should I do more. :~(

Henning Riedel wrote:

> Maybe you can try setting the paths with backslashs instead of slashs?
> C:MinGWbin instead of C:/MinGW/bin.
> And try to set them system wide instead of User specific. In my Win2k there
are two
> fields. I got the feeling setting them in the top (per User) does not update
the
> system wide (maybe until reboot).

> I don't think, that setting PATHs in Win2k3 is anything really different
than in
> Win2k!

Re: cdt 2.0M5 RC1? [message #87823 is a reply to message #87776]

Fri, 28 November 2003 11:36

Eclipse User

Hi,

I haven't tried on Win2K3, but have you tried a good ol' fashioned reboot
since updating your Path? Maybe the old version of the path is still
persisting
somewhere, and Eclipse is getting the old path...

Just a thought,

- Brent

"Jin-serk Baik" <leo@photonet.kaist.ac.kr> wrote in message
news:bq7jto$ar$1@eclipse.org...
> I really appreciate your kind replies. I agree what you thought. But, I
> have tried several tests on Win2k3. Also I tried backslashs instead of
> slashs, and vice versa. And, system wide variable are also tried (PATH
> variable is not a user specific but system wide).
> I can't think what should I do more. :~(
>
>
> Henning Riedel wrote:
>
> > Maybe you can try setting the paths with backslashs instead of slashs?
> > C:MinGWbin instead of C:/MinGW/bin.
> > And try to set them system wide instead of User specific. In my Win2k
there
> are two
> > fields. I got the feeling setting them in the top (per User) does not
update
> the
> > system wide (maybe until reboot).
>
> > I don't think, that setting PATHs in Win2k3 is anything really different
> than in
> > Win2k!
>
>
>
>

Re: cdt 2.0M5 RC1? -- I found what's wrong!!!!! [message #87838 is a reply to message #87776]

Fri, 28 November 2003 11:58

Eclipse User

I found what's wrong.

Eclipse can't understand the %PATH% variable of which values is over 255
characters.

When I reduce the length of PATH value, cdt works fine. No problem in
compilation.

I think this is a bug of eclipse or cdt, isn't this?

Previous Topic:	content assist in C++ editor
Next Topic:	CDT forget a little

Goto Forum:

-=] Back to Top [=-

Current Time: Sat Jul 26 18:37:09 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter