**** BEGIN LOGGING AT Fri Oct 12 03:00:00 2018 Oct 12 08:12:19 Is anyone able to build a cmake based recipe with the following in the local.conf? Oct 12 08:12:19 TARGET_CPPFLAGS += '-DBLA="bla"' Oct 12 08:12:19 In my environments the compiler is called with -DBLA=;bla" (the first quotation mark is replaced by a semicolon) Oct 12 08:20:26 sstiller: so you want to set a specific CMAKE flag in a specific recipe only, and that through local.conf? Oct 12 08:21:36 sstiller: why not just add a bbappend, if its something that you always need? Oct 12 08:24:11 LetoThe2nd, the flag is used in multiple recipes in custom layers. Oct 12 08:27:02 And it's set depending on the current project. Oct 12 08:28:38 sstiller: in that case, i think its rather complicated. Oct 12 08:29:03 setting per recipe is easy. but "for some", huh, no idea. Oct 12 08:32:40 I think, it's a bug somewhere (perhaps in the cmake.bbclass?) Oct 12 08:55:10 It seems to be a bigger problem. In other recipes I get -DBLA=bla or -DBLA="bla" or -DBLA=\"bla\" (the only correct one) Oct 12 11:52:16 OK, I have a program that compiles some .s files and it looks like gcc isn't getting called with -mthumb. Any ideas why? Oct 12 14:04:19 hi Oct 12 16:07:17 I am debugging a changing basehash problem, I tracked it down to the TIME variable and tried adding it to vardepsexclude of the task, but it does not help... what am I missing? Oct 12 16:41:48 Jin^eLD: it could also be DATETIME Oct 12 23:24:36 khem: I added all three actually, DATE, TIME, DATETIME to be sure, but I found my mistake now, I vardepexcluded the task because bitbake was complaining about it, but I should have added the actual function that I am calling from that task and that uses the variable... after I did that the basehash error was gone Oct 12 23:40:42 Jin^eLD: right yes Oct 13 00:53:51 nite **** ENDING LOGGING AT Sat Oct 13 02:59:59 2018