|
|
|
|
|
|
|
Project building failure with EE 1.4.3 (1 viewing) (1) Guests
Favoured: 0
|
|
|
TOPIC: Project building failure with EE 1.4.3
|
icserny (User)
Fresh Boarder
Posts: 9
|
|
Project building failure with EE 1.4.3 2 Months, 3 Weeks ago
|
Karma: 0  
|
|
Hi,
I installed Erika Enterprise 1.4.3 for dsPIC30 and tried to build one of sample projects for the demo board Explorer 16. Following the instructions in the Tutorial everything went smoothly, except of the building of the project. I've got the following error message.
Error launching external scanner info generator (gcc -E -P -v -dD C:/Evidence/workspace/._meta_data/.plugins/org.eclipse.cdt.make.core/specs.cpp) test1 -1 C/C++ Problem
This looks a bit strange for me, because the compiler is called pic30-gcc, not just gcc. And the file mentioned above (._meta_data/.plugins/org.eclipse.cdt.make.core/specs.cpp) contains just an empty line (single character of 0x0A). So does the file specs.c as well...
I tried to specify the MPLAB C30 compiler first, and after seeing the above problem I tried to use the EE gcc but the result was the same.
How can I elmiminate this problem, and compile the demo project?
|
|
|
|
|
|
|
The administrator has disabled public write access. |
|
|
|
Re:Project building failure with EE 1.4.3 2 Months, 3 Weeks ago
|
Karma: 4  
|
|
Hi...
We are getting this error too... but it seems not harmful at all.
in particular, take a look in the console, and check if the pic30.cof has been generated under the Debug directory.
The problem seems to be related to the CDT plugin trying to use gcc to get something done, but the executable gcc is not available by default in Eclipse... Maybe we should change something in the CDT, but I guess it is not so urgent...
Ciao,
PJ
|
|
|
|
|
|
|
The administrator has disabled public write access. |
icserny (User)
Fresh Boarder
Posts: 9
|
|
Re:Project building failure with EE 1.4.3 2 Months, 3 Weeks ago
|
Karma: 0  
|
|
Hi Paolo,
The problem is that the build procedure stops at the very beginning so pic30.cof is trivially not created.
The project wizard created files .cproject, .project, code.c and conf.oil.
Then rtdruid_launcher.bat created the Debug directory and files eecfg.c, eecfg.h and makefile.
The make just says: MAKE_DIRECTORIES (after a clean)
This happens also if I start mymake_cygwin.bat manually. So I guess, that the compiler is not started at all. Running make with the debug flag, it seems, that a lof of files are not found at all.
I attach here the debug output of make which may help to understand the situation.
BTW the path for the compiler is c:Program FilesMicrochipC30 in my case, which seems to be correctly reflected in the makefile.
Thank you for your reply!
|
|
|
|
|
|
|
The administrator has disabled public write access. |
icserny (User)
Fresh Boarder
Posts: 9
|
|
Re:Project building failure with EE 1.4.3 2 Months, 3 Weeks ago
|
Karma: 0  
|
Sorry, the file was too large to attach it, so I provide here _link_s to it and for the makefile as well: makefiledebug.txt
|
|
|
|
|
|
|
The administrator has disabled public write access. |
|
|
|
Re:Project building failure with EE 1.4.3 2 Months, 3 Weeks ago
|
Karma: 4  
|
|
Hi...
I see that the default directory specified in the makefile is "C:\Program Files\Microchip\C30" . On my machine is "C:\Program Files\Microchip\MPLAB C30". Did you installed the compiler in a different location or maybe you need to change the pathname?
Also, try to remove the Debug directory and rebuild. It often helps when dependency files are messed up...
PJ
|
|
|
|
|
|
|
The administrator has disabled public write access. |
icserny (User)
Fresh Boarder
Posts: 9
|
|
Re:Project building failure with EE 1.4.3 2 Months, 3 Weeks ago
|
Karma: 0  
|
|
Did you installed the compiler in a different location? Yes, so the C:Program FilesMicrochipC30 pathname is correct in my case.
Also, try to remove the Debug directory and rebuild. I've already tried it (several times).
I think, that the problem is here (see in debug.txt): Looking for an implicit rule for `/cygdrive/c/PROGRA~1/MICROC~1/C30/support/h/p33FJ256GP710.h'. I am away from my computer on which EE and RT-Druid was tested, but as I remember, the relative path of C30/support/h/p33FJ256GP710.h is incorrect, since the up to date Microchip compiler has separate subdirectories of each family of their 16 bit MCU's. So the path should be C30/support/dsPIC33/h/p33FJ256GP710.h or someting similar.
Does it mean, that my compiler (probably ver 3.11B, but I cannot check at this moment) is not compatible with EE 1.4.3?
|
|
|
|
|
|
|
The administrator has disabled public write access. |
|
|
|
|
|
|
|
|
 |
Evidence S.r.l. - PIVA: 01638690501
Via Carducci 64/A - Ghezzano - Pisa - Italy
|
Privacy Policy
|
 |
|
|