Re: [OE-core] want to clarify proper approach to shared lib (.so) installation

2021-06-04 Thread Robert P. J. Day
On Fri, 4 Jun 2021, Andre McCurdy wrote: ... big ship ... > Just a warning, but if your Makefiles are not generating versioned > shared libraries then they are probably not setting a soname > either... and that really messes up OE's automatic runtime > dependency tracking for shared libraries. >

Re: [OE-core] want to clarify proper approach to shared lib (.so) installation

2021-06-04 Thread Andre McCurdy
On Thu, Jun 3, 2021 at 7:26 AM Robert P. J. Day wrote: > > On Thu, 3 Jun 2021, Andrea Adami wrote: > > > On Thu, Jun 3, 2021 at 4:01 PM Robert P. J. Day > > wrote: > > > > > > > > > sort of a 2-part soliloquy. in current YP code base i've inherited, > > > most of the internal (local directory

Re: [OE-core] want to clarify proper approach to shared lib (.so) installation

2021-06-03 Thread Robert P. J. Day
On Thu, 3 Jun 2021, Andrea Adami wrote: > On Thu, Jun 3, 2021 at 4:01 PM Robert P. J. Day wrote: > > > > > > sort of a 2-part soliloquy. in current YP code base i've inherited, > > most of the internal (local directory SRC_URI-based) recipes inherit a > > proprietary class that, among doing oth

Re: [OE-core] want to clarify proper approach to shared lib (.so) installation

2021-06-03 Thread Andrea Adami
On Thu, Jun 3, 2021 at 4:01 PM Robert P. J. Day wrote: > > > sort of a 2-part soliloquy. in current YP code base i've inherited, > most of the internal (local directory SRC_URI-based) recipes inherit a > proprietary class that, among doing other internal, proprietary > things, totally redefines

[OE-core] want to clarify proper approach to shared lib (.so) installation

2021-06-03 Thread Robert P. J. Day
sort of a 2-part soliloquy. in current YP code base i've inherited, most of the internal (local directory SRC_URI-based) recipes inherit a proprietary class that, among doing other internal, proprietary things, totally redefines PACKAGES as: PACKAGES = "${PN} ... ${PN}-dev ..." i had never r