On Fri, 30 Oct 2015 17:56:56 +0000 "Garth N. Wells" <[email protected]> wrote:
> I'd like to flag this up again. I get problems building DOLFIN when I > have Qt dev packages installed. I don't have an interest in debugging > this, so I usually just remove the Qt dev packages. This isn't a > solution for all users, and it's a bad experience for new users. The solution might be configuring with -DDOLFIN_ENABLE_QT:BOOL=OFF. > > Any objections to removing the Qt dependency now? No. Jan > > Garth > > > > > > > On 15 January 2015 at 15:18, Jan Blechta <[email protected]> > wrote: > > > Garth suggested removing Qt dependency. Here are some facts to be > > considered > > > > 1. DOLFIN links to libQtCore, libQtGui > > - cost: > > - linking problems, recently on support mailing list but > > rather rare > > - size of libdolfin.so, Release build type, with everything > > except PaStiX and slepc4py: > > - with Qt 8M > > - without Qt 8M > > - memory footprint after "from dolfin import *" > > VIRT RES SHR > > - with Qt 751M 101M 39M > > - without Qt 679M 97M 48M > > This is rather negligible. > > - advantages: > > - Plot window can be closed! > > > > 2. there is plot-qt demo demonstrating how interactive widget > > allowing > > - basically what usual VTK plotting does > > - plus reporting some numbers on mouse hover > > - plus marking cells by clicking on them > > for the prize of 252 lines of C++ code (without comments and > > blank lines). According to git log in that directory, it seems that > > the code is not fragile and did not need maintenance nearly at > > all so far. > > > > Similarly, Qt, QVTK related code in dolfin/plot is rather > > minimal and does not require much maintenance. But this isn't so > > straightforward to check. > > > > Jan > > _______________________________________________ fenics mailing list [email protected] http://fenicsproject.org/mailman/listinfo/fenics
