Ahhh I see. It points to a file that would be bundled with the plugin code, ya?
I would refrain from using `target` as the attribute to specify which architecture to build for. In all other elements, `target` is used as a target destination for any plugin files. I'd like to keep that consistent. Perhaps an `architecture` or `arch` attribute? Would the SOs have to be placed in a specific location (and can/would that location need to be customized based on the library?). On 5/3/13 12:19 PM, "Jeffrey Heifetz" <[email protected]> wrote: >If you feel framework is a better choice I'm fine with that, I just >thought that frameworks were a part of the os/platform, but this would be >a native shared object made by the developer. > >On 13-05-03 3:14 PM, "Filip Maj" <[email protected]> wrote: > >>What about using <framework> elements for that? We can add a `target` >>attribute to it to satisfy BB's needs. >> >>On 5/3/13 12:07 PM, "Jeffrey Heifetz" <[email protected]> wrote: >> >>>While implementing the BlackBerry10 platform updates in plugman I've >>>noticed that the <lib-file> tags have been removed. I wanted to know if >>>this was a conscious decision and if so would anyone object to me >>>reviving them. In BlackBerry 10 some plugins require the use of >>>sharedObject libraries I would like to reference using the tag. >>> >>>Additionally I'd like to add an attribute "target" that would say the >>>architecture the lib-file was built for. For BB10 the libraries are >>>built >>>for device and simulator and we must install the library files >>>appropriate depending on the target at build time. >>> >>>So long as there are no objections, this will be merged in as part of >>>the >>>BlackBerry10 merge Lorin is helping us with in the not too distant >>>future. >>> >>>--------------------------------------------------------------------- >>>This transmission (including any attachments) may contain confidential >>>information, privileged material (including material protected by the >>>solicitor-client or other applicable privileges), or constitute >>>non-public information. Any use of this information by anyone other than >>>the intended recipient is prohibited. If you have received this >>>transmission in error, please immediately reply to the sender and delete >>>this information from your system. Use, dissemination, distribution, or >>>reproduction of this transmission by unintended recipients is not >>>authorized and may be unlawful. >> > > >--------------------------------------------------------------------- >This transmission (including any attachments) may contain confidential >information, privileged material (including material protected by the >solicitor-client or other applicable privileges), or constitute >non-public information. Any use of this information by anyone other than >the intended recipient is prohibited. If you have received this >transmission in error, please immediately reply to the sender and delete >this information from your system. Use, dissemination, distribution, or >reproduction of this transmission by unintended recipients is not >authorized and may be unlawful.
