XDE won't compile large applications

[leon_heller]

The XDE stopped working properly the other day on large applications, it's OK on small ones. These are the errors I get:

**** Build of configuration XMOS Compiler Collection (xcc) for project app_xc2_firmware.1v3 ****

xmake all
'cmd' is not recognized as an internal or external command,
operable program or batch file.
xmake: [.build_XC-2/fake_inc] Error 1 (ignored)
'cmd' is not recognized as an internal or external command,
operable program or batch file.
xmake: [.build_XC-2/] Error 1 (ignored)
'cmd' is not recognized as an internal or external command,
operable program or batch file.
xmake: [bin/XC-2/] Error 1 (ignored)
'cmd' is not recognized as an internal or external command,
operable program or batch file.
xmake: [clean_fake_includes] Error 1 (ignored)
Build complete

I've reinstalled the XDE a couple of times. The JRE binaries get deleted each time, and I have had to copy them into their directory each time, which is very strange. I don't remember having that problem before.

A path must have been changed, but reinstalling it should have fixed that.

[Berni]

Now that certainly is a strange bug. Does it do it on a different pc too? If so then its pretty likely its well reproducible so you should raise a ticket about it.

[leon_heller]

I'll raise a ticket. It might have something to do with the disappearing JRE that I mentioned on another thread.

[leon_heller]

Customer Support reckons it's a path conflict with another application, which has caused similar problems for other users. However, I removed all the global paths, rebooted, and still have the problem. :(

[Folknology]

How would a path problem only effect large projects and not small projects?

[leon_heller]

That's what I don't understand!

This is what I get for a large project:

**** Build of configuration XMOS Compiler Collection (xcc) for project app_xc2_firmware.1v3 ****

xmake all
'cmd' is not recognized as an internal or external command,
operable program or batch file.
xmake: [.build_XC-2] Error 1 (ignored)
'cmd' is not recognized as an internal or external command,
operable program or batch file.
xmake: [.build_XC-2/fake_inc] Error 1 (ignored)
Creating dependencies for sw_comps_common.h
The system cannot find the path specified.
Creating dependencies for ethernet_tx_client.h
The system cannot find the path specified.
Creating dependencies for ethernet_rx_client.h
. . .

and this is for a small project:


**** Build of configuration Debug for project XK-1 LED Project ****

xmake all
'Building file: ../src/xk1-led.xc'
'Invoking: XMOS XC Compiler'
xcc -O0 -g -Wall -c -o "src/xk1-led.o" "../src/xk1-led.xc" "../XK-1.xn"
'Finished building: ../src/xk1-led.xc'
' '
'Building target: XK-1LEDProject.xe'
'Invoking: XMOS Mapper'
xcc -Werror=timing-syntax -o "XK-1LEDProject.xe" ./src/xk1-led.o ../XK-1.xn
'Finished building target: XK-1LEDProject.xe'
' '
The small project seems to get compiled differently, the message at the beginning is different.

[bsmithyman]

I wasn't able to find the XC2 firmware online, so I haven't seen its specific file layout. However, don't the projects from XMOS with that naming scheme include extra files (e.g. a makefile)? On the other hand, the XK1 project is created by the XDE when you go through the menu, and so the project configuration parameters should be right for the particular version of the tools installed. Is it possible there's a build script in the XC2 firmware package that is out of date WRT your version of the tools, and is causing problems?

[leon_heller]

I'd deleted everything from my global path, except c:\, in case there was a conflict. Mike at Customer Support mentioned that I needed

C:\Windows;C:\Windows\System32;

as a minimum. I added those, and XDE worked again! They weren't on the path when I started having this problem, so something must have deleted them, I definitely didn't. I'll try adding those to the original path that I've saved in a text file, and pasting that back.

I still don't see why small programs were OK. They would use cmd.exe, in c:\Windows\System32, when being compiled, I'd have thought, which shouldn't have been found when I deleted everything from the path. Windows does some weird things at times!

[bsmithyman]

Huh. Well, I'm glad you got it figured out :)