Re: specialtopics.html: cmake ports and SHARED_LIBS

2022-01-25 Thread Antoine Jacoutot
On Tue, Jan 25, 2022 at 02:53:48PM +, Stuart Henderson wrote: > Ports using cmake.port.mk usually need some help to get shared libraries > built correctly with the version suffix, if a build is run without any > SHARED_LIBS entries for a library (as is the case for a new port, or an > existing

Re: specialtopics.html: cmake ports and SHARED_LIBS

2022-01-25 Thread Marc Espie
On Tue, Jan 25, 2022 at 02:53:48PM +, Stuart Henderson wrote: > Ports using cmake.port.mk usually need some help to get shared libraries > built correctly with the version suffix, if a build is run without any > SHARED_LIBS entries for a library (as is the case for a new port, or an > existing

Re: specialtopics.html: cmake ports and SHARED_LIBS

2022-01-25 Thread Kurt Mosiejczuk
On Tue, Jan 25, 2022 at 02:53:48PM +, Stuart Henderson wrote: > Ports using cmake.port.mk usually need some help to get shared libraries > built correctly with the version suffix, if a build is run without any > SHARED_LIBS entries for a library (as is the case for a new port, or an > existing

Re: specialtopics.html: cmake ports and SHARED_LIBS

2022-01-25 Thread Tracey Emery
On Tue, Jan 25, 2022 at 02:53:48PM +, Stuart Henderson wrote: > Ports using cmake.port.mk usually need some help to get shared libraries > built correctly with the version suffix, if a build is run without any > SHARED_LIBS entries for a library (as is the case for a new port, or an > existing

specialtopics.html: cmake ports and SHARED_LIBS

2022-01-25 Thread Stuart Henderson
Ports using cmake.port.mk usually need some help to get shared libraries built correctly with the version suffix, if a build is run without any SHARED_LIBS entries for a library (as is the case for a new port, or an existing port which adds a new library) the file is usually named libXXX.so rather