Nice. I'm a bit surprised file_name() returns a char* rather than a
std::filesystem::path, but it'll do. It's also nice to see
source_location has a function_name() that can finally unify the
disparate ways of getting that information.
The advantages are for instance that file_name() does
nor has the person contributed to the codebase during
the last couple of years.
The question is whether this is an abuse of approver rights.
This is a relevant question for the Qt project. Any person with approver
rights has the ability to cause a production stop. Ivan is asking for help
in t
Hi,
> We are
> also checking alternative options like using another service provider or our
> own machine room in the same capacity where CI and related development
> systems are running.
... or like setting up a load balancer that distributes download requests to
the mirrors? That would be benef
> Right. That will become an issue in 4 months when GCC 11 ships with its
> internal
> header-dependency refactorings, breaking all sorts of Qt code, and
> that will then
> bubble down to various distro downstreams during this year and next. Then
> again,
> distro packagers can hopefully handle t
Company's position regarding conan-center?
Thanks
BR
Richard Weickelt
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development
> Still waiting for instructions on how to do an unattended installation of a
> binary Qt.
While you are waiting, have you seen those pages?
- https://www.qt.io/blog/qt-online-installer-4.0-pre-alpha-released
- https://wiki.qt.io/Online_Installer_4.x
Bonus:
- https://pastebin.com/jUN51zci
May
> Oddly enough, continued support for the Free Software ecosystem around
> Qt is one of the things most of us who work here care about deeply, so
I have no doubts that Qt engineers do. I can see this in in every code reciew
and I appreciate it very much!
> Our management, in any case, knows full
> AppVeyor supports Linux, but they support Dot Net on Linux, which isn't
> interesting. Travis does not support Windows (or didn't, last I checked).
> That means I need both to have the two to support three OSes.
Travis supports Windows. The machines are not fast, but it is usually enough.
>
>
>> In an ideal world...
>>
>> - Alice opens a pull request on GitHub.
>> - A bot sees the PR and opens a corresponding request on Gerrit.
>> - Bob comments on the Gerrit request.
>> - A bot sees Bob's comment and replicates it to the GitHub PR.
>> - Alice replies (on GitHub) to Bob's comment.
>> -
Tino, Volker,
> In a CI/CD pipeline that depends on 3rd party packages like Qt, it’s a good
> idea to manage your own artefact/package repo, so that you have control over
> the versions you are building and testing against - or at the very least to
> become independent of 3rd party infrastructure
>> Maybe you all have great ideas that we missed though. What kind of change do
>> you think would give companies a really good reason to buy a license, without
>> at the same time hurting the community?
I wonder if selling per-developer licenses is still a sustainable business
model at all. We a
> - Product repo contains a Conan recipe. Conan takes care of
> getting/building the dependencies.
That sounds interesting. Will the QtCompany use Conan as _the_ package
manager for the market place and Qt6? Is there more information available?
Thanks
Richard
_
> Sad to see, there is no recording... :(
>
> Any materials/slides to share?
How hard would it be to upload a series of short Youtube videos about:
- how to contribute to Qt (walk through gerrit, git command line)
- best practices to use QtCreator
- for hacking and testing changes in Qt
-
> I'm wondering if anyone is interested in my experiences with using the
> Qt/Quick technology in a non standard way. I was specifically thinking of
> the QSkinny theming system and the implications of doing scene graph node
> composition ?
What is the latter?
I'm not sure if that is what You hav
> You can download snapshot via online installer. At the moment we don't publish
> separate src packages to download.qt.io
Thanks, but I can't see any Qt snapshots in the online installer. Some of the
"preview" packages there are even outdated.
This is what I see: https://pasteboard.co/Iz16Exp.pn
> I guess that building Qbs in Coin is the only way to build against unreleased
> Qt versions.
How much effort would that be to set up and to maintain for an external
contributor? Any experiences?
___
Development mailing list
Development@qt-project.org
Hello,
I would like to build and test Qbs against development snapshots of Qt in order
to prevent disasters like https://bugreports.qt.io/browse/QBS-1492 from
happening again.
Are there any snapshots of the Qt SDK available in some form? Something like
the 7z packages used by the installer too
Hello,
I've been trying to use windeployqt from a cross-compiled (mingw-w64 on
Linux) Qt. I must be the only person on the planet doing this because there
is a bug in windeployqt preventing it. The PE functionality is guarded by
Q_OS_WIN.
https://code.qt.io/cgit/qt/qttools.git/tree/src/shared/winu
> Qt used to make a point on having superior documentation to most other
> frameworks, and it was (and still is) one of the reasons for its success.
> Whatever we can do to help make the documentation better is something I
> think we should do.
Is it well known, how many QtCreator users are even
>> Thanks, Ivan. While this is true for other libs like xcb, Qt does not ship
>> icu. It uses either the one provided by the system or a thin replacement
>> resulting in a reduced localization feature set according to
>> https://wiki.qt.io/Qt_5_ICU#Design_Principles
>
> Linux binaries are shipped
On 05.06.2019 21:28, Иван Комиссаров wrote:
> AFAIK -R . is used to load that icu libraries I told you about in Gerrit.
>
> Otherwise it will try to load the system ones instead of the shipped ones
> with Qt.
Thanks, Ivan. While this is true for other libs like xcb, Qt does not ship
icu. It uses
> Excellent yes. That was a recent addition to the installer framework,
> very useful for exactly that purpose.
Thanks for _all_ replies! Actually, the configure command line in the COIN
logs differs from
https://code.qt.io/cgit/qtsdk/qtsdk.git/tree/packaging-tools/bld_config?h=v5.12.3-packaging
s
> I think this was asked on the interest list back in January [1].
I did search on the Qt mailing lists, but even when I type exactly the
subject of the thread you referred to, google doesn't find it. I would
expect "Official builds configuration options site:lists.qt-project.org" to
bring this p
Hi,
where can I find the configure command lines that have been used for Qt
binary releases provided at https://download.qt.io/official_releases/qt/ ?
Is there also more information available about the environment they have
been built on? I am particularly interested in the Linux release.
Thanks
> - People nowadays will just use the flatpak / appimage / snap / whatever
I can see how that works for single-binary GUI applications.
Do you know any example for a complex Qt-based multi-binary (preferably
command line usage) application that does that well?
__
> There are more tweaks that would be nice to apply to the UI to make it
> better. Does the new version make this any easier? What's your advice for
> people who'd like to contribute UI tweaks? What's the best way to
> proceed? (in the sense of empowering potential contributors instead of
> asking
> This was a case where I thought it is obvious already. The definition of
> "Done" (given by Thiago earlier in this thread) has not applied for a
> long time anymore. There hasn't been maintainer for a long time. I
> understand this leave use cases in the dust but this can only by averted
> if so
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
comman
> 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
> 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 Qb
>> 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
Hi,
I would like to know more about https://git.qt.io
- What's the purpose and the future plan?
- Is it available to registered users at qt.io ? I couldn't log in.
- Is it connected to gerrit or can it be connected?
- Does it offer gitlab CI?
Thanks
Best regards
Richard
_
> But do note that our parallelism isn't that bad right now. There's a long
> critical path before parallel things can currently be built, but once QtQml
> is
> built, the number of jobs that can be launched in parallel is very big. What
> doesn't need that build isn't very large.
Could you e
On 18.12.2018 21:20, Thiago Macieira wrote:
> On Tuesday, 18 December 2018 11:44:38 PST Denis Shienkov wrote:
>> If Qt maintainers says that they will not remove the QtCreator && QBS
>> integration in future (I'm about QBS project manager plugin), then I
>> will not worry (don't care) about CMake.
> On Sunday, 16 December 2018 20:12:47 PST Richard Weickelt wrote:
>> ... and if you cross-compile, you definetly don't want to your build system
>> to stick its nose into your system librararies on any platform.
>
> No, you really DO. The issue is what "system
> Here in Fedora, we actually *want* CMake to find system libraries. The
> situation on Windows is of course different, and third-party packages for
> GNU/Linux may or may not want to use the system libraries, but our
> distribution packages definitely want to use them.
... and if you cross-co
Tuukka,
On 02.11.2018 13:44, Tuukka Turunen wrote:
>
> Exactly. We are very pleased if there are people who start to contribute
> to Qbs. So far it has been very little by others than employees of The Qt
> Company.
Here are some possible reasons:
- the Qbs core code base is complex
- the code co
> It seems to differ quite a bit in scale. That blog post has 7 comments.
> Compare it to nearly 150 on "Deprecation of Qbs" in 3 days and countless
> emails here on the mailing list. I seem to wonder if the whole issue
> could be avoided if it was approached a bit more diplomatically from the
On 30.10.2018 18:14, NIkolai Marchenko wrote:
> For anyone interested in QBS survival, let's fill the sheet with QBS
> ecosystem.
> Maybe if we show TQtC that people are actually using it they will reconsider.
>
> Post your projects (and ones you know of) here:
>
> https://docs.google.com/sprea
> Can you name any project of moderate complexity using it?
https://github.com/bjorn/tiled
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
> Qbs is something that has been developed almost exclusively by The Qt
> Company. As such, TQtC had to also look at it from a business perspective
> and how it fits into the larger picture of making Qt successful. To make
> a long story short, while Qbs is pretty cool and interesting technology,
>> How much custom c++ code does it contains for just qt?
>
> which build system which supports automatic calling of moc doesn't have
> specific code for qt ?
Qbs :-)
At least no C++ code.
___
Development mailing list
Development@qt-project.org
http://
> There are JavaScript interpreters for microcontrollers (see Duktape and
> Jerryscript). But those are designed to run on tens of *kilobytes* of RAM.
> You
> can't compare them to Qt, as they have special limitations to run that way.
> For example, neither implementation supports "eval".
I wo
43 matches
Mail list logo
