Embedded compilers crach under RTC when project is shared
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 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. |
13 answers
It would appear that this is an issue in the CDT tooling. I am having the same problem using Ruby compilers as well running under RTC 3.0 (Eclipse 3.5.2). Using the DLTK plugin with a Ruby script that executes fine, as soon as I Share it, trying to run it give me an error, "Main script "test/test_foo.rb" path could not be resolved". I have created a Work Item for RTC 3.0 but haven't heard back with a confirmation that the developers have reproduced the issue yet. Comments
Jim Arnow
commented Jun 04 '12, 5:47 p.m.
It turns out this is likely an issue with Eclipse. The Jazz developers and I have created two bugs on bugzilla for the issue: https://bugs.eclipse.org/bugs/show_bug.cgi?id=378703 https://bugs.eclipse.org/bugs/show_bug.cgi?id=378882 |
I do have the same problem trying to work with a IAR compiler.
Any solution or workarround for this problem? Thanks in advance Rodrigo Such |
This is a CDT bug. Jazz Source Control uses a custom filesystem, hence once the project is shared, it changes the location from <workspace> to "sourcecontrol://jazz/default".
org.eclipse.cdt.managedbuilder.internal.buildmodel.BuildDescription ignores this, call's getPath on the location's URI and treats it as a local path.
https://bugs.eclipse.org/bugs/show_bug.cgi?id=423342
|
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.