Re: [Development] A deployment tool for Linux
11.04.2019, 04:05, "Richard Weickelt" : > On 10.04.2019 23:21, Marco Bubke wrote: >> Sounds you want flatpak. ;-) > > All those run-time extracted application container formats might be nice > solutions for GUI applications which is apparently the main target of Qt. > But my observation is that they perform rather poorly when being used for > command line applications or a combination of both. You can use static linking for command-line applications, or use AppImage where artifact is just a single executable file which could be put anywhere in $PATH -- Regards, Konstantin ___ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
Re: [Development] A deployment tool for Linux
On 10.04.2019 23:21, Marco Bubke wrote: > Sounds you want flatpak. ;-) All those run-time extracted application container formats might be nice solutions for GUI applications which is apparently the main target of Qt. But my observation is that they perform rather poorly when being used for command line applications or a combination of both. ___ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
Re: [Development] A deployment tool for Linux
> You may need to do custom steps on artifacts produced by windeployqt before > packing them, so it's better to have separate tools for "bundling" and > creation > of actual packages. Well, that's easily solved. The "tool" doesn't need to do everything on a single invocation which leaves enough room for custom steps. However, I do see the point of using different tools for that purpose. Yet it would be convenient and time-saving to have everything under the same roof within a common framework and good reference documentation :) ___ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
Re: [Development] A deployment tool for Linux
Sounds you want flatpak. ;-) On April 10, 2019 21:43:31 Richard Weickelt wrote: >>> I, as a person, think that a "deployment tool for Linux" is >>> something that spits out packages in half a dozen "native" >>> distribution package formats. >> >> Nope, that tool is called "package maintainer" :) > > Blessed be those who have a "package maintainer". I don'ẗ think it's that > easy. If I would want to bring my software product into the official > distribution repositories, maybe and of course every open source project > should aim for it. But that's quite some effort and sometimes even > impossible. I would be interested to know how easy it is to release a > Qt-based application with a bleeding edge Qt version (or with a patched one) > to the official Debian repositories. > > And if I had a proprietary product and want to make updating as convenient > as possible for my customers? > > Nothing stops me from publishing a self-containing .deb, .rpm, .whatever on > my website. If there was a one stop shop tool that produces a collection > like this with very little effort: https://speedcrunch.org/download.html I > would be sold. Maybe even in combination with setting up my own package > repos. But with very little manpower that can be cumbersome. > >>> Collecting "resources that the application uses (like [...] >>> graphics, [...]" *and dependencies* would be a (important) >>> step, but not all that it takes. >> >> By this logic windeployqt should produce .msi packages > > Wouldn't be the worst feature though, would it. That doesn't make Andre's > comment less valid. > > Richard > ___ > Development mailing list > Development@qt-project.org > https://lists.qt-project.org/listinfo/development ___ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
Re: [Development] A deployment tool for Linux
On Wed, Apr 10, 2019 at 09:44:45PM +0300, Konstantin Tokarev wrote: > 10.04.2019, 21:38, "André Pönitz" : > > On Wed, Apr 10, 2019 at 08:13:01AM +, Mitch Curtis wrote: > >> What do people think about having a deployment tool for Linux? > > > > I, as a person, think that a "deployment tool for Linux" is > > something that spits out packages in half a dozen "native" > > distribution package formats. > > Nope, that tool is called "package maintainer" :) That concept is notorious for lacking usable copy constructors ;-} > > Collecting "resources that the application uses (like [...] > > graphics, [...]" *and dependencies* would be a (important) > > step, but not all that it takes. > > By this logic windeployqt should produce .msi packages Funnily enough that would be a goal when I were to develop an installer system. Or, should I say, "was". Andre' ___ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
Re: [Development] A deployment tool for Linux
10.04.2019, 23:09, "Konstantin Tokarev" : > 10.04.2019, 22:43, "Richard Weickelt" : >> I would be interested to know how easy it is to release a >> Qt-based application with a bleeding edge Qt version (or with a patched one) >> to the official Debian repositories. > > The only possible way to add package to the official Debian repositories is > described at [1], > there is no possible software tool which will make your package compliant to > all policies > and find it a "sponsor" from Debian developers. > > [1] > https://www.debian.org/doc/manuals/distribute-deb/distribute-deb.html#adding-packages-to-debian (And, of course, using custom or patched version of Qt, or having bundled libraries in your package will get it rejected quickly) -- Regards, Konstantin ___ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
Re: [Development] A deployment tool for Linux
10.04.2019, 22:43, "Richard Weickelt" : > I would be interested to know how easy it is to release a > Qt-based application with a bleeding edge Qt version (or with a patched one) > to the official Debian repositories. The only possible way to add package to the official Debian repositories is described at [1], there is no possible software tool which will make your package compliant to all policies and find it a "sponsor" from Debian developers. [1] https://www.debian.org/doc/manuals/distribute-deb/distribute-deb.html#adding-packages-to-debian -- Regards, Konstantin ___ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
Re: [Development] A deployment tool for Linux
10.04.2019, 22:43, "Richard Weickelt" : > Nothing stops me from publishing a self-containing .deb, .rpm, .whatever on > my website. If there was a one stop shop tool that produces a collection > like this with very little effort: https://speedcrunch.org/download.html I > would be sold. Maybe even in combination with setting up my own package > repos. But with very little manpower that can be cumbersome. Note that you need to actually test these packages, otherwise they may be broken because of dependencies. While RPM has a way to provide meaningful cross-distibution packages, .deb is inherently tied to particular version of Debian or Ubuntu. In practise you won't provide (and surely won't check) .whatever, so these people will need to unpack .deb or .rpm as archives to proceed Also, installing packages in "native" format usually requires root privileges, while QtIFW or AppImage don't. You also can't have a portable application running from flash drive with native packages. > >>> Collecting "resources that the application uses (like [...] >>> graphics, [...]" *and dependencies* would be a (important) >>> step, but not all that it takes. >> >> By this logic windeployqt should produce .msi packages > > Wouldn't be the worst feature though, would it. That doesn't make Andre's > comment less valid. You may need to do custom steps on artifacts produced by windeployqt before packing them, so it's better to have separate tools for "bundling" and creation of actual packages. > > Richard > ___ > Development mailing list > Development@qt-project.org > https://lists.qt-project.org/listinfo/development -- Regards, Konstantin ___ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
Re: [Development] Gitlab at qt.io
> Since its company-internal, the answer likely doesn't matter to you. But it > doesn't have CI. If a repository is worth having CI for, it should go to > Gerrit. > Thanks for replying anyway. Interesting. I was looking for a (semi-)open and maintainable CI solution that I could propose for Qbs. Not using gerrit is not an option. But the Qt Company seems to lack of an easy-to-use CI solution for this kind of project and the current amount of contributors. Richard ___ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
Re: [Development] A deployment tool for Linux
>> I, as a person, think that a "deployment tool for Linux" is >> something that spits out packages in half a dozen "native" >> distribution package formats. > > Nope, that tool is called "package maintainer" :) Blessed be those who have a "package maintainer". I don'ẗ think it's that easy. If I would want to bring my software product into the official distribution repositories, maybe and of course every open source project should aim for it. But that's quite some effort and sometimes even impossible. I would be interested to know how easy it is to release a Qt-based application with a bleeding edge Qt version (or with a patched one) to the official Debian repositories. And if I had a proprietary product and want to make updating as convenient as possible for my customers? Nothing stops me from publishing a self-containing .deb, .rpm, .whatever on my website. If there was a one stop shop tool that produces a collection like this with very little effort: https://speedcrunch.org/download.html I would be sold. Maybe even in combination with setting up my own package repos. But with very little manpower that can be cumbersome. >> Collecting "resources that the application uses (like [...] >> graphics, [...]" *and dependencies* would be a (important) >> step, but not all that it takes. > > By this logic windeployqt should produce .msi packages Wouldn't be the worst feature though, would it. That doesn't make Andre's comment less valid. Richard ___ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
Re: [Development] A deployment tool for Linux
10.04.2019, 21:38, "André Pönitz" : > On Wed, Apr 10, 2019 at 08:13:01AM +, Mitch Curtis wrote: >> What do people think about having a deployment tool for Linux? > > I, as a person, think that a "deployment tool for Linux" is > something that spits out packages in half a dozen "native" > distribution package formats. Nope, that tool is called "package maintainer" :) > Collecting "resources that the application uses (like [...] > graphics, [...]" *and dependencies* would be a (important) > step, but not all that it takes. By this logic windeployqt should produce .msi packages > > Andre' > ___ > Development mailing list > Development@qt-project.org > https://lists.qt-project.org/listinfo/development -- Regards, Konstantin ___ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
Re: [Development] A deployment tool for Linux
On Wed, Apr 10, 2019 at 08:13:01AM +, Mitch Curtis wrote: > What do people think about having a deployment tool for Linux? I, as a person, think that a "deployment tool for Linux" is something that spits out packages in half a dozen "native" distribution package formats. Collecting "resources that the application uses (like [...] graphics, [...]" *and dependencies* would be a (important) step, but not all that it takes. Andre' ___ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
[Development] Qt wrapper for UPC UA Server stack (open62541)
Hi guys, This is pretty much WIP, but I would like some thoughts or even contributions. https://github.com/juangburgos/QUaServer Thanks, ___ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
Re: [Development] Adding more Datetime classes to Qt
Mark De Wit (10 April 2019 12:36) wrote:
> It might be good to highlight, for instance, that MSecsSinceEpoch is
> not share-able between users in different timezones unless QDateTime
> is instantiated with a timespec of Qt::UTC (which is not the default).
In what sense can't "milliseconds since epoch" values be shared ?
Note that they're always time since 1970-01-01 00:00 UTC, regardless of
which time-spec your QDateTime is using.
(If you dig the milliseconds from epoch value out of the guts of a
QDateTime, that's related to an origin with the same offset from UTC as
the QDateTime's spec currently uses; but you shouldn't be doing that.
Use QDateTime's methods; {to,from}MSecsSinceEpoch(), which both refer to
the UTC epoch.)
> The defaults (local time w. timezone conversion) are perhaps more
> likely to lead to error than the plain C time since epoch with no
> hours being added/subtracted.
The "plain C time since epoch" is also referred to UTC, so (aside from a
factor of 1000) is no better or worse than our "milliseconds since
epoch" (aside from the range of date-times expressible being narrower,
for a given integral type; but we use a 64-bit type, which leaves an
acceptably wide range).
We're stuck with the defaults we have (thanks to binary and source
compatibility promises), but you can over-ride them easily enough. Just
pass Qt::UTC as third argument to the QDateTime constructor and you've
got what you want. Or map the QDateTime you've got through
.toTimeSpec(Qt::UTC) to put it in the standard form. Or just ask for its
.toMSecsSinceEpoch() to reduce it to a simple number, regardless of its
spec; and you can compare these, from different-spec QDateTime values.
Then again, you can just compare the QDateTime values; they'll sort out
their difference in offset if they need to.
As for the documentation, if you can see ways to improve it, please give
us patches or file bug reports that explain clearly what's confusing
you,
Eddy.
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development
[Development] Requesting a repository for Alexa integration
Hi, I would like to request for a new repository: Name of the repository: qt-labs/qtalexa.git Description: A environment enabling a use of Alexa an Qt based UI systems. Responsible person: Vladimir Minenko Gerrit user/email: vladimir.mine...@pelagicore.com We developed an initial version of integration of Amazon Alexa in Qt-based UI. It can currently visualize selected cards (known as "Display Cards") as well as use Custom Skills to post control command to a system using Qt as UI framework. The current implementation is fully functional and was already used in a joint-development prototype with a customer. The mid- to long-term intention is to create a new extension for Qt which would enable using of a voice assistance in Qt based applications and systems. The code will be licensed under (L)GLPv3 and commercial licenses. -- Vladimir Minenko – Qt Automotive Platform, Luxoft Automotive * Munich * Germany * +49 170 8583617 * https://www.qt.io/qt-automotive-suite/ * https://doc.qt.io/QtAutomotiveSuite/ This e-mail and any attachment(s) are intended only for the recipient(s) named above and others who have been specifically authorized to receive them. They may contain confidential information. If you are not the intended recipient, please do not read this email or its attachment(s). Furthermore, you are hereby notified that any dissemination, distribution or copying of this e-mail and any attachment(s) is strictly prohibited. If you have received this e-mail in error, please immediately notify the sender by replying to this e-mail and then delete this e-mail and any attachment(s) or copies thereof from your system. Thank you. ___ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
[Development] Requesting a repository for UI analytics
Hi, I would like to request for a new repository: Name of the repository: qt-labs/qtuianalytics.git Description: An plugin for Qt Quick allowing collection of UI usage analytics. Responsible person: Vladimir Minenko Gerrit user/email: vladimir.mine...@pelagicore.com We developed an initial version of a Qt Quick plug in allowing collection of UI usage analytics. It can be used in almost any QML item. It currently uses Matomo (former Piwik) as a web-based storage and visualization backend. The current implementation is fully functional and was already used in a joint-development prototype with a customer. The mid- to long-term intention is to create a new extension for Qt which would enable collection of UI usage data and a basic visualization with standard, mostly web-based analytics services, like Matomo. The code will be licensed under LGLPv3 and commercial licenses. -- Vladimir Minenko – Qt Automotive Platform, Luxoft Automotive * Munich * Germany * +49 170 8583617 * https://www.qt.io/qt-automotive-suite/ * https://doc.qt.io/QtAutomotiveSuite/ This e-mail and any attachment(s) are intended only for the recipient(s) named above and others who have been specifically authorized to receive them. They may contain confidential information. If you are not the intended recipient, please do not read this email or its attachment(s). Furthermore, you are hereby notified that any dissemination, distribution or copying of this e-mail and any attachment(s) is strictly prohibited. If you have received this e-mail in error, please immediately notify the sender by replying to this e-mail and then delete this e-mail and any attachment(s) or copies thereof from your system. Thank you. ___ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
[Development] HEADS UP : Qt 5.13 String Freeze
Hi, As informed earlier string freeze for Qt 5.13 is now in effect. So please, no changes to translatable strings from this point, unless approved by the documentation team. br, Jani From: Jani Heikkinen Sent: Wednesday, April 3, 2019 11:45 AM To: localizat...@qt-project.org; releas...@qt-project.org; development@qt-project.org Subject: HEADS UP : Qt 5.13 soft string freeze Hi all, First beta release from Qt 5.13 is already out so it is time to start keeping translatable strings as it is. Official string freeze will be in effect Wed 10th April 2019. br, Jani ___ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
Re: [Development] Adding more Datetime classes to Qt
> From: Development On Behalf Of > Thiago Macieira > > On Tuesday, 9 April 2019 05:11:03 PDT Pouya Shahinfar wrote: > > You open a project which is developed by someone else, and he/she used > > QDateTime for holding time and date. The problem here is you as a > > newcomer to project do not know the value in the class is based on UTC > > or local time, etc. if there was a class like QLocalDateTime, the code > > was more maintainable. > > Why is the code unmaintainable or unreadable just because the information > is not in the class name? The information *is* there, held inside the object. > You can ask it (timeSpec(), offsetFromUtc() and timeZone()) what it is. > > So what is the problem? We fell into the same QDateTime trap recently. The documentation on QDateTime is perhaps a bit too obscure and/or does not sufficiently highlight possible pitfalls? It might be good to highlight, for instance, that MSecsSinceEpoch is not share-able between users in different timezones unless QDateTime is instantiated with a timespec of Qt::UTC (which is not the default). The defaults (local time w. timezone conversion) are perhaps more likely to lead to error than the plain C time since epoch with no hours being added/subtracted. Mark ___ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
Re: [Development] A deployment tool for Linux
> -Original Message- > From: Development On Behalf Of > Dan Leinir Turthra Jensen > Sent: Wednesday, 10 April 2019 11:23 AM > To: development@qt-project.org; Khuram Ali > Subject: Re: [Development] A deployment tool for Linux > > Handily, there has been a concerted effort to create linuxdeploy, which is a > pluginified and much cleaned up version of linuxdeployqt :) > https://github.com/linuxdeploy/linuxdeploy Great! I created a suggestion there: https://github.com/linuxdeploy/linuxdeploy/issues/73 Though I'm honestly not sure what the practical differences between these two are, especially for the average user who just wants to simply deploy their application. I've only used linuxdeployqt myself. > On Wednesday, 10 April 2019 10:15:27 BST Khuram Ali via Development > wrote: > > Hi, > > I think, it is a good idea to have an official deployment tool as we > > have for windows. linuxdeployqt works but as mentioned earlier slower > and older. > > The things can get a bit better. Regards,Khuram Ali > > > > > > -Ursprüngliche Mitteilung- > > Von: Mitch Curtis > > An: Bogdan Vatra ; development@qt- > project.org > > Verschickt: Mi, 10. Apr. 2019 10:27 > > Betreff: Re: [Development] A deployment tool for Linux > > > > > -Original Message- > > > From: Bogdan Vatra > > > Sent: Wednesday, 10 April 2019 10:22 AM > > > To: development@qt-project.org > > > Cc: Mitch Curtis > > > Subject: Re: [Development] A deployment tool for Linux > > > > > > Hi, > > > > > > Personally I think it's a great idea. I used linuxdeployqt myself > > > and it > > > > > > worked. The only problem I saw it was the speed, it takes quite a > > > lot to complete (e.g. it took a few minutes, while androiddelopqt > > > takes less than > > > 10 seconds). But witl some love I'm pretty sure it can be improved a lot. > > Yeah I noticed that too.. thought it was a bit odd considering that > > file operations are usually very quick compared to Windows, whereas > > windeployqt is actually faster. > > > Cheers, > > > BogDan. > > > > > > În ziua de miercuri, 10 aprilie 2019, la 11:13:01 EEST, Mitch Curtis > > > a > scris: > > > > What do people think about having a deployment tool for Linux? > > > > There is an existing community tool based on macdeployqt: > > > > > > > > https://github.com/probonopd/linuxdeployqt/ > > > > > > > > The author has considered the idea in the past: > > > > > > > > https://github.com/probonopd/linuxdeployqt/issues/84 > > > > > > > > A Jira suggestion to track it: > > > > > > > > https://bugreports.qt.io/browse/QTBUG-74940 > > > > > > > > ___ > > > > Development mailing list > > > > Development@qt-project.org > > > > https://lists.qt-project.org/listinfo/development > > > > ___ > > Development mailing list > > Development@qt-project.org > > https://lists.qt-project.org/listinfo/development > > > -- > ..dan / leinir.. > http://leinir.dk/ > > > ___ > Development mailing list > Development@qt-project.org > https://lists.qt-project.org/listinfo/development ___ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
Re: [Development] A deployment tool for Linux
Handily, there has been a concerted effort to create linuxdeploy, which is a pluginified and much cleaned up version of linuxdeployqt :) https://github.com/linuxdeploy/linuxdeploy On Wednesday, 10 April 2019 10:15:27 BST Khuram Ali via Development wrote: > Hi, > I think, it is a good idea to have an official deployment tool as we have > for windows. linuxdeployqt works but as mentioned earlier slower and older. > The things can get a bit better. Regards,Khuram Ali > > > -Ursprüngliche Mitteilung- > Von: Mitch Curtis > An: Bogdan Vatra ; development@qt-project.org > Verschickt: Mi, 10. Apr. 2019 10:27 > Betreff: Re: [Development] A deployment tool for Linux > > > -Original Message- > > From: Bogdan Vatra > > Sent: Wednesday, 10 April 2019 10:22 AM > > To: development@qt-project.org > > Cc: Mitch Curtis > > Subject: Re: [Development] A deployment tool for Linux > > > > Hi, > > > > Personally I think it's a great idea. I used linuxdeployqt myself and it > > > > worked. The only problem I saw it was the speed, it takes quite a lot to > > complete (e.g. it took a few minutes, while androiddelopqt takes less than > > 10 seconds). But witl some love I'm pretty sure it can be improved a lot. > Yeah I noticed that too.. thought it was a bit odd considering that file > operations are usually very quick compared to Windows, whereas windeployqt > is actually faster. > > Cheers, > > BogDan. > > > > În ziua de miercuri, 10 aprilie 2019, la 11:13:01 EEST, Mitch Curtis a scris: > > > What do people think about having a deployment tool for Linux? There > > > is an existing community tool based on macdeployqt: > > > > > > https://github.com/probonopd/linuxdeployqt/ > > > > > > The author has considered the idea in the past: > > > > > > https://github.com/probonopd/linuxdeployqt/issues/84 > > > > > > A Jira suggestion to track it: > > > > > > https://bugreports.qt.io/browse/QTBUG-74940 > > > > > > ___ > > > Development mailing list > > > Development@qt-project.org > > > https://lists.qt-project.org/listinfo/development > > ___ > Development mailing list > Development@qt-project.org > https://lists.qt-project.org/listinfo/development -- ..dan / leinir.. http://leinir.dk/ ___ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
Re: [Development] A deployment tool for Linux
Hi, I think, it is a good idea to have an official deployment tool as we have for windows. linuxdeployqt works but as mentioned earlier slower and older. The things can get a bit better. Regards,Khuram Ali -Ursprüngliche Mitteilung- Von: Mitch Curtis An: Bogdan Vatra ; development@qt-project.org Verschickt: Mi, 10. Apr. 2019 10:27 Betreff: Re: [Development] A deployment tool for Linux > -Original Message- > From: Bogdan Vatra > Sent: Wednesday, 10 April 2019 10:22 AM > To: development@qt-project.org > Cc: Mitch Curtis > Subject: Re: [Development] A deployment tool for Linux > > Hi, > > Personally I think it's a great idea. I used linuxdeployqt myself and it > worked. The only problem I saw it was the speed, it takes quite a lot to > complete (e.g. it took a few minutes, while androiddelopqt takes less than 10 > seconds). But witl some love I'm pretty sure it can be improved a lot. Yeah I noticed that too.. thought it was a bit odd considering that file operations are usually very quick compared to Windows, whereas windeployqt is actually faster. > Cheers, > BogDan. > > > În ziua de miercuri, 10 aprilie 2019, la 11:13:01 EEST, Mitch Curtis a scris: > > What do people think about having a deployment tool for Linux? There > > is an existing community tool based on macdeployqt: > > > > https://github.com/probonopd/linuxdeployqt/ > > > > The author has considered the idea in the past: > > > > https://github.com/probonopd/linuxdeployqt/issues/84 > > > > A Jira suggestion to track it: > > > > https://bugreports.qt.io/browse/QTBUG-74940 > > > > ___ > > Development mailing list > > Development@qt-project.org > > https://lists.qt-project.org/listinfo/development > > ___ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development ___ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
Re: [Development] A deployment tool for Linux
> -Original Message- > From: Bogdan Vatra > Sent: Wednesday, 10 April 2019 10:22 AM > To: development@qt-project.org > Cc: Mitch Curtis > Subject: Re: [Development] A deployment tool for Linux > > Hi, > > Personally I think it's a great idea. I used linuxdeployqt myself and it > worked. The only problem I saw it was the speed, it takes quite a lot to > complete (e.g. it took a few minutes, while androiddelopqt takes less than 10 > seconds). But witl some love I'm pretty sure it can be improved a lot. Yeah I noticed that too.. thought it was a bit odd considering that file operations are usually very quick compared to Windows, whereas windeployqt is actually faster. > Cheers, > BogDan. > > > În ziua de miercuri, 10 aprilie 2019, la 11:13:01 EEST, Mitch Curtis a scris: > > What do people think about having a deployment tool for Linux? There > > is an existing community tool based on macdeployqt: > > > > https://github.com/probonopd/linuxdeployqt/ > > > > The author has considered the idea in the past: > > > > https://github.com/probonopd/linuxdeployqt/issues/84 > > > > A Jira suggestion to track it: > > > > https://bugreports.qt.io/browse/QTBUG-74940 > > > > ___ > > Development mailing list > > Development@qt-project.org > > https://lists.qt-project.org/listinfo/development > > ___ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
Re: [Development] A deployment tool for Linux
Hi, Personally I think it's a great idea. I used linuxdeployqt myself and it worked. The only problem I saw it was the speed, it takes quite a lot to complete (e.g. it took a few minutes, while androiddelopqt takes less than 10 seconds). But witl some love I'm pretty sure it can be improved a lot. Cheers, BogDan. În ziua de miercuri, 10 aprilie 2019, la 11:13:01 EEST, Mitch Curtis a scris: > What do people think about having a deployment tool for Linux? There is an > existing community tool based on macdeployqt: > > https://github.com/probonopd/linuxdeployqt/ > > The author has considered the idea in the past: > > https://github.com/probonopd/linuxdeployqt/issues/84 > > A Jira suggestion to track it: > > https://bugreports.qt.io/browse/QTBUG-74940 > > ___ > Development mailing list > Development@qt-project.org > https://lists.qt-project.org/listinfo/development ___ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
[Development] A deployment tool for Linux
What do people think about having a deployment tool for Linux? There is an existing community tool based on macdeployqt: https://github.com/probonopd/linuxdeployqt/ The author has considered the idea in the past: https://github.com/probonopd/linuxdeployqt/issues/84 A Jira suggestion to track it: https://bugreports.qt.io/browse/QTBUG-74940 ___ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
Re: [Development] Gitlab at qt.io
On 9.4.2019 17.02, Richard Weickelt wrote: > Hi, > > I would like to know more about https://git.qt.io > > - What's the purpose and the future plan? It's an internal Gitlab instance for The Qt Company. It's mostly a place for people to put small things that don't belong anywhere in Gerrit and are not worth creating a repo there. (Or not yet in the case of personal prototypes.) > - Is it available to registered users at qt.io ? I couldn't log in. It's not available to external people. > - Is it connected to gerrit or can it be connected? No. Big enough projects (even internal ones) get Gerrit repositories. > - Does it offer gitlab CI? Since its company-internal, the answer likely doesn't matter to you. But it doesn't have CI. If a repository is worth having CI for, it should go to Gerrit. -- Kari ___ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
