Path Entry Problem

If you have a simple question and just want an answer.
martinh
Member++
Posts: 19
Joined: Thu Oct 01, 2015 10:55 am

Path Entry Problem

Post by martinh »

Hello,
 
I am using xTimeComposer vs. 14.1.0 with the xCORE-200 eXplorer board. 
When I launch xTimeComposer there are warnings regarding Path Entry Problems like this:
 
Invalid project path: Include path not found 
- (C:\Pr\XMOS\xTIMEcomposer\Community_14.1.0\target\include\c++\4.2.1). lib_gpio
- (C:\Pr\XMOS\xTIMEcomposer\Community_14.1.0\target\include\c++\4.2.1). lib_xassert
- (C:\Pr\XMOS\xTIMEcomposer\Community_14.1.0\target\include\c++\4.2.1\xcore-xmos-elf). lib_gpio
- (C:\Pr\XMOS\xTIMEcomposer\Community_14.1.0\target\include\c++\4.2.1\xcore-xmos-elf). lib_xassert
- (C:\Pr\XMOS\xTIMEcomposer\Community_14.1.0\target\include\gcc). lib_gpio
- (C:\Pr\XMOS\xTIMEcomposer\Community_14.1.0\target\include\gcc). lib_xassert
 
However, if I delete the warnings, clean the project and  recompile,  the warnings are gone.
Is that something that should ring a bell? Or can it be ignored?
 
Also, how can libraries be removed from a project?
The Makefile (USED MODULES: ...) does not contain the libraries that have been dragged to the project.
 
Regards,
 
Martin H.
User avatar
johned
XCore Addict
Posts: 185
Joined: Tue Mar 26, 2013 12:10 pm

Post by johned »

Hi Martin,

I always perform a clean before a build, on new projects to ensure that dependencies are resolved correctly (as you have seen).

I do not recommend removing unused modules becasue you can cause some dependency problems. It is better to leave them in place. They will not use up unnecessary program memory space when you build your application.

Best regards,

John

 

martinh
Member++
Posts: 19
Joined: Thu Oct 01, 2015 10:55 am

Post by martinh »

Hi John,

good to know. I wasn't sure if that would have any influence.

Thank you!

Regards,

Martin H.