_AGNOSK_ and _AGNOSCL_

The Compilation Options _AGNOSK_ and _AGNOSCL_ allow isolating code specific to a Card Interface Technology

This allows removing unused code and save some memory when a Card Interface Technology is not present on a Terminal:

• _AGNOSK_: Code specific to the Contact Card Reader Interface

• _AGNOSCL_: Code specific to the Contactless Card Reader Interface

If both Card Interface Technologies are supported then both Compilation Options shall be present, otherwise only add the Compilation Option for the Card Interface Technology supported by the Terminal

For example, a COTS Device which has only a NFC Interface available only requires presence of the compilation _AGNOSCL_ (_AGNOSK_ being useless)

Presence of Agnos Components

Some Agnos Libraries may be Contact or Contactless specific, the following table illustrates presence of Agnos Framework Components based on Card Technology:

...

Agnos Library

...

_AGNOSK_

...

_AGNOSCL_

...

EMVCo

...

Required

...

AgnosEP

...

Required

...

Contactless Kernel C2, C3, C4…

...

Conditional

NOTE: GPI, DEVICE, TLV, Agnos, AgnosDB and AgnosMW are always required

_DUAL_POLLING_

The _DUAL_POLLING_ Compilation Option allows to perform Card Detection on both Contact and Contactless Interface Technologies at the same time.

This Compilation Option is only relevant to the Kizis Application, the KizisSP Application always perform Card Detection on all Card interface Technologies that are available.This section contains Compilation Options that are specific to the support of the Contact and Contactless Card Technologies