Thanks for trying this out Raph - we would certainly be interested in having a convenient way to name the output library.
In answer to Assam's question - we build a large number of Android libraries as part of our application. Most are built using Visual Studio (for historical reasons), and we segregate them by architecture into different directories. So we have an existing naming convention that does not include the architecture name, which means the couple of libraries we actually build with qmake are named in a way that is inconsistent with all our other libraries. In fact we only build for ARM32 at present, so architecture qualifiers are not that important to us. I can see the benefits of the new Qt library naming scheme, and over time I expect we might go that way and make all our other libraries consistent with it. But in short, it didn't seem unreasonable to me that I ought to be able to choose whatever name I want for the library I'm building, and I was a bit surprised to find that there was no way to control this behavior. Rob Allan From: Assam Boudjelthia <assam.boudjelt...@qt.io> > To: Raphael Cotty <raphael.co...@gmail.com>, "interest@qt-project.org" < > interest@qt-project.org> > Date: Fri, 27 Nov 2020 10:21:44 +0000 > Subject: Re: [Interest] Customizing the output library name in Android > builds > Hi, > > What's the benefit of removing the suffix in a multi-abi build? > > Best regards, > Assam >
_______________________________________________ Interest mailing list Interest@qt-project.org https://lists.qt-project.org/listinfo/interest
