lk/app/loader/rules.mk

LOCAL_DIR := $(GET_LOCAL_DIR)

MODULE := $(LOCAL_DIR)

MODULE_SRCS += \
	$(LOCAL_DIR)/loader.c \

# disable a few warnings in gcc 11 that some of this module's code trips over
MODULE_COMPILEFLAGS += -Wno-array-bounds -Wno-stringop-overflow

MODULE_DEPS := \
    lib/cksum \
    lib/console \
    lib/tftp  \
    lib/elf

include make/module.mk
[app][loader] Load blobs and run elf via tftp into SDRAM Introduces two commands: load any <filename> load elf <filename> Then from another system in the network you can: tftp -i <ip-addr> put <filename> Which for the 'any' case just loads the file into DRAM and for the 'elf' case it parses the file and if correct it spawns a thread to run the entrypoint. 2015-09-17 18:21:39 -07:00			`LOCAL_DIR := $(GET_LOCAL_DIR)`

			`MODULE := $(LOCAL_DIR)`

			`MODULE_SRCS += \`
			`$(LOCAL_DIR)/loader.c \`

[warnings][gcc 11] Fix a few annoying out of bounds pointer warnings It seems to be in the case of a string op against a raw address, the compiler decides the destination object is 0 bytes long and throws a particular warning. Work around it by not using memcpy in one case and by disabling the warning in the other. Both are fairly benign code that basically operates in a hard coded way that knows the destination buffer is valid. 2021-06-27 00:28:58 -07:00			`# disable a few warnings in gcc 11 that some of this module's code trips over`
			`MODULE_COMPILEFLAGS += -Wno-array-bounds -Wno-stringop-overflow`
[app][loader] Load blobs and run elf via tftp into SDRAM Introduces two commands: load any <filename> load elf <filename> Then from another system in the network you can: tftp -i <ip-addr> put <filename> Which for the 'any' case just loads the file into DRAM and for the 'elf' case it parses the file and if correct it spawns a thread to run the entrypoint. 2015-09-17 18:21:39 -07:00
			`MODULE_DEPS := \`
			`lib/cksum \`
[include][console] split lib/console.h into two TL;DR most uses of lib/console.h -> lk/console_cmd.h Move the part that lets a piece of code somewhere in the system to define a console command from the actual lib/console api to start an instance of the console. Move in almost every place the user of the console command definition to the new header, lk/console_cmd.h which is always in the include path. Also remove most uses of testing for WITH_LIB_CONSOLE since you can almost always just safely define it and then let the linker remove it. 2019-07-13 16:56:33 -07:00			`lib/console \`
[app][loader] Load blobs and run elf via tftp into SDRAM Introduces two commands: load any <filename> load elf <filename> Then from another system in the network you can: tftp -i <ip-addr> put <filename> Which for the 'any' case just loads the file into DRAM and for the 'elf' case it parses the file and if correct it spawns a thread to run the entrypoint. 2015-09-17 18:21:39 -07:00			`lib/tftp \`
			`lib/elf`

			`include make/module.mk`