Remove prototype support for C++ constructors, since it is not well designed. Device drivers (or other application code) that requires an automatic initialization capability should use the device initialization macros instead. Note: Support for C++ constructors may be re-introduced at a later date. However, a number of issues need to be settled, such as when the constructors are invoked and what context they run in. (Running them during nanokernel initialization, as was previously done, is probably not the right approach.) Change-Id: If6d27ac16b485cb39d5ec34084e9d0f1991074f4 Signed-off-by: Peter Mitsis <peter.mitsis@windriver.com>
19 lines
630 B
Makefile
19 lines
630 B
Makefile
ccflags-y +=-I$(srctree)/kernel/nanokernel/include
|
|
ccflags-y +=-I$(srctree)/kernel/microkernel/include
|
|
|
|
|
|
asflags-y := ${ccflags-y}
|
|
|
|
obj-y = nano_fiber.o nano_lifo.o \
|
|
nano_fifo.o nano_stack.o nano_sys_clock.o \
|
|
nano_context.o nano_init.o nano_sema.o \
|
|
version.o device.o
|
|
|
|
obj-$(CONFIG_STACK_CANARIES) += compiler_stack_protect.o
|
|
obj-$(CONFIG_INT_LATENCY_BENCHMARK) += int_latency_bench.o
|
|
obj-$(CONFIG_ADVANCED_POWER_MANAGEMENT) += idle.o
|
|
obj-$(CONFIG_NANO_TIMERS) += nano_timer.o
|
|
obj-$(CONFIG_EVENT_LOGGER) += event_logger.o
|
|
obj-$(CONFIG_KERNEL_EVENT_LOGGER) += kernel_event_logger.o
|
|
obj-$(CONFIG_RING_BUFFER) += ring_buffer.o
|