On sábado, 10 de setembro de 2016 09:21:58 PDT Marc Mutz wrote:
> (and the less obvious one: why are changes to the config system done in 5.8,
> and not LTS? They don't touch code, after all).
You mean the complete rewrite of configure and configure.exe, with a huge chunk
of new qmake code that w
On 08/09/16 14:34, Christian Kandeler wrote:
On 09/08/2016 02:03 PM, Bo Thorsen wrote:
Ok, go try it. Create a simple python or perl script that reads a file.
The file just has a single number N inside it. And based on N the script
outputs those files:
Here's the CMake version:
cmake_mi
On 08/09/16 14:34, Christian Kandeler wrote:
On 09/08/2016 02:03 PM, Bo Thorsen wrote:
Ok, go try it. Create a simple python or perl script that reads a file.
The file just has a single number N inside it. And based on N the script
outputs those files:
Here's the CMake version:
cmake_
Hi,
I've been developing a Qt oriented clang compiler plugin called clazy [1].
It has about 50 custom checks/warnings for common Qt and C++ mistakes.
I would like to propose clazy to be used to sanitize API of new Qt modules. Of
course, only a few of the 50 checks are relevant to API, so I will
http://lists.qt-project.org/pipermail/development/2016-September/027083.html
On 9 September 2016 at 08:39, Marc Mutz wrote:
> Hi,
>
> I don't get notification emails from Gerrit anymore, and since the big
> downtime of Gerrit and dev ML two(?) days ago only sporadically.
>
> Anyone else seeing t
In my qtc-based projects, there is a lot of doxygen.
Qtc contains a highlighter for doxygen-style comments,
but no highlighter for doxyfile,
I've wrote this (a little bit smarter than simple INI format)
and using this for some time. I'd like to share , probably this can be
helpful for someone else.
10.09.2016, 15:32, "Marc Mutz" :
> Hi Lars,
>
> On Friday 09 September 2016 15:21:04 Lars Knoll wrote:
>> A cherry-picking approach for the LTS branch can make sense, as it
>> distributes the burden of bringing the bug fix to both the stable and LTS
>> branch over all developers and doesn’t pu
Hi Lars,
On Friday 09 September 2016 15:21:04 Lars Knoll wrote:
> A cherry-picking approach for the LTS branch can make sense, as it
> distributes the burden of bringing the bug fix to both the stable and LTS
> branch over all developers and doesn’t put it on the one person having to
> do the merg
Il 09/09/2016 17:48, Frederik Gladhorn ha scritto:
> Since the problem is very likely something with the mail setup being broken,
> we'll disable gerrit mails - so expect not to see any emails from gerrit
> until
> this is fixed. Occasional mail might still make it, we'll try giving mails a
> s
On Friday 09 September 2016 13:56:26 Edward Welbourne wrote:
> https://codereview.qt-project.org/170641 -- qtwayland
> https://codereview.qt-project.org/170643 -- qtserialbus
> https://codereview.qt-project.org/170652 -- qtscxml
These three are exiting TP state on 5.8, so the whole API needs to be
On joi, 8 septembrie 2016 20:22:25 EEST Jake Petroules wrote:
> I just found a perfect example of how hard building a JAR file is in qmake
> for example, compared to qbs:
IMHO will be even easier if instead:
qbs-javac-scan.qbs:
[...]
files: [
"io/qt/qbs/**/*.java"
]
[...]
You'll w
Hi,
I don't get notification emails from Gerrit anymore, and since the big
downtime of Gerrit and dev ML two(?) days ago only sporadically.
Anyone else seeing this? Or is it KDAB's mail server problem?
Thanks,
Marc
--
Marc Mutz | Senior Software Engineer
KDAB (Deutschland) GmbH & Co.KG, a KD
On Sep 9, 2016, at 4:39 AM, Kevin Kofler
mailto:kevin.kof...@chello.at>> wrote:
Jake Petroules wrote:
Another thing that's very hard to do in other build systems is building
Java code. The class files emitted by a Java compiler actually vary
depending on the contents of the Java files themselves
13 matches
Mail list logo
