- Jun 6, 2020
- 11,593
- 4,507
B4i libraries are written in Objective C. You need to use a Mac with Xcode and you need to know Objective C.
From my experience it is more difficult to write B4i libraries compared to B4A / B4J libraries.
Libraries are made of three files: library.a, library.h and library.xml.
The xml file is created automatically from the h file using the tool attached to this thread.
This is a command line tool written with B4J. You need to pass two arguments: path to the h file and path to the output file.
For example:
B4X:
Note that this tool parses the file line by line. It will not handle properly signatures that span multiple lines.
The a and h files should be eventually copied to the Libs folder on the Mac and the xml file should be copied to the IDE libraries folder.
Libraries should include two binaries: arm64 and armv7.
Supported types
The following types can be exposed to B4i: BOOL, unsigned char, unichar, short, int, long...
From my experience it is more difficult to write B4i libraries compared to B4A / B4J libraries.
Libraries are made of three files: library.a, library.h and library.xml.
The xml file is created automatically from the h file using the tool attached to this thread.
This is a command line tool written with B4J. You need to pass two arguments: path to the h file and path to the output file.
For example:
B4X:
java -jar B4Ih2xml.jar test.h test.xmlNote that this tool parses the file line by line. It will not handle properly signatures that span multiple lines.
The a and h files should be eventually copied to the Libs folder on the Mac and the xml file should be copied to the IDE libraries folder.
Libraries should include two binaries: arm64 and armv7.
Supported types
The following types can be exposed to B4i: BOOL, unsigned char, unichar, short, int, long...
برای دیدن لینک ها باید ثبت نام کنید
برای دیدن لینک ها باید ثبت نام کنید