What is native library? What is binding? Why it is needed?
A native library is a library that contains "native" code. That is, code that has been compiled for a specific hardware architecture or operating system such as x86 or windows. Including such native library in your project may break the platform-independence of you application.
A native service binding gives the details necessary to access an IBM® i service program directly. Open the EGL Deployment Descriptor editor by double-clicking an EGL deployment descriptor. For details about creating the file, see “Creating an EGL deployment descriptor.” Click Service Bindings.
In programming and software design, binding is an application programming interface (API) that provides glue code specifically made to allow a programming language to use a foreign library or operating system service (one that is not native to that language).
A native library is a library written in a language that compiles down to native code for the platform it runs on, i.e. C++ creating PE files with x86 code. A binding, or language binding is the "glue" that makes it possible / more comfortable to use such a library from within another programming language, possibly providing a more elegant interface than just calling directly into the native code (think: better than P/Invoke, for example).
The question as to why it is needed is a simple one: To use the very large number of already existing libraries.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With