Re: shared and static library names differ

On Mon, Jan 20, 2014 at 1:40 AM, Roman Valov wrote: > The problem is that on unix systems cmake generates shared > library with name libglfw.so.3 (libglfw.so intented to be put > into -dev package) and static library is built with api version > in its name: libglfw3.a Sounds like a bug that shoul

Re: shared and static library names differ

2014/1/19 Roman Valov : > What is the best way to handle this? Is it okay to drop static library > from -dev package? My personal opinion is not to ship static library at all, if it is possible. Regards, Anton -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject

Re: shared and static library names differ

2014/1/19 Roman Valov : > libglfw3.a mv libglfw3.a libglfw.a ? -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/call-q8zfh7ktvfphybc5fxqdt8v8s5uworh+jceqlrbuzpt...@

shared and static library names differ

Dear mentors, atm I'm trying to package glfw3 (http://www.glfw.org) library. The problem is that on unix systems cmake generates shared library with name libglfw.so.3 (libglfw.so intented to be put into -dev package) and static library is built with api version in its name: libglfw3.a Moreover o