The Additional Libraries folder configured in the local B4i IDE does not participate directly in the actual iOS build process on the Hosted Builder. Its primary purpose is to make libraries known to the IDE at development time. This includes providing metadata for IntelliSense, allowing the IDE to validate symbols, classes, and methods, and enabling the B4i compiler to correctly translate the BASIC code into Objective-C by generating the required references and placeholders during the initial compilation phase.
When B4i translates BASIC code to Objective-C, it needs to know which libraries exist and which APIs they expose. This information comes from the locally installed libraries and their XML descriptions.
However, the real native compilation, linking, and header resolution happens entirely on the Hosted Builder. For that step, the Hosted Builder must already have the corresponding native library files available on the server side.
Libraries placed in the local Additional Libraries folder are not automatically uploaded or transferred to the Hosted Builder. This is why missing header errors occur even though the library is correctly configured in the local IDE.
In short, the Additional Libraries folder supports the IDE and the translation step, but it has no influence on which native libraries are available on the Hosted Builder during the actual iOS build.