Re: [Development] A deployment tool for Linux

[Kevin Kofler]

Mitch Curtis wrote:
> (which it turns out you still need to bundle libs that are dynamically
> linked like ICU)

With a bit of effort, you can also force Qt to build against a static ICU.
This is the hack (abusing the ICU bundled by Chromium bundled by
QtWebEngine, which is part of the monolithic Qt tarball) I used a while ago
with Qt 5.6.3 (to build portable Qt Jambi 5 binaries):
  cd qtwebengine/src/3rdparty/chromium/third_party/icu/source/
  ICU_DIR=`pwd`
  sed -i -e 's! test/Makefile test/compat/Makefile test/testdata/Makefile 
test/testdata/pkgdataMakefile test/hdrtst/Makefile test/intltest/Makefile 
test/cintltst/Makefile test/iotest/Makefile test/letest/Makefile 
test/perf/Makefile test/perf/collationperf/Makefile test/perf/collperf/Makefile 
test/perf/collperf2/Makefile test/perf/dicttrieperf/Makefile 
test/perf/ubrkperf/Makefile test/perf/charperf/Makefile 
test/perf/convperf/Makefile 
test/perf/normperf/Makefile test/perf/DateFmtPerf/Makefile 
test/perf/howExpensiveIs/Makefile test/perf/strsrchperf/Makefile 
test/perf/unisetperf/Makefile 
test/perf/usetperf/Makefile test/perf/ustrperf/Makefile 
test/perf/utfperf/Makefile test/perf/utrie2perf/Makefile 
test/perf/leperf/Makefile!!g' configure
  rm -f data/translit/trnslocal.mk
  CC=gcc CXX=g++ CFLAGS="-O2 -fPIC -fno-strict-aliasing -fvisibility=hidden" 
CXXFLAGS="-O2 -fPIC -fno-strict-aliasing -fvisibility=hidden -fvisibility-
inlines-hidden" ./configure --disable-shared --enable-static --disable-layout 
--disable-tests || exit 1
  make -j8 VERBOSE=1 || exit 1
  cd ../../../../../../..
  sed -i -e "s#LIBS_PRIVATE += -licui18n -licuuc -licudata#INCLUDEPATH += 
$ICU_DIR/common $ICU_DIR/i18n $ICU_DIR/io $ICU_DIR/extra/uconv\n
LIBS_PRIVATE 
+= -Wl,--gc-sections -L$ICU_DIR/lib -Wl,-Bstatic -licui18n -licuuc -licudata 
-Wl,-Bdynamic#g" qtbase/src/3rdparty/icu_dependency.pri

This probably needs changes for current Qt 5.12, but that's the idea at
least.

Kevin Kofler

___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] A deployment tool for Linux

[Łukasz Korbel]

Nice to know that someone prepared linuxdeployqt. Even if slow its probably
better than no tool at all as it is now. Last time on my CI I had to use
simple copy script with fixed list of libs based od readelf info. Works but
I would rather preffer to avoid repeating this :)

*Łukasz Korbel *
Senior Software Developer
Email: lkor...@milosolutions.com
Skype: lukasz_korbel
*Milo Solutions*
www.milosolutions.com | Facebook 
| Twitter 
Disclaimer: This e-mail and any attachments contain information that may be
privileged or confidential and is the property of Milo Solutions. If you
are not the intended recipient, please notify me immediately by replying to
this e-mail, and then delete it. Any unauthorised
dissemination, distribution, copying or use of this communication is
strictly prohibited. The contents of an attachment to this e-mail may
contain software viruses, which could damage your own computer system.
Although this e-mail and any files attached to it may have been checked
with virus detection software before transmission you should carry out your
own virus checks before opening the attachment. No liability can be
accepted for any damage which you may sustain as a result of software
viruses.


On Thu, Apr 11, 2019 at 5:45 PM Jason H  wrote:

> > 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
>
> Doesn't static linking require a static Qt?
>
> Last time I messed with this was 1 years ago on a windows system which was
> pretty easy. I would use depends.exe and make sure the dependencies were
> next to the binary. Since then I've been mainly doing mobile apps which
> have their own packages. But once in a while I'll whip up a program for
> automation. I've lucked out that these systems are large and not Pis with
> limited storage, so I can put all of Qt on and compile it there. That's
> easiest. It was easier to just install Qt and build it on that system.
>
> Minimally I would like something to produce an image suitable for and
> "/opt" install. That is to me to be a structure like:
> project/
> + bin/
> + + a.out
> + libs/
> + + [list of libs, Qt | system]
> + etc/
>
> Given a generic binary, I would assume there's a generic tool to do this
> already? Is there a [what is the] Qt value-add?
>
> I tried linuxdeployqt and it made my head spin. It stats out: "You'll need
> to provide the basic structure of an AppDir which should look something
> like this:". To which I say "No" this should be done for me. QMake knows
> all the things. There is no value-add in a human doing it. It continues
> "Where your desktop file would look something like:" Again, no, generate
> one for me. If I need to adjust things, I'll do that after they are
> generated. Of this, the application icon is the only thing I might want to
> modify. The time to do all that setup is greater than installing Qt,
> checking out the source and building.
>
>
>
>
>
>
>
>
>
>
> ___
> 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

