Wind River Compiling Problem

Technical C/C++
1

Hi,
(Here is another reason why I really want to stop using WindRiver)
So when I was compiling my code on WindRiver, an error similar to this came up:


**building IterativeDemo_partialImage/Debug/Objects/IterativeDemo/IterativeDemo.o**
F:\DOCUME~1\User\LOCALS~1\Temp\make33845.sh: ccppc: command not found
F:\WindRiver\Workbench-3.0\x86-win32\bin\make.exe: ***[IterativeDemo_partialImage/Debug/Objects/IterativeDemo/IterativeDemo.o] Error 127
**Build Failed in Project "IterativeDemo" (Process Exit Value was 2): 2010-04-14 15:17:41 (Elapsed Time: 00:01)**

I think it has something to do with the environmental “PATH” variable…
Has anyone else have this kind of problem?

THANKS!!!

-Masoug

2

Hi,
While I was compiling a project on WindRiver, I saw this error message on the build console:

Build Started in Project ‘IterativeDemo’: 2010-04-14 16:12:52
Generation of makefiles started.
Generation of makefiles finished (Elapsed Time: 00:00).
Platform: Wind River Workbench 3.0
Command: make --no-print-directory BUILD_SPEC=PPC603gnu DEBUG_MODE=1 TRACE=1
Working Directory: F:/Workspace/IterativeDemo/PPC603gnu
if ! -d “dirname "IterativeDemo_partialImage/Debug/Objects/IterativeDemo/IterativeDemo.o"” ]; then mkdir -p “dirname "IterativeDemo_partialImage/Debug/Objects/IterativeDemo/IterativeDemo.o"”; fi;echo “building IterativeDemo_partialImage/Debug/Objects/IterativeDemo/IterativeDemo.o”; ccppc -g -mcpu=603 -mstrict-align -mno-implicit-fp -ansi -Wall -MD -MP -I/target/h/WPILib -I/target/h -I/target/h/wrn/coreip -DCPU=PPC603 -DTOOL_FAMILY=gnu -DTOOL=gnu -D_WRS_KERNEL -o “IterativeDemo_partialImage/Debug/Objects/IterativeDemo/IterativeDemo.o” -c “F:/Workspace/IterativeDemo/IterativeDemo.cpp”
building IterativeDemo_partialImage/Debug/Objects/IterativeDemo/IterativeDemo.o
F:\DOCUME~1\User\LOCALS~1\Temp\make33685.sh: ccppc: command not found
F:\WindRiver\workbench-3.0\x86-win32\bin\make.exe: *** [IterativeDemo_partialImage/Debug/Objects/IterativeDemo/IterativeDemo.o] Error 127
Build Failed in Project ‘IterativeDemo’ (Process Exit Value was 2): 2010-04-14 16:12:53 (Elapsed Time: 00:01)

Did anyone else encounter something similar?
I think it has something to do with the environmental “PATH” variable.

THANKS!!!

-Masoug

3

It looks like the problem is in fact the path. Add the directory of wind river that contains the file ccppc.exe to PATH (google it if you don’t know how) and it should work.

4

Similar threads by same poster merged together.

5

HELP!!! I’m having the exact same error on WindRiver 2014 3.3. When we try to compile, we get:

Build Started in Project ‘SimpleTemplate’: 2014-01-11 15:28:39
Generation of makefiles started.
Generation of makefiles finished (Elapsed Time: 00:00).
Platform: Wind River VxWorks 6.3
Command: make --no-print-directory BUILD_SPEC=PPC603gnu DEBUG_MODE=1 TRACE=1
Working Directory: C:/WindRiver/workspace/SimpleTemplate/PPC603gnu
if ! -d “dirname "SimpleTemplate_partialImage/Debug/Objects/SimpleTemplate/MyRobot.o"” ]; then mkdir -p “dirname "SimpleTemplate_partialImage/Debug/Objects/SimpleTemplate/MyRobot.o"”; fi;echo “building SimpleTemplate_partialImage/Debug/Objects/SimpleTemplate/MyRobot.o”; ccppc -g -mcpu=603 -mstrict-align -mno-implicit-fp -mlongcall -ansi -Wall -MD -MP -mlongcall -IC:/WindRiver/vxworks-6.3/target/h -IC:/WindRiver/vxworks-6.3/target/h/WPILib -IC:/WindRiver/vxworks-6.3/target/h/wrn/coreip -DCPU=PPC603 -DTOOL_FAMILY=gnu -DTOOL=gnu -D_WRS_KERNEL -o “SimpleTemplate_partialImage/Debug/Objects/SimpleTemplate/MyRobot.o” -c “C:/WindRiver/workspace/SimpleTemplate/MyRobot.cpp”
building SimpleTemplate_partialImage/Debug/Objects/SimpleTemplate/MyRobot.o
(null) tried to spawn get_feature but failed: The system cannot find the file specified.
C:\WindRiver\vxworks-6.3\host\x86-win32\bin\make.exe: *** [SimpleTemplate_partialImage/Debug/Objects/SimpleTemplate/MyRobot.o] Error 1
Build Failed in Project ‘SimpleTemplate’ (Process Exit Value was 2): 2014-01-11 15:28:39 (Elapsed Time: 00:00)

We’ve tried adding the make to the PATH and cleaning and rebuilding. Does anyone else have any advice? This is the first time we’ve tried running WindRiver on this computer also, so could it be the installation process went wrong somehow? And yes we installed both discs.

6

WindRiver is quirky like that; that’s why I usually use makefiles manually. For the time being though, try re-installing WindRiver and running its demos.

It might be worth trying UCPP: https://github.com/nikitakit/ucpp - It automagically creates makefiles for you to build projects with.

7

ok, thanks. I know my makefile is good so I’m just gonna reinstall WindRiver. Darn :confused: that’s a great use of a saturday…