Hi, anybody can build gpsbabel ?
error Qt requires a C++11 compiler and yours does not seem to be that.
a long list of errors and
In file included from /usr/include/qt5/QtCore/qshareddata.h:46:0,
from /usr/include/qt5/QtCore/qdatetime.h:45,
from /usr/include/qt5
Here I attached a patch which fixes that error.
To apply it, copy that file to your directory with gpsbabel.SlackBuild
and run the command:
patch -p1 < cxx-fix.patch
It adds "-std=c++11" to the C++ compiler flags.
After that gpsbabel.SlackBuild should build fine.
However, on my machine
After building and installing qt5-webkit, I ran the SlackBuild again and
the command "make gui" in the SlackBuild threw another error like "Qt
requires a C++11 compiler and yours does not seem to be that.".
So I made another patch which fixes that error and attached it here.
Marek Srejma schr
On 6/12/17, Frédéric Falsetti wrote:
> Hi, anybody can build gpsbabel ?
>
> error Qt requires a C++11 compiler and yours does not seem to be that.
> a long list of errors and
>
> In file included from /usr/include/qt5/QtCore/qshareddata.h:46:0,
> from /usr/include/qt5/QtCore/qdate
I can confirm that the gpsbabel fails to build if you have Qt5
installed. Add this line in the SlackBuild, right before `autoreconf
-vif` to make sure it uses Qt4 instead:
sed -i 's/qmake-qt5 qmake-qt4 qmake/qmake qmake-qt4 qmake-qt5/g' configure.in
I have tested this and it works here.
Dan
On
>> Looks like it's trying to build against Qt5. I've only tested against Qt4.
>>
>> Also there is a newer version, 1.5.4, but I've held back at 1.5.3
>> since 1.5.4 requires Qt5. Can you try a simple version bump and see
>> if the errors go away with 1.5.4?
It seems the transition to qt5 is inev
On 6/15/17, Willy Sudiarto Raharjo wrote:
>>> Looks like it's trying to build against Qt5. I've only tested against
>>> Qt4.
>>>
>>> Also there is a newer version, 1.5.4, but I've held back at 1.5.3
>>> since 1.5.4 requires Qt5. Can you try a simple version bump and see
>>> if the errors go away
>> It seems the transition to qt5 is inevitable. Simply holding back to
>> 1.5.3 means it's one year behind and definitely inability to work
>> properly with new devices and the lack of GeoJSON write support
>
> Good point. I'm putting together an update to 1.5.4, and I'll leave a
> note in the R
