genode/repos/libports/src/test/smartcard/target.mk

TARGET = test-smartcard
LIBS   = pcsc-lite posix
SRC_CC = main.cc

vpath main.cc $(PRG_DIR)/..

CC_CXX_WARN_STRICT =
libports: add pcsc-lite library Fixes #2145 2016-10-20 15:47:19 +02:00			`TARGET = test-smartcard`
Simpify startup of dynamically linked binaries This patch removes the component_entry_point library, which used to proved a hook for the libc to intercept the call of the 'Component::construct' function. The mechansim has several shortcomings (see the discussion in the associated issue) and was complex. So we eventually discarded the approach in favor of the explicit handling of the startup. A regular Genode component provides a 'Component::construct' function, which is determined by the dynamic linker via a symbol lookup. For the time being, the dynamic linker falls back to looking up a 'main' function if no 'Component::construct' function could be found. The libc provides an implementation of 'Component::construct', which sets up the libc's task handling and finally call the function 'Libc::Component::construct' from the context of the appllication task. This function is expected to be provided by the libc-using application. Consequently, Genode components that use the libc have to implement the 'Libc::Component::construct' function. The new 'posix' library provides an implementation of 'Libc::Component::construct' that calls a main function. Hence, POSIX programs that merely use the POSIX API merely have to add 'posix' to the 'LIBS' declaration in their 'target.mk' file. Their execution starts at 'main'. Issue #2199 2016-12-22 15:01:19 +01:00			`LIBS = pcsc-lite posix`
libports: add pcsc-lite library Fixes #2145 2016-10-20 15:47:19 +02:00			`SRC_CC = main.cc`

			`vpath main.cc $(PRG_DIR)/..`
Exclude higher-level repos from strict warnings This is a follow-up commit to "Increase default warning level", which overrides Genode's new default warning level for targets contained in higher-level repositories. By explicitly whitelisting all those targets, we can selectively adjust them to the new strictness over time - by looking out for 'CC_CXX_WARN_STRICT' in the target description files. Issue #465 2018-01-03 18:40:54 +01:00
			`CC_CXX_WARN_STRICT =`