Re: [Interest] qmake: Building a shared object which is not a lib

On 27/06/12 18:26, Andreas Pakulat wrote: > Hi, > > Am Mittwoch, 27. Juni 2012 schrieb Christian Gagneraud : > > On 27/06/12 12:32, Mandeep Sandhu wrote: > > On Wed, Jun 27, 2012 at 4:29 PM, Christian Gagneraud > > wrote: > >> Hi there, > >> > [...] > > > > If y

Re: [Interest] qmake: Building a shared object which is not a lib

Hi, Am Mittwoch, 27. Juni 2012 schrieb Christian Gagneraud : > On 27/06/12 12:32, Mandeep Sandhu wrote: > > On Wed, Jun 27, 2012 at 4:29 PM, Christian Gagneraud > > > > wrote: > >> Hi there, > >> > [...] > > > > If you build a plugin, then the version links are not created, and > > simply the li

Re: [Interest] qmake: Building a shared object which is not a lib

On 27/06/12 12:32, Mandeep Sandhu wrote: > On Wed, Jun 27, 2012 at 4:29 PM, Christian Gagneraud > wrote: >> Hi there, >> [...] > > If you build a plugin, then the version links are not created, and > simply the libXYZ.so will be created (the lib prefix is still there). > > Why do you want to remo

Re: [Interest] qmake: Building a shared object which is not a lib

On Wed, Jun 27, 2012 at 4:29 PM, Christian Gagneraud wrote: > Hi there, > > I would like to build a shared object (PySide module) using qmake. > My first attempt was to use TEMPLATE=lib, which worked except that I > have no control on the name of the output file. > Is there a way to override the n

[Interest] qmake: Building a shared object which is not a lib

Hi there, I would like to build a shared object (PySide module) using qmake. My first attempt was to use TEMPLATE=lib, which worked except that I have no control on the name of the output file. Is there a way to override the name of the generated shared object file? Basically using TEMPLATE=lib,