El domingo, 22 de julio de 2018 18:54:14 -03 Kevin Kofler escribió:
> Thiago Macieira wrote:
> > Specifically, the problem with TensorFlow is that it wants to download its
> > dependencies when you compile it, then compile them at the same time. That
> > can't work because the build servers don't h
Thiago Macieira wrote:
> Specifically, the problem with TensorFlow is that it wants to download its
> dependencies when you compile it, then compile them at the same time. That
> can't work because the build servers don't have internet connectivity.
+1, this is also a hard, non-negotiable requirem
On Sunday, 22 July 2018 10:34:13 PDT Tobias Hunger wrote:
> > "More than one" would be quite a challenge.
>
> We can not expect people to drop their preferred set of tools to work on
> Qt. That is a sure-fire way to reduce contributions from outside of our
> core community.
Sure, but we compare th
Hi Thiago,
On Sun, Jul 22, 2018, 17:35 Thiago Macieira
wrote:
> > A) works with IDE(s) -- preferably more than one
>
> Hello Tobias
>
> The fact that we have an IDE of ours means this one should be reasonably
> easy
> to address, as we can make that IDE work with the tool. So long as the
> tool
On Sun, Jul 22, 2018, 12:58 Иван Комиссаров wrote:
> But only qmake works fine with new clang model, other build systems pass
> incorrect parameters to clang so it can’t compile my files (code model
> complains about missing std:: classes/functions, however the code compiles
> so project file is
On Sunday, 22 July 2018 03:57:37 PDT Иван Комиссаров wrote:
> That’s it. You pointing too much attention to the Linux distros and
> maintainers, which is very important, but you are using wrong arguments.
> Give those maintainers a good tool and they will be happy. And the «good
> tool» is not the
On Sunday, 22 July 2018 01:57:59 PDT Tobias Hunger wrote:
> All these are very reasonable to ask for. I personally would like to add
> the following point for consideration:
>
> 4) Toolable
>
> A) works with IDE(s) -- preferably more than one
Hello Tobias
The fact that we have an IDE of ours m
On Sunday, 22 July 2018 02:20:04 PDT Christian Gagneraud wrote:
> > It's EXACTLY the reason our seniormost engineers spent three days trying
> > to
> > upgrade TensorFlow in Clear Linux. That's not your junior guy who only
> > knows how to run "npn install". We're talking about people who had been
On Sunday, 22 July 2018 03:31:42 PDT Kevin Kofler wrote:
> PS: In addition, https://bazel.build/ itself describes Bazel as "Beta". In
> particular, "Bazel is not yet covered by a deprecation policy, may be
> subject to backward-incompatible changes, and is missing some features."
>
> I do not thin
El dom., 22 de jul. de 2018 06:40, Christian Gagneraud
escribió:
> On 22 July 2018 at 00:42, Kevin Kofler wrote:
> > Bogdan Vatra via Development wrote:
> >> Anyway IMHO is more important to have a clean, nice and easy to use
> syntax
> >> and to be tooling friendly than 1.b.
> >
> > A custom bu
On Sun, Jul 22, 2018 at 3:11 AM Kevin Kofler wrote:
>
> Jason Newton wrote:
> > My conclusion for the build system with the brightest future is bazel
>
> Looking at this, this build system depends on Python AND Java! They ship
> binaries with everything bundled, but that is a huge bloat (and it al
Hi,
În ziua de duminică, 22 iulie 2018, la 12:18:06 EEST, Tobias Hunger a scris:
> On Sat, Jul 21, 2018, 14:49 Jean-Michaël Celerier <
>
> jeanmichael.celer...@gmail.com> wrote:
> > +1, I was flabbergasted when the big objection against CMake in Qt 6
> > boiled down to "it does not supports all th
Hi,
În ziua de duminică, 22 iulie 2018, la 12:11:44 EEST, Tobias Hunger a scris:
> On Sat, Jul 21, 2018, 07:38 Bogdan Vatra via Development <
>
> development@qt-project.org> wrote:
> > You really hate QBS don't you ? :)
>
> Do you have so few arguments for qbs that you need to appeal to emotions?
Sounds like you have a configuration problem in Qt Creator. I've been using
qtc with the clang code model and CMake projects for over a year on various
C++11/14/17 projects and everything works fine.
$ echo '#include \nint main() { std::string_view s("foo"); }'
> main.cpp ; echo 'project(foo CXX)\
> 21 июля 2018 г., в 23:04, Thiago Macieira
> написал(а):
>
> On Saturday, 21 July 2018 10:39:49 PDT Иван Комиссаров wrote:
>> 1. IDE integration. I really need the IDE know the correct CXX flags for
>> each separate file in my project - that is includes, c++ version and so on.
>> Currently i’m
I wrote:
> Bazel is still fairly new and adoption is low, especially in the Free
> Software world.
PS: In addition, https://bazel.build/ itself describes Bazel as "Beta". In
particular, "Bazel is not yet covered by a deprecation policy, may be
subject to backward-incompatible changes, and is mis
Jason Newton wrote:
> My conclusion for the build system with the brightest future is bazel
Looking at this, this build system depends on Python AND Java! They ship
binaries with everything bundled, but that is a huge bloat (and it also does
not help GNU/Linux distributions, which will want to u
My bad, I thought that you were counting in Kloc of code, not in kilobytes.
That's in my opinion a weird metric for measuring code since indenting
with, say, 4 spaces instead of 1 tab would certainly end up giving wild
differences.
cloc cmake/Source/cmQt*
--
On Sun, Jul 22, 2018, 10:20 AM Christian Gagneraud wrote:
> On 22 July 2018 at 14:05, Thiago Macieira
> wrote:
> > On Saturday, 21 July 2018 16:52:44 PDT Jason Newton wrote:
> >> -Ability to build external libraries from source or pull in binary
> >> libraries
> >
> > This is not a feature. It's
On 22 July 2018 at 00:42, Kevin Kofler wrote:
> Bogdan Vatra via Development wrote:
>> Anyway IMHO is more important to have a clean, nice and easy to use syntax
>> and to be tooling friendly than 1.b.
>
> A custom build system is always a major pain point for distributions. A
> circular dependenc
On 22 July 2018 at 14:05, Thiago Macieira wrote:
> On Saturday, 21 July 2018 16:52:44 PDT Jason Newton wrote:
>> -Ability to build external libraries from source or pull in binary
>> libraries
>
> This is not a feature. It's a misfeature.
>
> It's EXACTLY the reason our seniormost engineers spent
On Sat, Jul 21, 2018, 14:49 Jean-Michaël Celerier <
jeanmichael.celer...@gmail.com> wrote:
> +1, I was flabbergasted when the big objection against CMake in Qt 6
> boiled down to "it does not supports all the architectures that Qt
> supports",
>
IIRC the bid showstopper was that CMake does not su
On Sat, Jul 21, 2018, 07:38 Bogdan Vatra via Development <
development@qt-project.org> wrote:
> You really hate QBS don't you ? :)
Do you have so few arguments for qbs that you need to appeal to emotions? :)
Anyway IMHO is more important to have a clean, nice and easy to use syntax
> and
> to b
Hi Thiago,
On Sat, Jul 21, 2018, 04:36 Thiago Macieira
wrote:
> [...] I'd like to add the following
> extra requirements to the buildsystem we choose to use. This is in
> addition to
> the functionality requirements.
>
> [...]
>
1) Ease of obtention
2) Track record
>
> 3) Community support
>
24 matches
Mail list logo