[Ashley Sibille]

Someone please remove me from this list

On Thu, Apr 11, 2019 at 8:44 AM Jason H  wrote:

> > 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
>
> Doesn't static linking require a static Qt?
>
> Last time I messed with this was 1 years ago on a windows system which was
> pretty easy. I would use depends.exe and make sure the dependencies were
> next to the binary. Since then I've been mainly doing mobile apps which
> have their own packages. But once in a while I'll whip up a program for
> automation. I've lucked out that these systems are large and not Pis with
> limited storage, so I can put all of Qt on and compile it there. That's
> easiest. It was easier to just install Qt and build it on that system.
>
> Minimally I would like something to produce an image suitable for and
> "/opt" install. That is to me to be a structure like:
> project/
> + bin/
> + + a.out
> + libs/
> + + [list of libs, Qt | system]
> + etc/
>
> Given a generic binary, I would assume there's a generic tool to do this
> already? Is there a [what is the] Qt value-add?
>
> I tried linuxdeployqt and it made my head spin. It stats out: "You'll need
> to provide the basic structure of an AppDir which should look something
> like this:". To which I say "No" this should be done for me. QMake knows
> all the things. There is no value-add in a human doing it. It continues
> "Where your desktop file would look something like:" Again, no, generate
> one for me. If I need to adjust things, I'll do that after they are
> generated. Of this, the application icon is the only thing I might want to
> modify. The time to do all that setup is greater than installing Qt,
> checking out the source and building.
>
>
>
>
>
>
>
>
>
>
> ___
> Development mailing list
> Development@qt-project.org
> https://lists.qt-project.org/listinfo/development
>


-- 
all the best,

ashley
www.ashleysibille.com
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] A deployment tool for Linux

[Jason H]

> 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

Doesn't static linking require a static Qt?

Last time I messed with this was 1 years ago on a windows system which was 
pretty easy. I would use depends.exe and make sure the dependencies were next 
to the binary. Since then I've been mainly doing mobile apps which have their 
own packages. But once in a while I'll whip up a program for automation. I've 
lucked out that these systems are large and not Pis with limited storage, so I 
can put all of Qt on and compile it there. That's easiest. It was easier to 
just install Qt and build it on that system.  

Minimally I would like something to produce an image suitable for and "/opt" 
install. That is to me to be a structure like:
project/
+ bin/
+ + a.out
+ libs/
+ + [list of libs, Qt | system]
+ etc/

Given a generic binary, I would assume there's a generic tool to do this 
already? Is there a [what is the] Qt value-add?

I tried linuxdeployqt and it made my head spin. It stats out: "You'll need to 
provide the basic structure of an AppDir which should look something like 
this:". To which I say "No" this should be done for me. QMake knows all the 
things. There is no value-add in a human doing it. It continues "Where your 
desktop file would look something like:" Again, no, generate one for me. If I 
need to adjust things, I'll do that after they are generated. Of this, the 
application icon is the only thing I might want to modify. The time to do all 
that setup is greater than installing Qt, checking out the source and building.










___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] A deployment tool for Linux

[Mitch Curtis]

I think it's better to have a tool that does *something* with a documented, 
limited scope than offer nothing at all.

Then again, I know very little about shipping applications on Linux. I've 
either been building statically (which it turns out you still need to bundle 
libs that are dynamically linked like ICU) or using linuxdeployqt, and I only 
bother supporting Ubuntu because that's what I use.

On 4/10/19, 8:35 PM, "André Pönitz"  wrote:

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

Re: [Development] A deployment tool for Linux

[Konstantin Tokarev]

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

[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.
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] A deployment tool for Linux

[Richard Weickelt]

> 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

[Marco Bubke]

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

[André Pönitz]

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

[Konstantin Tokarev]

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

[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

-- 
Regards,
Konstantin

___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] A deployment tool for Linux

[Konstantin Tokarev]

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] A deployment tool for Linux

[Richard Weickelt]

>> 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

[Konstantin Tokarev]

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

[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.

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

Re: [Development] A deployment tool for Linux

[Mitch Curtis]

> -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

[Dan Leinir Turthra Jensen]

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

[Khuram Ali via Development]

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

[Mitch Curtis]

> -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

[Bogdan Vatra via Development]

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

[Mitch Curtis]

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