dependency on lib_xassert ...

New to XMOS and XCore? Get started here.
soundhound
Member
Posts: 11
Joined: Thu Mar 08, 2018 4:07 pm

dependency on lib_xassert ...

Postby soundhound » Fri Mar 09, 2018 1:45 pm

hi
after ticking off lib_logging and lib_xassert (which loggind depends on) in the makefile module dependencies for my Hello World application,
the compilation fails with
"lib_logging/src/debug_printf.c:2:10: fatal error: 'debug_print.h' file not found "

how can this be when the dependency is explicitly established?
User avatar
mon2
XCore Legend
Posts: 1098
Joined: Thu Jun 10, 2010 11:43 am
Contact:

Postby mon2 » Fri Mar 09, 2018 2:19 pm

try adding:

Code: Select all

#include "debug_print.h"


and post your results. If still not working, post your code here.
soundhound
Member
Posts: 11
Joined: Thu Mar 08, 2018 4:07 pm

Postby soundhound » Fri Mar 09, 2018 4:07 pm

scrap my reference to lib_xassert, I don't think it is relevant here....

I'm not using any debug statements - that include is in lib_logging/src/debug_printf.c
so the anomaly is that lib_logging doesn't appear able to include its own header file!
from what I have read of the xtc guide so far a library should be describing everything about itself necessary for compilation.
my expectation is that ticking a dependency box in my app should be all that is needed for the library to compile itself for inclusion :(
soundhound
Member
Posts: 11
Joined: Thu Mar 08, 2018 4:07 pm

Postby soundhound » Fri Mar 09, 2018 10:37 pm

after going through the content of the underlying directory and swapping in files from a working compilation (AN00156 I2C example)
looking for the difference that accounted for not finding a library's own header file, I found that nothing mattered - I could not reliably recreate a failure/success, could not account for any step that yielded one or the other.

after a day's worth of fiddling I was creating a new project, toggling the makefile dependency on lib_i2c, and seeing the compilation of library lib_logging indicating the debug_print.h file was being found.
I can now NOT recreate the original error. Utterly inexplicable!!!
it's as if something in the behaviour of XTC itself changed over the course of the day.
frustrating to hit such anomalies right out of the gate.

Who is online

Users browsing this forum: No registered users and 7 guests