the intention of the libraries was for private use for the application and not for -dev only, since they are very tightly bound to the tool. Two of the shared libraries are two builds of the same ACPICA core with different build modes. They have a fwts specific shim to allow allow the tool to use the ACPICA core but also to hide a lot symbols to stop symbol clashes. Thus they are really for fwts usage only.
If I was intending to allow other packages build against these libraries I would first write some documentation, but that's outside the scope of this project at the moment.
Daniel,
the intention of the libraries was for private use for the application and not for -dev only, since they are very tightly bound to the tool. Two of the shared libraries are two builds of the same ACPICA core with different build modes. They have a fwts specific shim to allow allow the tool to use the ACPICA core but also to hide a lot symbols to stop symbol clashes. Thus they are really for fwts usage only.
If I was intending to allow other packages build against these libraries I would first write some documentation, but that's outside the scope of this project at the moment.
Hope that clarifies things.
Colin