从lis上看是否宏编译到了.docVIP

学习一个新的平台,总被复杂的调用关系,一大堆的宏所困扰.以MTK为例.在一个版本中集中了非常多的功能,又有不同的芯片功能,程序显得繁复.这种情况对于一个初学者来说就显得很复杂.有无从下手的感觉. 刚开始时,我也觉得代码不好看.后面发现了一个有用的文件lis.这个文件和bin文件都在build目录下.这个文件指出了交叉引用关系.实际上这是一个ADS固有的功能,对所有以ADS编译的平台都是一样的.以开机初始化为例. #if defined(KAL_ON_NUCLEUS) void Application_Initialize (void *first_available_memory) #elif defined(KAL_ON_THREADX) void tx_application_define(void *first_unused_memory) #endif { __rt_lib_init(0, 0); #ifdef __MULTI_BOOT__ _boot_mode = *(volatile kal_uint16 *)BOOT_CONFIG_ADDR; #ifndef L1_NOT_PRESENT L1D_SetInitMode(_boot_mode); #endif #endif systemIntialization(); #ifdef MTK_PCM nvrm_init(); #endif HWDInitialization(); #ifdef _NAND_FLASH_BOOTING_ NFB_InitThirdROM(); NFB_LoadingSecondaryMAUI(); #endif Drv_Init_Phase2(); systemInitializeResource(); stack_check_msgid_range(); mainp(); #ifdef _MAUI_SOFTWARE_LA_ #endif #ifdef __PRODUCTION_RELEASE__ #ifdef __MULTI_BOOT__ if ( system_boot_mode!=FACTORY_BOOT ) #endif WDT_Enable(KAL_TRUE); #endif } 这个程序中很多的宏.哪个有个,哪个没有看不出.除非接合mak文件来查看.这也容易出错.在lis文件中就有比较简单的说明. init.obj(i.Application_Initialize) refers to lib_init.o(.text) for __rt_lib_init init.obj(i.Application_Initialize) refers to m12100.obj(i.L1D_SetInitMode) for L1D_SetInitMode init.obj(i.Application_Initialize) refers to intrCtrl.obj(i.initINTR) for initINTR init.obj(i.Application_Initialize) refers to isrentry.obj(i.IRQ_LISR_Init) for IRQ_LISR_Init init.obj(i.Application_Initialize) refers to custom_EMI.obj(i.Initialize_FDD_tables) for Initialize_FDD_tables init.obj(i.Application_Initialize) refers to kal_debug_error_handling.obj(i.kal_debug_register_print_string_function) for kal_debug_register_print_string_function init.obj(i.Application_Initialize) refers to kal_error_handling.obj(i.kal_register_fatal_error_handler) for kal_register_fatal_error_handler init.obj(i.Application_Initialize) refers to kal_nucleus_initialize.obj(i.kal_initialize_me