Hallo,

We are using different other C/C++ embedded compilers like IAR under
eclipse 3.6 or 3.7 as a plug-in
1) Every time we share a project our
project with RTC SCM and we build a project, give eclipse us a error
message that he can't find the /default/xxxx directory.

Errors occurred during the build.
Errors running builder 'CDT Builder' on project 'test001'.
Cannot find build output folder: /default/test001/Release

The '/Default' path is confusing with the project (we don't have any
path like this in our project)

2) Also when the project was shared with RTC and we modify the source
code. When we build the project, the compiler says that there was
noting changed.

We have informated the different companies of this issue and they says
that the problem is comming from RTC. They has also tell me that he
has the same issue with the GNU compiler for eclipse (MinGW-4.4.1).

So who can help me to resolve this issue.

btw: when we using SVN or CVT than we don't have more error messages
or compilation problems.

Here we explain how you can simulate the issue:

We have used eclipse Indigo 3.7 with the RTC 3.0.1 plug-in.

For what concerns the RTC compatibility issue: The essential problem
that I found is that when building using the Internal Builder, the
current working directory is changed to
/default/<proj>/<config>. So, any tool which is
invoked will operate in an invalid folder.

This is because RTC installs its own Eclipse file system extension
(EFS), which uses URIs with a custom protocol to access files (e.g.
sourcecontrol://jazz/default/HelloWorldGcc2/src/HelloWorldGcc2.c).


As far as I could see, the RTC file system extension is not compatible
with the CDT Internal builder.
An easily reproducible test case is to build a project using GCC:

* Using Eclipse Version: Indigo Service Release 1 Build id:
20110916-0149, with CDT 8.0.1 installed.
* Install MinGW gcc tools for Windows as described in CDT help:
http://help.eclipse.org/indigo/index.jsp
* Create a new C project using the MinGW GCC toolchain and the
Hello World ANSI C Project template (from C/C++ perspective,
use File> New> C Project> Executable> Hello World
ANSI C Project and MinGW GCC)
* Verify that the project builds correctly
* Share the project using RTC (Right click on project> Team
Share project> Jazz Source Control)
* Clean the project and verify that the rm tool results in an
error similar to:

rm -rf
C:/default/HelloWorldGcc2/Debug/src/HelloWorldGcc2.d
C:/eclipseTests/eclipse-cpp-indigo-SR1-incubation-win32-RTC/eclipse/workspace/HelloWorldGcc2/Debug/HelloWorldGcc2.exe
C:/eclipseTests/eclipse-cpp-indigo-SR1-incubation-win32-RTC/eclipse/workspace/HelloWorldGcc2/Debug/src/HelloWorldGcc2.o
Error: Cannot run program "rm": The directory name is
invalid.

* Build the project and verify that the following error is displayed
in the build console:

**** Rebuild of configuration Debug for project HelloWorldGcc2 ****

**** Internal Builder is used for build ****
gcc -O0 -g3 -Wall -c -fmessage-length=0 -o
C:\default\HelloWorldGcc2\Debug\src\HelloWorldGcc2.o
C:\eclipseTests\eclipse-cpp-indigo-SR1-incubation-win32-RTC\eclipse\workspace\HelloWorldGcc2\src\HelloWorldGcc2.c
Error: Cannot run program "gcc": The directory name is
invalid.

Build error occurred, build is stopped
Time consumed: 41 ms.

* Disconnect the project from source control (Right click on project
Team> Disconnect)
* Build the project and you can seen that the build now works

We also encoutered this problem.

I did some testing and it seems to occur only in combination with the
Eclipse Indigo release. When testing using RTC in combination with
Eclipse Helios the problem did not occur.

Should we submit a work-item or will this be closed anyway because
Indigo is officially not supported yet ?

Daan.