what's the rationale for libpcre_8.35 "PROVIDING" pcre?
i might be overthinking this, but ive noticed a number of "lib*"
recipe files that "PROVIDE" the shorter name. case in point -- in the current oe-core, the recipe file libpcre_8.35.bb explicitly does this:
PROVIDES += "pcre"
is there a reason for this, other than the obvious allowing to use the shorter name?
i did notice that, although the name "libpcre" suggests a shared
library, the recipe file clearly creates a number of packages, including some that provide command-line utilities:
PACKAGES =+ "libpcrecpp libpcreposix pcregrep pcregrep-doc pcretest pcretest-doc"
so is there anything to this occasional "lib*" renaming, other than
brevity? thanks.
rday
Signature · 7 lines
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================Quoted 9 lines · Robert P. J. Day
i might be overthinking this, but ive noticed a number of "lib*"
recipe files that "PROVIDE" the shorter name. case in point -- in the current oe-core, the recipe file libpcre_8.35.bb explicitly does this:PROVIDES += "pcre"
is there a reason for this, other than the obvious allowing to use the shorter name?
Quoted 8 lines
i did notice that, although the name "libpcre" suggests a shared
library, the recipe file clearly creates a number of packages, including some that provide command-line utilities:PACKAGES =+ "libpcrecpp libpcreposix pcregrep pcregrep-doc pcretest pcretest-doc"
so is there anything to this occasional "lib*" renaming, other than
brevity? thanks.
I suspect the recipe was once called "pcre" but was renamed and the PROVIDES was for compatibility. There might be something in the history about that.
Cheers,
Richard