RE: how do i view header files in keil component classes?

chadrick — Mon, 11 Apr 2016 14:03:06 GMT

yep i think you're right. I think compiling it is the key.

RE: how do i view header files in keil component classes?

Hung Bui — Mon, 11 Apr 2016 12:50:22 GMT

Hi Chadrick, I believe if you can manage to compile the project, you will see the list of header files for each file. Do you have any problem when you compile the "issue" project ? Note that in the latest SDK, we moved away from packs. Have a look here.

RE: how do i view header files in keil component classes?

chadrick — Sun, 10 Apr 2016 13:19:23 GMT

okay I have found out half of the reason why this happens.

Part of the reason behind this difference was the 'variant' configuration of 'software components'. Here's a walkthough showing what difference this can make.

User can manage their software components via 'manage run-time environment' icon.
in my case, I'm interested in the 'board support' software component.

there are four variants in total. I'm not sure what each of those variants do but I do have a fair-guess of my own. If you want to get the same amount of hunch that I do now, take a look at 'bsp.h' file. In that file, there is a small piece of code that looks like this:

/* BSP_UART_SUPPORT
 * This define enables UART support module.
 */
#ifdef BSP_UART_SUPPORT
#include "app_uart.h"
#endif // BSP_UART_SUPPORT

So, my hunch is that depending on the variant, the 'bsp.h' file will include some more features or not. Therefore, I'm pretty sure that it is safe to assume that 'default' variant is the 'default' version of 'bsp.h'. However, I have no clue on what 'defines' variant could be. also, there isn't another "#ifdef" at all, leaving me curious what the 'Simple_with_uart' variant could possibly be. Despite many unanswered questions, I'll show what results occur depending on the 'defines' and 'default' variants.

First, when I choose the 'defines' variant the project panel looks like this:

the 'board support' component cannot be extended further.

If I can the variant to 'default':

then I get:

this time, I have an extendable 'board support' component.

I have found that in some examles projects, the 'board support' component does not become extensive despite using the 'default' variant. That is why I think I've only found half of my answer.

If anyone could enlighten me on the key difference between 'defines' and 'default' variant of software components, I would be grateful.