In addition to that, he has been "shadow-maintaining" the port over
> the last year, so this would rather reflect reality.
>
> https://codereview.qt-project.org/#/q/owner:%22Oliver+Wolff+%253Coliver.wolf
> f%2540qt.io%253E%22,n,z
+1
Thanks Maurice and Oliver for the ef
let people know what the current state is. We already have too
few people who test our betas, so if we stop calling them that, we'll have
even fewer.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
ime where we
> fuzzed Qt's image formats.
I don't think it was reported against DDS. We fuzzed all the image format
readers after a report against one of them.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
__
See
https://developercommunity.visualstudio.com/content/problem/76198/vs-2017-compiler-creates-broken-debug-build-using.html
The fix is slated for 15.7.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
ily think of for using the compressed JPEG data is
lossless rotation in multiples of 90°.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
___
Development mailing list
Development@qt-
power of Clang.
Does it mean other compilers are not supported? That's a showstopper.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
ex C++ code into
> existing C & C++98 projects. You can use any C++11 compiler to compile
> the resulting code.
So I need Clang to parse my code. Will it parse Microsoft headers properly?
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
On Monday, 23 April 2018 22:35:36 PDT Phil Bouchard wrote:
> On 04/23/2018 10:34 PM, Thiago Macieira wrote:
> > On Monday, 23 April 2018 18:46:05 PDT Phil Bouchard wrote:
> >>>> - QML is an interpreted language thus it can be reverse engineered and
> &g
> these efforts.
>
> Anyway I have high hopes for Qt as I am using it since January 2000.
I meant C++.
We'll continue using C++ and have no intention of changing.
Your solution is technically a new language.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect -
oking at the code
if the problem is still there.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
s" which should be renamed
> then.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
*is* flaky because it succeeded in one of the retries, but
apparently failed the other 16 runs.
Can someone take a look?
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
___
Developm
On Wednesday, 2 May 2018 00:29:18 PDT Thiago Macieira wrote:
> 8 out of 8 integrations attempted in both qtbase/dev and qtbase/5.11
> yesterday resulted in
Make that 9 of 9.
I'll stop trying to stage anything in qtbase until further notice.
--
Thiago Macieira - thiago.macieira (AT
On Wednesday, 2 May 2018 13:45:46 PDT Phil Bouchard wrote:
> So what do you think Qt? Are you:
>
> 1) Not interested or whatsoever
> 2) Interested to give a trial version a shot
> 3) You get the idea already and might consider it
Probably (1).
--
Thiago Macieira - thia
only.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
om.
To all users: please continue submitting contributions through the
contribution system as much as you can. Submitting patches via the bug
reporting tool may not work if the assignee or maintainer in question does not
work for the Qt Company and there's no one who does that is willin
| defined(__x86_64__) || \
defined(__amd64) || defined(__MIPSEL__)
It's possible it's one of those and there's something else wrong. I don't have
access to the toolchain and therefore can't test to see what it is.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Soft
On Wednesday, 16 May 2018 09:31:56 PDT Oswald Buddenhagen wrote:
> On Wed, May 16, 2018 at 09:06:59AM -0700, Thiago Macieira wrote:
> > Please note this grants The Qt Company this right, presumably because
> > that "Feedback" is submitted to a web service they control.
ouldn't be submitting it under CLA (though you need it for
> purely technical reasons). qt employees obviously also don't submit
> under the CLA (because the code is already owned by tqtc) even though we
> use the same technical process.
You have not convinced me enough.
I
So they are defined but not required to be equal to something?
Ok, will change the change.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
___
Development mailing list
Development@qt-
eryone, but write access
> should be limited to The Qt Company.
Is the source code for licheck going to be added to the repository?
If not, then the binary cannot be added to the a Qt Project repository.
--
Thiago Macieira - thiago.macieira (AT) intel.com
So
On Friday, 18 May 2018 12:53:00 PDT Kai Koehne wrote:
> > From: Development on
> > behalf of Thiago Macieira
> >
> >
> > Is the source code for licheck going to be added to the repository?
>
> No, I'd only add the binaries.
>
> > If not, t
On Friday, 18 May 2018 18:18:02 -03 Thiago Macieira wrote:
> > Just for clarification: The official source packages contain the licheck
> > executables already. My aim is that a git checkout and the source packages
> > we provide contain the very same content.
>
> I unders
ngs make finding our warnings more difficult and it
affects our reputation because people see warnings and think they're Qt's
fault.
Qt3D maintainers, please take action to make sure those warnings disappear
from our builds.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software
m/qt and qt-
project.org, but other places in qt.io could be acceptable.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
___
Development mailing list
Development@qt-project.org
ht
git/qt-creator/qt-creator.git/tree/qtcreator.pro#n123?
configure no longer saves anything, whether you pass -opensource or -
commercial. The options are currently dummy.
But they could be changed back to saving something.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect -
On Thursday, 24 May 2018 09:58:43 -03 Kai Koehne wrote:
> Thanks, that's actually an interesting idea. Obvious downside is that you
> need network access ... but you can argue that, if people are using git,
> they most likely have it
Uh... not really. I use git while on the plane :
tp://download.qt.io/archive/qt. But official releases are there of course
> and that's why I think it should be OK to remove those pre-releases.
Snapshots yes. For the others, remove binaries but please keep the sources.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Arch
y used in order to comply with the LGPL, but we know most
people don't do that. If it's not too much to ask, we should help them comply
with the LGPL.
That said, we don't need those mirrored. They can be kept in a colder archive.
--
Thiago Macieira - thiago.macieira (AT) i
o grab licheck
> and put it in the right spot, then error out? Anything that avoids manual
> steps that are only found in the online documentation.
Printing the instructions if licheck isn't found is preferable. Hitting the
network during automated builds is really bad pract
On Thursday, 24 May 2018 16:45:58 -03 Thiago Macieira wrote:
> The problem is that those sources are *not* what's on the repository, since
> our process includes a little more besides git archive. I know I couldn't
> recreate the release, if just given a tarball.
I meant &
ely to simply be Linux containers, so you should be expecting the host
device to be like a Raspberry Pi or a low-end Intel Atom CPU with 1 GB of RAM
or so.
[It goes without saying that Qt could be used for digital signage, but it's a
stretch to call those IoT]
--
Thiago Macieira - thiago.
s have a
lot of internals that allocate memory too, in the form of vectors, strings,
signal-slot connecion tables, etc.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
___
Development m
ar use and hardly reusable. You're getting close to
static memory allocation, which is when you decide at compile time that you're
going to have N such objects and never more. That's how MCU-class OSes
implement TCP/IP for example. They can have at most an configuration-time
ch
g/images/f/ff/JavaScript_Meets_Zephyr.pdf
Disclaimer: Sakari is a colleague of mine. And some of the folks at TQtC may
remember him from Nokia times, as he worked on Maemo/MeeGo.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Cen
On Saturday, 2 June 2018 10:27:28 PDT Jason H wrote:
> I heard that after 5.11 the focus will start on Qt6?
That information is outdated. There are no plans for Qt 6.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Cen
't using QtSql.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
the single-file build style.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
On Wednesday, 6 June 2018 19:57:55 PDT Thiago Macieira wrote:
> On Wednesday, 6 June 2018 19:09:00 PDT Lisandro Damián Nicanor Pérez Meyer
>
> wrote:
> > - Is it worth the trade off considering it makes finding security bugs
> > more
> >
> > complicated?
>
eader dependency and are easy to
fix).
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
On Wednesday, 6 June 2018 23:52:35 PDT Marco Bubke wrote:
> Hi
>
> I am on vacation till end of July, I am looking forward to discuss it in
> August.
Sure. Meanwhile, can we apply Lisandro's patch?
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect -
default.
So we just need a conditional to disable the building if the refactoring
plugin isn't enabled either.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
___
Development m
On Thursday, 7 June 2018 02:19:26 PDT Giuseppe D'Angelo wrote:
> Hi,
>
> On 07/06/18 05:13, Thiago Macieira wrote:
> > As you may be aware, Intel is taking security VERY seriously and I cannot
> > accept a project I contribute to having any worse policies. Our open
&g
cess to them, would they notice?
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
versions) intact.
>
> Agreed? If so I'll file a patch soon-ish.
I think it makes sense. This doesn't look like a simple change.
The missing #includes is a known issue and even then I looked at what caused
the issue for QButtonGroup and QAction. I can't find the
Corollary: existing code that cannot meet this requirement will be
deleted from the Qt Project sources.
I know this is harsh, but I think it's necessary. Let's discuss on Monday to
see if there's any solution I've missed.
--
Thiago Macieira - thiago.macieir
ly it is hard
> to imagine any security related problem in this context. We should follow
> here a reasonable instead of a fundamental approach. In that sense we
> should distinguish between different Qt Project software packages.
Good points for discussion. I'll forego giving my comment
trying to educate users. If someone downstream from us has more lax
policies, it's their business. It's their liability if something happens.
My problem is those downstream who have more strict policies. Our not
complying to them could mean Qt cannot be used. It could mean loss of
m two independent processes of the same
application
* Currently using QDataStream
** Has a lot of problems, can't really detect errors and not extensible enough
* Need more exploration, no conclusion
=== Protobuf ===
* Need volunteers to write a Proof of Concept
** plugin to protoc?
--
Th
of sqlite is released.
Good point about chasing a moving target.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
___
Development mailing list
Development@qt-project.org
http://lists.q
On Monday, 11 June 2018 13:23:21 CEST Liang Qi wrote:
> On Mon, 11 Jun 2018 at 13:17, Thiago Macieira
>
> wrote:
> > Link: https://wiki.qt.io/QtCS2018_Serialisation
> >
> > === Protobuf ===
> >
> > * Need volunteers to write a Proof of Concept
> >
* Didn't have enough time to discuss this
* We have a contribution for QAbstractCalendar
** We need a solution that enables code outside of Qt to implement their own
calendars
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect -
On Monday, 11 June 2018 22:50:09 CEST Rafael Roquetto wrote:
> Would it also make sense to explore msgpack? https://msgpack.org/
No. Msgpack is the older version of CBOR, which we already have.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Sou
or example, the next data model over would be XML. And we are indeed missing
a DOM structure for it since we deprecated QDomDocument. Can anyone see a data
structure that works for both JSON/CBOR and generic XML? More importantly, one
that is worthy of being Qt, with nice, intuitive API?
I'm s
ormat specific limitations and give you a fully typed API.
That was my original plan. The QCborValue backend can be reused for JSON as a
thin wrapper API. There's just a lot of copy & paste.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source
On Thursday, 14 June 2018 06:19:51 PDT Kevin Funk wrote:
> Heya,
>
> Patch for restoring qt5_use_modules() is here:
> https://codereview.qt-project.org/#/c/232367/
Thanks, Kevin!
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Techn
ve an API.
>From the 41 libraries that were listed in there, can you list which ones
support QString?
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
s allocation, but the use of both
QSharedPointer and QPointer isn't likely. And for Qt 6, we may reimplement
QSharedPointer on top of std::shard_ptr, so this wouldn't be available for
long as a feature.
> IOW, is a QSharedPointer specialization feasible?
To do what?
--
Th
On Thursday, 14 June 2018 23:55:33 PDT Olivier Goffart wrote:
> QDomDocument is, in fact, not deprecated.
Fair enough. But the QtXml module as a whole is Done.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Cen
eview the resulting format?
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
sConnection::connect taking PMF), a large refactoring of QFileSystemEngine
that no one has reviewed yet despite being on Gerrit for over a year, some
work for CBOR and a few other miscellaneous changes.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source
/kcwells/cveman. Both
tools consume the feed from the National Vulnerability Database from the US
NIST - https://nvd.nist.gov/.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
___
Development
the people who are working on the distribution and will apply the patches.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
out that.
Well, CVEMAN will be made public some time, hopefully. It's still in
development. For now, the other tool works.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
___
Dev
g the logo the tool should use, so...
The cve-check-tool should suffice for now. Or reading directly from the NIST
database, with specific filters for the software that Qt has as third-party.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Tec
Hello
Yesterday during the PDXCPP Meet Up, I was asked if we had come up with a good
solution to the increase in size of native binaries on Android when switching
from GCC to Clang. I reported I had no idea there was even a problem.
So, what's the status here?
--
Thiago Mac
; sources)?
Just tell configure you have win32-msvc2015. Don't try to patch to recognise
2017.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
___
Development mailing list
Deve
l for rebasing after such a massive change that deals with
whitespace only and that includes writing such a script.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
___
Development mailing li
in the fingers of one hand.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
eviews. Gerrit has no such functionality and in any case, reviewers need to
agree between themselves on what they ar reviewing.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
___
way from
> customer oriented development.
Right. I'm ok with the bot announcing formatting errors and getting people to
agree on a single format.
So long as we agree that there's no whitespace before a comma.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Int
ohmann/json).
You forgot the Asio dependency, which makes it not pure C++.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
___
Development mailing list
Development@qt-project.org
http://lis
se those hardcoded paths can also be overridden
by environment variables (XDG_CONFIG_DIRS, QT_PLUGIN_PATH and
QML2_IMPORT_PATH).
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
___
Devel
.
I'll create a P0 if my current integration fails again.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
___
Development mailing list
Development@qt-project.org
http://lists.q
6371 (RTL))
So we doubled the performance. But it wasn't enough.
Trying Eddy's suggestion instead:
https://codereview.qt-project.org/233794
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Sourc
Right, this was in dev...
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
how it
would work for Qt? Will it be invisible to our users and ourselves? Note how
Linux distros don't have it nor does Homebrew on Mac.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Techno
[2015]
Fedora 22 [2015]
Debian 9 (Stretch) [2017]
openSUSE Leap 15 [2018]
Note that this does not apply to QNX or Android, so C++14 features would not
be allowed in cross-platform code.
But we'd be able to use it in the XCB plugin. [Does QNX build that?]
--
Thi
here still valid reasons for requiring old NDKs?
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailma
I'm not asking about deployment, only building.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.
On Monday, 9 July 2018 02:39:05 PDT Alexandru Croitor wrote:
> we are using XCode 8.2, and the last supported version on 10.11 is 8.2.1. I
> don't think that the patch release will make a big difference though.
Then how about my second request?
> > If that's the latest, can we declare that buildi
to use that
content.
I'm not saying this is an actual issue here as I don't know the code. But
there could be such an issue.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
___
nt until that happens.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
1 testing.
> Seeing as we’re not building/testing on 10.13 (the latest macOS release),
> or 10.14 (the upcoming release), that would leave us with 10.12 as the
> single build/test target for macOS.
Ok, I've found a workaround to the issue meanwhile.
--
Thiago Macieira - thiago.
Thank you. Do I understand that the minimum version will be r16b?
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
___
Development mailing list
Development@qt-project.org
http://lists.qt-proj
On Wednesday, 11 July 2018 23:32:16 PDT Thiago Macieira wrote:
> On Wednesday, 11 July 2018 23:00:50 PDT Liang Qi wrote:
> > https://bugreports.qt.io/browse/QTQAINFRA-1681
> > https://codereview.qt-project.org/#/c/216306/
> > https://codereview.qt-project.org/#/c/229465
On Thursday, 5 July 2018 12:53:14 PDT Thiago Macieira wrote:
> On Mac, we kinda already require that. I'm asking to raise the minimum for
> the regular Linux builds to C++14. Specifically, I'm asking for the "auto"
> functions without trailing return type and relaxed c
1531612896/log.txt.gz
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
On Sunday, 15 July 2018 12:06:05 PDT Tor Arne Vestbø wrote:
> https://codereview.qt-project.org/#/c/222801/
>
> Is it resulting in an error, or is it just the warning you are seeing?
Uh, that's a good point. It's a warning. I guess my error is elsewhere in the
log file...
t that our style says we should make the
first one contain the line break, not the second.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
___
Development mailing list
Development@qt-proje
On Monday, 16 July 2018 00:08:44 PDT Bogdan Vatra via Development wrote:
> The clang support was added and works fine from 5.9. But I think is too late
> to switch NDK for 5.11.
I'm not asking to change compilers. I am asking whether we can require fixed
NDK headers?
--
Thia
On Friday, 20 July 2018 11:08:57 PDT Thomas Miller wrote:
> What's the best way to set up a review with changes in multiple submodules?
> Should I just push changes for 1 submodule at a time?
One submodule at a time. Don't worry about the update to qt5.git, that's done
autom
reports if not.
But until then, I will pretend it doesn't exist and will ignore the branch
that uses it to build.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
___
Developm
On Friday, 20 July 2018 19:35:48 PDT Thiago Macieira wrote:
> I'll take care of Clear Linux, but we apply the "two major distros" rule, so
> I won't be first.
Fedora and openSUSE already package it, so I will add it to Clear Linux.
However, I am blocked by https
equiring Qt source was that one would need to download and
extract qtbase, putting it alongside the tool, just so it can be built.
Instead of doing that, I suggest copying the files that one needs into the
tool's source tree and packaging those for its release.
--
Thiago Macieira
TensorFlow. Why do you think it is difficult to build? It uses bazel and
Google loves that too.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
___
Development mailing list
Dev
On Friday, 20 July 2018 19:35:48 PDT Thiago Macieira wrote:
> c) Must not require too-recent version in order to compile Qt. The versions
> found in ( a) must be sufficient to build Qt 6.0 and this must continue
> throughout Qt 6's lifetime.
Clarification: I don't mean the vers
de too.
The problem of the Qt dependency can be solved by copying the necessary files.
Why are we even discussing (1.b)? That's got a technical solution.
I thought that (2) and (3) would be a lot more contentious. Especially (2.c).
--
Thiago Macieira - thiago.macieira (AT) intel.com
Sof
rder. And all I'm asking is for experience. I don't want Qt to
be the guinea pig.
More to the point: I will not be part of the experimentation. Give me a mature
tool.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
ntinuously for 2
years.
So maybe bazel has a shot. Or ninja. Or scons. Who knows.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
___
Development mailing list
Development@qt-proje
1 - 100 of 6737 matches
Mail list logo
