Skip to main content
changed headline
Link
Frau Schmidt
  • 1.2k
  • 9
  • 27

Why using Keep up to date a cpp-plugin(windows) for QGIS LTR 2.14?with less effort

added 774 characters in body
Source Link
Frau Schmidt
  • 1.2k
  • 9
  • 27

We have two c++-plugins for QGIS and thought with the LTR release we are bit saver against the fast version-changes. Today I updated my QGis from 2.14.0 to 2.14.4 and had to recognise, that the plugins couldn't been loaded. Could be the reason therefore the new QGIS is built and deployed with a newer GDAL/OGR?

Or is there for every build of QGis requiered to have a seperate build for the plugin?

So I have to download and update the sources again and recreate the VS Project for every subversion of the LTR?

EDIT:

Found out, need new gdal_i.lib and spatialite_i.lib to compile, so I changed it in the Linker-Properties of my VS-Project. Then I need the libs qgis_core and qgis_gui. Downloaded them with the qgis-devel and linked it. But now I get the following Linker error:

Fehler 1058 error LNK2001: Nicht aufgelöstes externes Symbol ""public: virtual bool __thiscall QgsSymbolLayerV2::writeDxf(class QgsDxfExport &,double,class QString const &,class QgsSymbolV2RenderContext *,class QgsFeature const *,class QPointF)const " (?writeDxf@QgsSymbolLayerV2@@UBE_NAAVQgsDxfExport@@NABVQString@@PAVQgsSymbolV2RenderContext@@PBVQgsFeature@@VQPointF@@@Z)". QGISFunc.obj tb4qgisplugin

But in code I can't find any hint, never use sth like DXF. Any idea?

We have two c++-plugins for QGIS and thought with the LTR release we are bit saver against the fast version-changes. Today I updated my QGis from 2.14.0 to 2.14.4 and had to recognise, that the plugins couldn't been loaded. Could be the reason therefore the new QGIS is built and deployed with a newer GDAL/OGR?

Or is there for every build of QGis requiered to have a seperate build for the plugin?

So I have to download and update the sources again and recreate the VS Project for every subversion of the LTR?

We have two c++-plugins for QGIS and thought with the LTR release we are bit saver against the fast version-changes. Today I updated my QGis from 2.14.0 to 2.14.4 and had to recognise, that the plugins couldn't been loaded. Could be the reason therefore the new QGIS is built and deployed with a newer GDAL/OGR?

Or is there for every build of QGis requiered to have a seperate build for the plugin?

So I have to download and update the sources again and recreate the VS Project for every subversion of the LTR?

EDIT:

Found out, need new gdal_i.lib and spatialite_i.lib to compile, so I changed it in the Linker-Properties of my VS-Project. Then I need the libs qgis_core and qgis_gui. Downloaded them with the qgis-devel and linked it. But now I get the following Linker error:

Fehler 1058 error LNK2001: Nicht aufgelöstes externes Symbol ""public: virtual bool __thiscall QgsSymbolLayerV2::writeDxf(class QgsDxfExport &,double,class QString const &,class QgsSymbolV2RenderContext *,class QgsFeature const *,class QPointF)const " (?writeDxf@QgsSymbolLayerV2@@UBE_NAAVQgsDxfExport@@NABVQString@@PAVQgsSymbolV2RenderContext@@PBVQgsFeature@@VQPointF@@@Z)". QGISFunc.obj tb4qgisplugin

But in code I can't find any hint, never use sth like DXF. Any idea?

Source Link
Frau Schmidt
  • 1.2k
  • 9
  • 27

Why using QGIS LTR 2.14?

We have two c++-plugins for QGIS and thought with the LTR release we are bit saver against the fast version-changes. Today I updated my QGis from 2.14.0 to 2.14.4 and had to recognise, that the plugins couldn't been loaded. Could be the reason therefore the new QGIS is built and deployed with a newer GDAL/OGR?

Or is there for every build of QGis requiered to have a seperate build for the plugin?

So I have to download and update the sources again and recreate the VS Project for every subversion of the LTR?