Re: [Qgis-developer] Qt5 support and packages
Hi Paolo, What is the reason for doing so? Which platforms would you think require packages? Best, Matthias On 11/18/2014 08:36 AM, Werner Macho wrote: hmm - ah ok - debian testing .. well .. that should become stable somewhere soon (but looking at the arguing about systemd I am not so sure about this) funny that I don't have that specific package available in my install here .. But well, this is LMDE .. probably thats a special case .. thanks for pointing it out regards Werner On 11/18/2014 08:32 AM, Paolo Cavallini wrote: Il 18/11/2014 08:29, Werner Macho ha scritto: Hi! I am not quite sure but at least on debian it looks like that pyqt5 packages are only available built against python3. (correct me if I am wrong but I only found python3-pyqt5-* packages ..) So I assume at least on debian a switch to qt5 would also mean a switch to python3 .. aptitude show python-pyqt5 Package: python-pyqt5 New: yes State: installed Automatically installed: yes Version: 5.3.2+dfsg-3 Priority: optional Section: python Maintainer: Debian Python Modules Team python-modules-t...@lists.alioth.debian.org Architecture: amd64 Uncompressed Size: 13.7 M Depends: python (= 2.7), python ( 2.8), libc6 (= 2.14), libqt5core5a (= 5.3.0), libqt5dbus5 (= 5.0.2), libqt5designer5 (= 5.0.2), libqt5gui5 (= 5.3.0), libqt5help5 (= 5.3.0), libqt5network5 (= 5.3.0), libqt5printsupport5 (= 5.3.0), libqt5test5 (= 5.0.2), libqt5widgets5 (= 5.3.0), libstdc++6 (= 4.1.1), qtbase-abi-5-3-2, sip-api-11.1 Suggests: python-pyqt5-dbg Description: Python bindings for Qt5 PyQt5 exposes the Qt5 API to Python. This package contains the following modules: * QtCore * QtDBus * QtDesigner * QtGui * QtHelp * QtNetwork * QtPrintSupport * QtTest * QtWidgets Homepage: http://www.riverbankcomputing.co.uk/software/pyqt/ ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer -- -- Please help taking QGIS to the next level of quality. Before November 15 ! http://blog.vitu.ch/10102014-1046/crowdfunding-initiative-automated-testing ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Qt5 support and packages
Il 18/11/2014 09:09, Matthias Kuhn ha scritto: What is the reason for doing so? I think it would be useful to do some testing, so that we are free to switch once things are running well (or we warn plugin devs, etc.). Which platforms would you think require packages? I can test on Debian sid, but probably it would be useful if also a win package would be available. All the best, and thanks. -- Paolo Cavallini - www.faunalia.eu Corsi QGIS e PostGIS: http://www.faunalia.eu/training.html ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
[Qgis-developer] Lizmap load document/image form
Dear list, it would be useful/nice to have the possibility to load an image or document associated with a feature using the Lizmap web client, in edit session, is this feasible or beyond the scope of the application? thanks, Roy. ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Lizmap load document/image form
Hi Roy, You can take a look at the lizmap-web-client github issues list. https://github.com/3liz/lizmap-web-client/issues If you didn't see it you can create it. Thanks. René-Luc Le 18/11/2014 11:57, Roy a écrit : Dear list, it would be useful/nice to have the possibility to load an image or document associated with a feature using the Lizmap web client, in edit session, is this feasible or beyond the scope of the application? thanks, Roy. ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Lizmap Relation value field
Hi René-Luc i searched for this issue in QGIS bug but cannot find it, do you know if it's actually an open request? because if this does not works the realtion value is basically useless... thanks Roy. Il 17/11/2014 20.39, René-Luc Dhont ha scritto: Hi Roy, It's the way that QGIS-Server returns feature info. I thought that QGIS 2.6 has corrected this issue. René-Luc D'Hont 3Liz Le 17/11/2014 19:52, Roy a écrit : Hi all, i'm testing Lizmap web Client with value relation to map values to be inserted in a point layer, with the edit tool values are correctly displayed with a drop-down list, but the layer popup only display the numerical key value used for the relation, do i need to setup a custom popup or is this feature not supported ? thanks, Roy. ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Lizmap Relation value field
Hi, Value relations work in QGIS server - if there are single values. If there are multiple values (array) it doesn't work yet. You need either QGIS 2.6 or master. Andreas Am 2014-11-18 12:36, schrieb Roy: Hi René-Luc i searched for this issue in QGIS bug but cannot find it, do you know if it's actually an open request? because if this does not works the realtion value is basically useless... thanks Roy. Il 17/11/2014 20.39, René-Luc Dhont ha scritto: Hi Roy, It's the way that QGIS-Server returns feature info. I thought that QGIS 2.6 has corrected this issue. René-Luc D'Hont 3Liz Le 17/11/2014 19:52, Roy a écrit : Hi all, i'm testing Lizmap web Client with value relation to map values to be inserted in a point layer, with the edit tool values are correctly displayed with a drop-down list, but the layer popup only display the numerical key value used for the relation, do i need to setup a custom popup or is this feature not supported ? thanks, Roy. ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Write custom c++ application using QGIS under windows
Hi, First you must download packages listed below from OSGeo4w ( http://qgis.org/en/site/forusers/download.html OSGeo4W Network Installer (32 or 64 bit)): - qgis: QGIS desktop - grass: GRASS GIS - qgis-devel - qt4-devel - qt4-doc - qt4-libs - qwt-devel-qt4 - qwt-doc-qt - qwt-libs-qt4 In the post of Denis just replace: @set PATH=%OSGEO4W_ROOT%\bin;%OSGEO4W_ROOT%\apps\qgis-dev\bin;%PATH% @set INCLUDE=%INCLUDE%;%OSGEO4W_ROOT%\include;%OSGEO4W_ROOT%\apps\qgis-dev\include With: @set PATH=%OSGEO4W_ROOT%\bin;%OSGEO4W_ROOT%\apps\qgis\bin;%PATH% @set INCLUDE=%INCLUDE%;%OSGEO4W_ROOT%\include;%OSGEO4W_ROOT%\apps\qgis\include (replace qgis-dev with qgis) And if you want to build 64 bits applications with visual studio 2010 replace: set VS90COMNTOOLS=C:\Program Files\Microsoft Visual Studio 9.0\Common7\Tools\ call C:\Program Files\Microsoft Visual Studio 9.0\VC\vcvarsall.bat x86 with: call %PF86%\Microsoft Visual Studio 10.0\VC\vcvarsall.bat amd64 if exist c:\Program Files\Microsoft SDKs\Windows\v7.1\Bin\SetEnv.Cmd call c:\Program Files\Microsoft SDKs\Windows\v7.1\Bin\SetEnv.Cmd /x64 /Release path %path%;%PF86%\Microsoft Visual Studio 10.0\VC\bin set SETUPAPI_LIBRARY=%PF86%\Microsoft SDKs\Windows\v7.0A\Lib\x64\SetupAPI.Lib if not exist %SETUPAPI_LIBRARY% set SETUPAPI_LIBRARY=%PROGRAMFILES%\Microsoft SDKs\Windows\v7.1\Lib\x64\SetupAPI.lib Cheers, Nejia -Message d'origine- De : qgis-developer-boun...@lists.osgeo.org [mailto:qgis-developer-boun...@lists.osgeo.org] De la part de eliu1234 Envoyé : mardi 18 novembre 2014 00:15 À : qgis-developer@lists.osgeo.org Objet : Re: [Qgis-developer] Write custom c++ application using QGIS under windows I saw your post on this. And I actually used this .proj file. However, with all of your include directory, the header files qgisapplication.h does not exist in anyone of them. This is why I am confused about where it can be. Re: Write custom c++ application using QGIS under windows Nov 17, 2014; 5:47pm — by 3nids 3nids Hi, I wrote a post about that: http://3nids.wordpress.com/2014/02/27/build-and-deploy-c-qgis-app-on-windows/ I hope it helps Denis Le mardi 18 novembre 2014, eliu1234 [hidden email] a écrit : Thanks for the reply. So after that, I should just include the directory containing the header files in .proj? I tried to do this, however, i get the error in the following stackoverflow post: http://stackoverflow.com/questions/26597253/syntax-error-in-qgsapplication-h -- View this message in context: http://osgeo-org.1560.x6.nabble.com/Write-custom-c-application-using-QGIS-under-windows-tp5173377p5173395.html Sent from the Quantum GIS - Developer mailing list archive at Nabble.com. ___ Qgis-developer mailing list Qgis-developer@... http://lists.osgeo.org/mailman/listinfo/qgis-developer ___ Qgis-developer mailing list [hidden email] http://lists.osgeo.org/mailman/listinfo/qgis-developer javascript:; -- View this message in context: http://osgeo-org.1560.x6.nabble.com/Write-custom-c-application-using-QGIS-under-windows-tp5173377p5173412.html Sent from the Quantum GIS - Developer mailing list archive at Nabble.com. ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
[Qgis-developer] Processing with raster files 4GB
Hi, I am having a lot of troubles with large raster files and processing. The intermediate results can go 4GB. Processing stops with not so helpful error messages. I wonder if processing is hitting the 4GB limit. Can I force processing to use the BIGTIFF option or a raster format that can handle 4GB files? Thank you, Andreas ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
[Qgis-developer] Continuous Integration / Testing with TravisCI
Hi all, You may have noticed that there is a new symbol on the qgis github page that (hopefully) says build passing. [1] The last week I have been busy with fixing tests for integration with Travis CI. Right now, whenever somebody pushes a change to * a branch in the qgis repository (that affects master and release-x_y branches) * a pull request for the qgis repository a service called Travis CI [2] will be activated and compile the sourcecode and run the test suite there. That has the advantage that we have a reference platform (ubuntu precise for the moment) where all tests pass. This defined environment is a big step forward as it makes test runs comparable and if something goes wrong we know that code is responsible and not some other variable. Currently all tests (with a few exceptions which are disabled) are passing. And it would be excellent if it stays like that! What does that mean for developers? **Use pull requests** Whenever you open a pull request first you get the chance to test your changes without making the nice green symbol on the front page go red. You can push to these pull requests until the tests go green. For reviewers this is also nice: you don't need to spend time on pull requests that don't build or don't pass tests. **Write tests** If you implement a new feature or fix a bug, write a test for it. If somebody breaks the test, the pull request or the symbol on the github project page will turn red. This means that it's clear which commit broke the test. But the test is your feature or your bugfix! **Try to avoid rendering tests** A big portion of fixing has been spent on rendering tests. The problem with rendering tests is, that a lot of them have slight inconsistencies across systems. Gradients, anti aliasing, fonts... This all may render differently without being really a problem. But it produces a (false) alarm on another system and one needs to take measures. There are such measures: defining color intolerance, allowed pixel mismatches, known anomalies, since last week also different reference pictures... But in the end this means extra work and false alarms once in a while. We do create a software that has visual products. Therefore rendering tests are required. But think very about different possibilities before writing such a test. Maybe you can extract the WKT from a geometry and compare that against a known WKT string instead? That is less brittle, faster to test and much easier to maintain than a rendering test! If you really need to write a rendering test it is likely that it will fail on travis in the beginning. To make it pass on travis, create a pull request and wait for it to be tested. The results will be uploaded to the OTB CDash [3] where you get information what exactly you need to adjust. How many pixels failed? Visual comparison if adjusting the color tolerance a bit may help. Is an anomaly ok? Is there a need to add another reference picture? **C++ vs. Python tests** I made an earlier call for having only either one or the other. That was based on misinterpretation of test results from my side. Sorry. My current opinion is: do what you feel comfortable with. If you prefer to write C++ tests, do so. If you prefer to write Python tests, do so. If you want both, do so. The important thing is: DO IT! If you really need advice: go for python tests, they test the same functionality like C++ functions but also test the python API and therefore cover a slightly bigger area. Which tests are not fixed (on the reference platform)? * The atlas tests had interdependencies, that made some tests pass just because the environment was ok from previous ones. These tests are now changed to be independent one of another. And there is a PR that should fix the issues and re-enable the test. [4] * The symbology tests fail due to problems with sld loading. There is a pull request that partly reverts a commit that broke things and re-enables the test. [5] * The server pal labeling tests produced very different rendering results. I could imagine that they would be better off if the would also use the QGIS test font? New reference images could also be introduced. Dakota cartography's call. * The server canvas labeling tests crash on exit because of a not-yet-ended thread. Multithreading issue? Something else? * Recently the WCS test started to fail. I guess the server it uses to test does not always respond? We should either fix the server, disable the test, increase the timeout... Where to go from here? There are two things I would like to see: Many more tests :) More platforms: Travis can also handle mac. We could ask them to enable mac testing for us. But we'd first need to fix the tests there. There is a service called appveyor that runs tests for windows. But we'd first need to fix the tests there. I am very happy that there was such a great interest in the crowdfunding campaign that made it possible to do that work. THANK YOU to everybody who helped to
Re: [Qgis-developer] Continuous Integration / Testing with TravisCI
Hi On Tue, Nov 18, 2014 at 4:52 PM, Matthias Kuhn matthias.k...@gmx.ch wrote: Hi all, You may have noticed that there is a new symbol on the qgis github page that (hopefully) says build passing. [1] The last week I have been busy with fixing tests for integration with Travis CI. Right now, whenever somebody pushes a change to * a branch in the qgis repository (that affects master and release-x_y branches) * a pull request for the qgis repository a service called Travis CI [2] will be activated and compile the sourcecode and run the test suite there. That has the advantage that we have a reference platform (ubuntu precise for the moment) where all tests pass. This defined environment is a big step forward as it makes test runs comparable and if something goes wrong we know that code is responsible and not some other variable. Currently all tests (with a few exceptions which are disabled) are passing. And it would be excellent if it stays like that! What does that mean for developers? **Use pull requests** Whenever you open a pull request first you get the chance to test your changes without making the nice green symbol on the front page go red. You can push to these pull requests until the tests go green. For reviewers this is also nice: you don't need to spend time on pull requests that don't build or don't pass tests. **Write tests** If you implement a new feature or fix a bug, write a test for it. If somebody breaks the test, the pull request or the symbol on the github project page will turn red. This means that it's clear which commit broke the test. But the test is your feature or your bugfix! **Try to avoid rendering tests** A big portion of fixing has been spent on rendering tests. The problem with rendering tests is, that a lot of them have slight inconsistencies across systems. Gradients, anti aliasing, fonts... This all may render differently without being really a problem. But it produces a (false) alarm on another system and one needs to take measures. There are such measures: defining color intolerance, allowed pixel mismatches, known anomalies, since last week also different reference pictures... But in the end this means extra work and false alarms once in a while. We do create a software that has visual products. Therefore rendering tests are required. But think very about different possibilities before writing such a test. Maybe you can extract the WKT from a geometry and compare that against a known WKT string instead? That is less brittle, faster to test and much easier to maintain than a rendering test! If you really need to write a rendering test it is likely that it will fail on travis in the beginning. To make it pass on travis, create a pull request and wait for it to be tested. The results will be uploaded to the OTB CDash [3] where you get information what exactly you need to adjust. How many pixels failed? Visual comparison if adjusting the color tolerance a bit may help. Is an anomaly ok? Is there a need to add another reference picture? **C++ vs. Python tests** I made an earlier call for having only either one or the other. That was based on misinterpretation of test results from my side. Sorry. My current opinion is: do what you feel comfortable with. If you prefer to write C++ tests, do so. If you prefer to write Python tests, do so. If you want both, do so. The important thing is: DO IT! If you really need advice: go for python tests, they test the same functionality like C++ functions but also test the python API and therefore cover a slightly bigger area. Which tests are not fixed (on the reference platform)? * The atlas tests had interdependencies, that made some tests pass just because the environment was ok from previous ones. These tests are now changed to be independent one of another. And there is a PR that should fix the issues and re-enable the test. [4] * The symbology tests fail due to problems with sld loading. There is a pull request that partly reverts a commit that broke things and re-enables the test. [5] * The server pal labeling tests produced very different rendering results. I could imagine that they would be better off if the would also use the QGIS test font? New reference images could also be introduced. Dakota cartography's call. * The server canvas labeling tests crash on exit because of a not-yet-ended thread. Multithreading issue? Something else? * Recently the WCS test started to fail. I guess the server it uses to test does not always respond? We should either fix the server, disable the test, increase the timeout... Where to go from here? There are two things I would like to see: Many more tests :) More platforms: Travis can also handle mac. We could ask them to enable mac testing for us. But we'd first need to fix the tests there. There is a service called appveyor that runs tests for windows. But we'd first need to fix the tests
Re: [Qgis-developer] Qt5 support and packages
RHEL 6 has Qt 4.6 and so in order to build anything from the 2.x series it has to be built against Qt 5. http://lists.osgeo.org/pipermail/qgis-developer/2014-September/034458.html On Tue, Nov 18, 2014 at 1:09 AM, Matthias Kuhn matthias.k...@gmx.ch wrote: Hi Paolo, What is the reason for doing so? Which platforms would you think require packages? Best, Matthias On 11/18/2014 08:36 AM, Werner Macho wrote: hmm - ah ok - debian testing .. well .. that should become stable somewhere soon (but looking at the arguing about systemd I am not so sure about this) funny that I don't have that specific package available in my install here .. But well, this is LMDE .. probably thats a special case .. thanks for pointing it out regards Werner On 11/18/2014 08:32 AM, Paolo Cavallini wrote: Il 18/11/2014 08:29, Werner Macho ha scritto: Hi! I am not quite sure but at least on debian it looks like that pyqt5 packages are only available built against python3. (correct me if I am wrong but I only found python3-pyqt5-* packages ..) So I assume at least on debian a switch to qt5 would also mean a switch to python3 .. aptitude show python-pyqt5 Package: python-pyqt5 New: yes State: installed Automatically installed: yes Version: 5.3.2+dfsg-3 Priority: optional Section: python Maintainer: Debian Python Modules Team python-modules-team@lists. alioth.debian.org Architecture: amd64 Uncompressed Size: 13.7 M Depends: python (= 2.7), python ( 2.8), libc6 (= 2.14), libqt5core5a (= 5.3.0), libqt5dbus5 (= 5.0.2), libqt5designer5 (= 5.0.2), libqt5gui5 (= 5.3.0), libqt5help5 (= 5.3.0), libqt5network5 (= 5.3.0), libqt5printsupport5 (= 5.3.0), libqt5test5 (= 5.0.2), libqt5widgets5 (= 5.3.0), libstdc++6 (= 4.1.1), qtbase-abi-5-3-2, sip-api-11.1 Suggests: python-pyqt5-dbg Description: Python bindings for Qt5 PyQt5 exposes the Qt5 API to Python. This package contains the following modules: * QtCore * QtDBus * QtDesigner * QtGui * QtHelp * QtNetwork * QtPrintSupport * QtTest * QtWidgets Homepage: http://www.riverbankcomputing.co.uk/software/pyqt/ ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer -- -- Please help taking QGIS to the next level of quality. Before November 15 ! http://blog.vitu.ch/10102014-1046/crowdfunding-initiative- automated-testing ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Continuous Integration / Testing with TravisCI
Matthias, Great move from yours ! I can point you to an email I sent to the mapguide folks recently, sharing my experience with C.I. tools for GDAL. See the end of http://lists.osgeo.org/pipermail/mapguide-internals/2014-August/007518.html I'm skeptical you'll manage to build QGIS with (the free program of) AppVeyor, since GDAL reaches their build time limit. Regarding comparing images, MapServer used to use the 'perceptualdiff' utility that can accept some, invisible to the eye, differences between the reference image and the image produced. But this may be sometimes still be a bit oversensitive. Definitely a tricky subject to have rendering tests running consistently accross platforms. You mention comparing WKT, but that can be non obvious too since there might be different rounding accross platforms. Better to have a dedicated geometry comparison method that accept an epsilon when doing vertex comparisons. Even Hi all, You may have noticed that there is a new symbol on the qgis github page that (hopefully) says build passing. [1] The last week I have been busy with fixing tests for integration with Travis CI. Right now, whenever somebody pushes a change to * a branch in the qgis repository (that affects master and release-x_y branches) * a pull request for the qgis repository a service called Travis CI [2] will be activated and compile the sourcecode and run the test suite there. That has the advantage that we have a reference platform (ubuntu precise for the moment) where all tests pass. This defined environment is a big step forward as it makes test runs comparable and if something goes wrong we know that code is responsible and not some other variable. Currently all tests (with a few exceptions which are disabled) are passing. And it would be excellent if it stays like that! What does that mean for developers? **Use pull requests** Whenever you open a pull request first you get the chance to test your changes without making the nice green symbol on the front page go red. You can push to these pull requests until the tests go green. For reviewers this is also nice: you don't need to spend time on pull requests that don't build or don't pass tests. **Write tests** If you implement a new feature or fix a bug, write a test for it. If somebody breaks the test, the pull request or the symbol on the github project page will turn red. This means that it's clear which commit broke the test. But the test is your feature or your bugfix! **Try to avoid rendering tests** A big portion of fixing has been spent on rendering tests. The problem with rendering tests is, that a lot of them have slight inconsistencies across systems. Gradients, anti aliasing, fonts... This all may render differently without being really a problem. But it produces a (false) alarm on another system and one needs to take measures. There are such measures: defining color intolerance, allowed pixel mismatches, known anomalies, since last week also different reference pictures... But in the end this means extra work and false alarms once in a while. We do create a software that has visual products. Therefore rendering tests are required. But think very about different possibilities before writing such a test. Maybe you can extract the WKT from a geometry and compare that against a known WKT string instead? That is less brittle, faster to test and much easier to maintain than a rendering test! If you really need to write a rendering test it is likely that it will fail on travis in the beginning. To make it pass on travis, create a pull request and wait for it to be tested. The results will be uploaded to the OTB CDash [3] where you get information what exactly you need to adjust. How many pixels failed? Visual comparison if adjusting the color tolerance a bit may help. Is an anomaly ok? Is there a need to add another reference picture? **C++ vs. Python tests** I made an earlier call for having only either one or the other. That was based on misinterpretation of test results from my side. Sorry. My current opinion is: do what you feel comfortable with. If you prefer to write C++ tests, do so. If you prefer to write Python tests, do so. If you want both, do so. The important thing is: DO IT! If you really need advice: go for python tests, they test the same functionality like C++ functions but also test the python API and therefore cover a slightly bigger area. Which tests are not fixed (on the reference platform)? * The atlas tests had interdependencies, that made some tests pass just because the environment was ok from previous ones. These tests are now changed to be independent one of another. And there is a PR that should fix the issues and re-enable the test. [4] * The symbology tests fail due to problems with sld loading. There is a pull request that partly reverts a commit that broke things and re-enables the test. [5] * The server
Re: [Qgis-developer] Continuous Integration / Testing with TravisCI
Hi Even On 18.11.2014 16:13, Even Rouault wrote: Matthias, Great move from yours ! I can point you to an email I sent to the mapguide folks recently, sharing my experience with C.I. tools for GDAL. See the end of http://lists.osgeo.org/pipermail/mapguide-internals/2014-August/007518.html Definitely an interesting read. Good to know that ther's a short timeout with appveyor and alternatives, although mingw/wine solutions appear to be a workaround. I wonder if there is a problem with appveyor, maybe there is somebody in need of stable windows build who could sponsor this. I'm skeptical you'll manage to build QGIS with (the free program of) AppVeyor, since GDAL reaches their build time limit. Regarding comparing images, MapServer used to use the 'perceptualdiff' utility that can accept some, invisible to the eye, differences between the reference image and the image produced. But this may be sometimes still be a bit oversensitive. Definitely a tricky subject to have rendering tests running consistently accross platforms. You mention comparing WKT, but that can be non obvious too since there might be different rounding accross platforms. Better to have a dedicated geometry comparison method that accept an epsilon when doing vertex comparisons. I had a short look at that last week and found that in the end you still need to define a number of allowed mismatch pixels for some font images I compared. But maybe one could tweak the parameters. Concerning WKT you are right of course (thinking of ARM where qReal is interpreted as float vs. double on other platforms). Something like this for vertex comparisons could be good: https://docs.python.org/2/library/unittest.html#unittest.TestCase.assertAlmostEqual Matthias ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Continuous Integration / Testing with TravisCI
Hello, Le mardi 18 novembre 2014 16:05:57, Tim Sutton a écrit : Hi On Tue, Nov 18, 2014 at 4:52 PM, Matthias Kuhn matthias.k...@gmx.ch wrote: Hi all, You may have noticed that there is a new symbol on the qgis github page that (hopefully) says build passing. [1] The last week I have been busy with fixing tests for integration with Travis CI. [...] Brilliant stuff Matthias! Now we need to agree to 'no new code without tests' as a formal requirement and we will be a long way down the road towards a more stable QGIS. Great work Matthias ! Really good to see QGIS starting to keep up on the quality and industrialization side ! I second Tim on the mandatory tests with features, time to strengthen the rules for even more quality. Vincent Regards Tim Matthias [1] https://github.com/qgis/QGIS [2] http://travis-ci.org/ [3] http://dash.orfeo-toolbox.org/index.php?project=QGIS ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
[Qgis-developer] User-contributed scripts/models for Processing
Hi all and sorry for cross-posting, you may have know that we have a GitHub repo with user-contributed scripts and models for Processing [0] and Processing itself provides easy way to download them for further use. This scripts/models may contain bugs or one may want to submit feature request. Unfortunately right now there is no central place for this. So we have two options here: 1. create special category in QGIS bugtracker 2. use GitHub bugtracker Another thing, as this scripts and models (well, the biggest part of them) actually contributed by users, core developers are not responsible to their bugs. But users often think that if they use script/model in QGIS that this is QGIS bug and complain. Maybe we should add a warning/explanation to download dialog? Opinions? [0] https://github.com/qgis/QGIS-Processing -- Alexander Bruy ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Lizmap Relation value field
Hi Roy, It is the responsibility of QGIS server to deliver the correct human readable value instead of the code. So make sure that QGIS server supports that. It works fine on my server. Andreas Am 2014-11-18 14:38, schrieb Roy: Hi Andreas, i'm using Lizmap web client release_2_10 and QGIS 2.6.0 i'm talking about Lizmap web client info popup not displaying the relation description but the numeric code value used for the relation mapping; actually i don't know/uderstand if the problem is in the client or server side; not claiming that the server is not working nor the client ... thanks, Roy. Il 18/11/2014 13.44, Andreas Neumann ha scritto: Hi, Value relations work in QGIS server - if there are single values. If there are multiple values (array) it doesn't work yet. You need either QGIS 2.6 or master. Andreas Am 2014-11-18 12:36, schrieb Roy: Hi René-Luc i searched for this issue in QGIS bug but cannot find it, do you know if it's actually an open request? because if this does not works the realtion value is basically useless... thanks Roy. Il 17/11/2014 20.39, René-Luc Dhont ha scritto: Hi Roy, It's the way that QGIS-Server returns feature info. I thought that QGIS 2.6 has corrected this issue. René-Luc D'Hont 3Liz Le 17/11/2014 19:52, Roy a écrit : Hi all, i'm testing Lizmap web Client with value relation to map values to be inserted in a point layer, with the edit tool values are correctly displayed with a drop-down list, but the layer popup only display the numerical key value used for the relation, do i need to setup a custom popup or is this feature not supported ? thanks, Roy. ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Continuous Integration / Testing with TravisCI
On Tue, Nov 18, 2014 at 03:52:12PM +0100, Matthias Kuhn wrote: You may have noticed that there is a new symbol on the qgis github page that (hopefully) says build passing. [1] [..] [1] https://github.com/qgis/QGIS It does, and great work ! TravisCI is nice for the gihub integration, but for larger coverage it would be very nice to get the osgeo buildbot back [2], and ask users to setup bots for their preferred platform: http://trac.osgeo.org/osgeo/ticket/1214 Hint: Buildbot is in python, which should be familiar to the QGIS developers :) --strk; () Free GIS Flash consultant/developer /\ http://strk.keybit.net/services.html ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Continuous Integration / Testing with TravisCI
Il 18/11/2014 16:29, Vincent Picavet ha scritto: I second Tim on the mandatory tests with features, time to strengthen the rules for even more quality. I think this would be a good move, so customers are warned they have to pay also for the test. It will be difficult to implement for the works now in progress though. IMHO it wouold be important also to clarify how to define a function, and how extensive a test should be. Definitely another step towards maturity. All the best, and thanks. -- Paolo Cavallini - www.faunalia.eu Corsi QGIS e PostGIS: http://www.faunalia.eu/training.html ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Lizmap Relation value field
Hi Andreas, thanks for your answer Il 18/11/2014 17.21, Andreas Neumann ha scritto: Hi Roy, It is the responsibility of QGIS server to deliver the correct human readable value instead of the code. So make sure that QGIS server supports that. It works fine on my server. so do i need to recompile QGIS to activate this feature? i searched for documentation but i cannot find anything relevant. What i understand is that the configuration file for QGIS server is the one saved with QGIS desktop... maybe i need to edit this file to add more config parameter ? also i cannot find documentation about those (if they exists) parameters configuration... thanks, Roy. Andreas Am 2014-11-18 14:38, schrieb Roy: Hi Andreas, i'm using Lizmap web client release_2_10 and QGIS 2.6.0 i'm talking about Lizmap web client info popup not displaying the relation description but the numeric code value used for the relation mapping; actually i don't know/uderstand if the problem is in the client or server side; not claiming that the server is not working nor the client ... thanks, Roy. Il 18/11/2014 13.44, Andreas Neumann ha scritto: Hi, Value relations work in QGIS server - if there are single values. If there are multiple values (array) it doesn't work yet. You need either QGIS 2.6 or master. Andreas Am 2014-11-18 12:36, schrieb Roy: Hi René-Luc i searched for this issue in QGIS bug but cannot find it, do you know if it's actually an open request? because if this does not works the realtion value is basically useless... thanks Roy. Il 17/11/2014 20.39, René-Luc Dhont ha scritto: Hi Roy, It's the way that QGIS-Server returns feature info. I thought that QGIS 2.6 has corrected this issue. René-Luc D'Hont 3Liz Le 17/11/2014 19:52, Roy a écrit : Hi all, i'm testing Lizmap web Client with value relation to map values to be inserted in a point layer, with the edit tool values are correctly displayed with a drop-down list, but the layer popup only display the numerical key value used for the relation, do i need to setup a custom popup or is this feature not supported ? thanks, Roy. ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Continuous Integration / Testing with TravisCI
Le mardi 18 novembre 2014, 15:52:12 Matthias Kuhn a écrit : Hi all, You may have noticed that there is a new symbol on the qgis github page that (hopefully) says build passing. [1] The last week I have been busy with fixing tests for integration with Travis CI. Right now, whenever somebody pushes a change to * a branch in the qgis repository (that affects master and release-x_y branches) * a pull request for the qgis repository a service called Travis CI [2] will be activated and compile the sourcecode and run the test suite there. That has the advantage that we have a reference platform (ubuntu precise for the moment) where all tests pass. This defined environment is a big step forward as it makes test runs comparable and if something goes wrong we know that code is responsible and not some other variable. Currently all tests (with a few exceptions which are disabled) are passing. And it would be excellent if it stays like that! What does that mean for developers? **Use pull requests** Whenever you open a pull request first you get the chance to test your changes without making the nice green symbol on the front page go red. You can push to these pull requests until the tests go green. For reviewers this is also nice: you don't need to spend time on pull requests that don't build or don't pass tests. **Write tests** If you implement a new feature or fix a bug, write a test for it. If somebody breaks the test, the pull request or the symbol on the github project page will turn red. This means that it's clear which commit broke the test. But the test is your feature or your bugfix! **Try to avoid rendering tests** A big portion of fixing has been spent on rendering tests. The problem with rendering tests is, that a lot of them have slight inconsistencies across systems. Gradients, anti aliasing, fonts... This all may render differently without being really a problem. But it produces a (false) alarm on another system and one needs to take measures. There are such measures: defining color intolerance, allowed pixel mismatches, known anomalies, since last week also different reference pictures... But in the end this means extra work and false alarms once in a while. We do create a software that has visual products. Therefore rendering tests are required. But think very about different possibilities before writing such a test. Maybe you can extract the WKT from a geometry and compare that against a known WKT string instead? That is less brittle, faster to test and much easier to maintain than a rendering test! If you really need to write a rendering test it is likely that it will fail on travis in the beginning. To make it pass on travis, create a pull request and wait for it to be tested. The results will be uploaded to the OTB CDash [3] where you get information what exactly you need to adjust. How many pixels failed? Visual comparison if adjusting the color tolerance a bit may help. Is an anomaly ok? Is there a need to add another reference picture? **C++ vs. Python tests** I made an earlier call for having only either one or the other. That was based on misinterpretation of test results from my side. Sorry. My current opinion is: do what you feel comfortable with. If you prefer to write C++ tests, do so. If you prefer to write Python tests, do so. If you want both, do so. The important thing is: DO IT! If you really need advice: go for python tests, they test the same functionality like C++ functions but also test the python API and therefore cover a slightly bigger area. Which tests are not fixed (on the reference platform)? * The atlas tests had interdependencies, that made some tests pass just because the environment was ok from previous ones. These tests are now changed to be independent one of another. And there is a PR that should fix the issues and re-enable the test. [4] * The symbology tests fail due to problems with sld loading. There is a pull request that partly reverts a commit that broke things and re-enables the test. [5] * The server pal labeling tests produced very different rendering results. I could imagine that they would be better off if the would also use the QGIS test font? New reference images could also be introduced. Dakota cartography's call. * The server canvas labeling tests crash on exit because of a not-yet-ended thread. Multithreading issue? Something else? * Recently the WCS test started to fail. I guess the server it uses to test does not always respond? We should either fix the server, disable the test, increase the timeout... Where to go from here? There are two things I would like to see: Many more tests :) More platforms: Travis can also handle mac. We could ask them to enable mac testing for us. But we'd first need to fix the tests there. There is a service called appveyor that runs tests for windows. But we'd first need to fix the tests there. I
Re: [Qgis-developer] Processing with raster files 4GB
Hi, I am having a lot of troubles with large raster files and processing. The intermediate results can go 4GB. Processing stops with not so helpful error messages. I wonder if processing is hitting the 4GB limit. Can I force processing to use the BIGTIFF option or a raster format that can handle 4GB files? Hi Andreas, what tool specifically? cheers -- Giovanni -- ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Groups in Layers panel
Zoltan, Le vendredi 14 novembre 2014, 08:23:35 Zoltan Szecsei a écrit : Hi, I'm dealing with quite a number of vector map tiles, and I have grouped many of them with a common theme. What I'm finding pretty unworkable, is that when I want to set rendering style, I have to do it individually per map in that group, You could copy-paste style, not the fastest way but faster. and likewise, when I want to Identify a feature within that group, I have to click through each map in that group in order to find which map in that group holds the feature I want to identify. You can choose the up to bottom stop the first mode in identify. There are probably quite a few other actions that would be easier to work at a group level rather than a map level, but: Am I attacking this issue the wrong way, or is there a possibility that some of these actions can be processed by QGIS at a map-group level? Regards to all, Y. -- Yves Jacolin ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] QGIS 2.6 - Open postgis raster: decimal separator problem?
Le vendredi 14 novembre 2014, 10:24:36 Giovanni Manghi a écrit : Hi devs, I'm unable to open Postgis rasters using the default language setting, which is pt_PT.UTF-8 in my case. By overriding language settings, I can open Postgis rasters. Maybe something related with the decimal_point setting in LC_NUMERIC? I didn't find any bug related with this issue. Can some else confirm this problem? Should I submit a bug? How to reproduce the problem (if decimal_point == ',' and not '.'): it may be unrelated, but I recall a ticket about systems (Windows in that case) were using the , instead of . for decimal separator cause(d) issues at many levels. I can't find the ticket now and I can't remember if the issue was fixed or not. cheers! I can confirm that there was such bug in gdal/ogr but it shoud be closed in recent release. I have a mail in my archive explaining this sent by Even rouault in gdal-dev list the 22/10/2013. Y. -- Yves Jacolin ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Groups in Layers panel
On 19 Nov 2014 8:17 am, Yves Jacolin yjaco...@free.fr wrote: and likewise, when I want to Identify a feature within that group, I have to click through each map in that group in order to find which map in that group holds the feature I want to identify. You can choose the up to bottom stop the first mode in identify. You can also (with 2.6) right click with the identify tool to get a popup menu with features from all intersecting layers. Nyall ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Continuous Integration / Testing with TravisCI
On 19 November 2014 06:33, Yves Jacolin yjaco...@free.fr wrote: At camptocamp we often use Travis CI and Coverall: https://coveralls.io/ which give statistic on test coveralls. Is it worth to add it? I'd love to see something like this. Another nice extension of this work could be to add a test for documentation coverage. We could utilise https://github.com/alobbs/doxy-coverage , and keep raising the threshold required for the test until we get a nice coverage of doxygen comments. Nyall ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Continuous Integration / Testing with TravisCI
On 19 November 2014 01:52, Matthias Kuhn matthias.k...@gmx.ch wrote: I am very happy that there was such a great interest in the crowdfunding campaign that made it possible to do that work. THANK YOU to everybody who helped to get the testing integration to the next level. Matthias, This is fantastic work. Thank you so much for tackling this. (and thanks to the sponsors who made it possible too!) Nyall ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] QGIS 2.6 - Open postgis raster: decimal separator problem?
Thanks, Yves. I found the thread in gdal-dev from almost a year ago (Oct. 2013). This is fixed now: http://trac.osgeo.org/gdal/ticket/5731 but only for gdal 2.0. I was hoping to see this fixed in gdal 1.11. Thanks in advance, J. Gustavo On 18-11-2014 21:19, Yves Jacolin wrote: Le vendredi 14 novembre 2014, 10:24:36 Giovanni Manghi a écrit : Hi devs, I'm unable to open Postgis rasters using the default language setting, which is pt_PT.UTF-8 in my case. By overriding language settings, I can open Postgis rasters. Maybe something related with the decimal_point setting in LC_NUMERIC? I didn't find any bug related with this issue. Can some else confirm this problem? Should I submit a bug? How to reproduce the problem (if decimal_point == ',' and not '.'): it may be unrelated, but I recall a ticket about systems (Windows in that case) were using the , instead of . for decimal separator cause(d) issues at many levels. I can't find the ticket now and I can't remember if the issue was fixed or not. cheers! I can confirm that there was such bug in gdal/ogr but it shoud be closed in recent release. I have a mail in my archive explaining this sent by Even rouault in gdal-dev list the 22/10/2013. Y. J. Gustavo -- Jorge Gustavo Rocha Departamento de Informática Universidade do Minho 4710-057 Braga Tel: +351 253604480 Fax: +351 253604471 Móvel: +351 910333888 skype: nabocudnosor ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Write custom c++ application using QGIS under windows
Thanks so much for the answer. I am able to get the 32 bit version working. Right now, I am facing the problem of not able to run debug mode. Since all those xd.lib files does not exist with the OSGeo4W installation. Do you have any idea how to fix this? And right now, I cannot seem to print anything in this mode. I tried to use cout but my output line is not printed. I tried to setup using visual studio. But is unsure how to include these dll files without their corresponding library files. Do you have any idea on this? Thanks. In Reply To Re: Write custom c++ application using QGIS under windows Nov 18, 2014; 7:43am — by Nejia Nejia Hi, First you must download packages listed below from OSGeo4w ( http://qgis.org/en/site/forusers/download.html OSGeo4W Network Installer (32 or 64 bit)): - qgis: QGIS desktop - grass: GRASS GIS - qgis-devel - qt4-devel - qt4-doc - qt4-libs - qwt-devel-qt4 - qwt-doc-qt - qwt-libs-qt4 In the post of Denis just replace: @set PATH=%OSGEO4W_ROOT%\bin;%OSGEO4W_ROOT%\apps\qgis-dev\bin;%PATH% @set INCLUDE=%INCLUDE%;%OSGEO4W_ROOT%\include;%OSGEO4W_ROOT%\apps\qgis-dev\include With: @set PATH=%OSGEO4W_ROOT%\bin;%OSGEO4W_ROOT%\apps\qgis\bin;%PATH% @set INCLUDE=%INCLUDE%;%OSGEO4W_ROOT%\include;%OSGEO4W_ROOT%\apps\qgis\include (replace qgis-dev with qgis) And if you want to build 64 bits applications with visual studio 2010 replace: set VS90COMNTOOLS=C:\Program Files\Microsoft Visual Studio 9.0\Common7\Tools\ call C:\Program Files\Microsoft Visual Studio 9.0\VC\vcvarsall.bat x86 with: call %PF86%\Microsoft Visual Studio 10.0\VC\vcvarsall.bat amd64 if exist c:\Program Files\Microsoft SDKs\Windows\v7.1\Bin\SetEnv.Cmd call c:\Program Files\Microsoft SDKs\Windows\v7.1\Bin\SetEnv.Cmd /x64 /Release path %path%;%PF86%\Microsoft Visual Studio 10.0\VC\bin set SETUPAPI_LIBRARY=%PF86%\Microsoft SDKs\Windows\v7.0A\Lib\x64\SetupAPI.Lib if not exist %SETUPAPI_LIBRARY% set SETUPAPI_LIBRARY=%PROGRAMFILES%\Microsoft SDKs\Windows\v7.1\Lib\x64\SetupAPI.lib Cheers, Nejia -- View this message in context: http://osgeo-org.1560.x6.nabble.com/Write-custom-c-application-using-QGIS-under-windows-tp5173377p5173692.html Sent from the Quantum GIS - Developer mailing list archive at Nabble.com. ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Write custom c++ application using QGIS under windows
hi eliu1234, The *.lib of QGIS should be created by compile. For the Qt's lib , e.g *d.lib. The qwt should download from OSGeo4W, so the qwt5.lib should found in OSGeo4W. The rest qt related packages should just install a Qt from http://qt-project.org/, when compiling API using cmake, it can automatically check the QT you installed before. Remember, the minimum version of QT QGIS-2X need is 4.7.0. hope this help. Date: Tue, 18 Nov 2014 15:04:34 -0800 From: lby20...@hotmail.com To: qgis-developer@lists.osgeo.org Subject: Re: [Qgis-developer] Write custom c++ application using QGIS under windows Thanks so much for the answer. I am able to get the 32 bit version working. Right now, I am facing the problem of not able to run debug mode. Since all those xd.lib files does not exist with the OSGeo4W installation. Do you have any idea how to fix this? And right now, I cannot seem to print anything in this mode. I tried to use cout but my output line is not printed. I tried to setup using visual studio. But is unsure how to include these dll files without their corresponding library files. Do you have any idea on this? Thanks. In Reply To Re: Write custom c++ application using QGIS under windows Nov 18, 2014; 7:43am ― by Nejia Nejia Hi, First you must download packages listed below from OSGeo4w ( http://qgis.org/en/site/forusers/download.html OSGeo4W Network Installer (32 or 64 bit)): - qgis: QGIS desktop - grass: GRASS GIS - qgis-devel - qt4-devel - qt4-doc - qt4-libs - qwt-devel-qt4 - qwt-doc-qt - qwt-libs-qt4 In the post of Denis just replace: @set PATH=%OSGEO4W_ROOT%\bin;%OSGEO4W_ROOT%\apps\qgis-dev\bin;%PATH% @set INCLUDE=%INCLUDE%;%OSGEO4W_ROOT%\include;%OSGEO4W_ROOT%\apps\qgis-dev\include With: @set PATH=%OSGEO4W_ROOT%\bin;%OSGEO4W_ROOT%\apps\qgis\bin;%PATH% @set INCLUDE=%INCLUDE%;%OSGEO4W_ROOT%\include;%OSGEO4W_ROOT%\apps\qgis\include (replace qgis-dev with qgis) And if you want to build 64 bits applications with visual studio 2010 replace: set VS90COMNTOOLS=C:\Program Files\Microsoft Visual Studio 9.0\Common7\Tools\ call C:\Program Files\Microsoft Visual Studio 9.0\VC\vcvarsall.bat x86 with: call %PF86%\Microsoft Visual Studio 10.0\VC\vcvarsall.bat amd64 if exist c:\Program Files\Microsoft SDKs\Windows\v7.1\Bin\SetEnv.Cmd call c:\Program Files\Microsoft SDKs\Windows\v7.1\Bin\SetEnv.Cmd /x64 /Release path %path%;%PF86%\Microsoft Visual Studio 10.0\VC\bin set SETUPAPI_LIBRARY=%PF86%\Microsoft SDKs\Windows\v7.0A\Lib\x64\SetupAPI.Lib if not exist %SETUPAPI_LIBRARY% set SETUPAPI_LIBRARY=%PROGRAMFILES%\Microsoft SDKs\Windows\v7.1\Lib\x64\SetupAPI.lib Cheers, Nejia -- View this message in context: http://osgeo-org.1560.x6.nabble.com/Write-custom-c-application-using-QGIS-under-windows-tp5173377p5173692.html Sent from the Quantum GIS - Developer mailing list archive at Nabble.com. ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
[Qgis-developer] Problems with developing custom c++ qgis application with QtCreator and MSVC2008 on Windows
I am using qtcreator and msvc2008 for developing the c++ custom application. I followed the following tutorial to setup the system: http://3nids.wordpress.com/2014/02/27/build-and-deploy-c-qgis-app-on-windows/ Problem 1: under debug mode, I cannot create a QgsMapCanvas object. It always exit with code 1. Problem 2: under release mode, I tried to create a raster layer with the following command: QgsRasterLayer * layer = new QgsRasterLayer(http://server.arcgisonline.com/ArcGIS/rest/services/World_Imagery/MapServer?f=jsonpretty=true,raster;); It always result in a layer which is invalid. I tried the python equivalent command: layer = QgsRasterLayer(http://server.arcgisonline.com/ArcGIS/rest/services/World_Imagery/MapServer?f=jsonpretty=true,raster;); in qgis python console and it works fine. Any help is appreciated. -- View this message in context: http://osgeo-org.1560.x6.nabble.com/Problems-with-developing-custom-c-qgis-application-with-QtCreator-and-MSVC2008-on-Windows-tp5173711.html Sent from the Quantum GIS - Developer mailing list archive at Nabble.com. ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Problems with developing custom c++ qgis application with QtCreator and MSVC2008 on Windows
Hi, 1- QGIS and Qt libraries shipped with Osgeo4W are compiled using release mode so if you want to debug your application you can use RelWithDebInfo mode. 2- see: http://gis.stackexchange.com/questions/120823/how-to-load-a-wms-layer-using- pyqgis http://ieqgis.wordpress.com/2014/08/09/adding-esris-online-world-imagery-dat aset-to-qgis/ Cheers Nejia -Message d'origine- De : qgis-developer-boun...@lists.osgeo.org [mailto:qgis-developer-boun...@lists.osgeo.org] De la part de eliu1234 Envoyé : mercredi 19 novembre 2014 07:42 À : qgis-developer@lists.osgeo.org Objet : [Qgis-developer] Problems with developing custom c++ qgis application with QtCreator and MSVC2008 on Windows I am using qtcreator and msvc2008 for developing the c++ custom application. I followed the following tutorial to setup the system: http://3nids.wordpress.com/2014/02/27/build-and-deploy-c-qgis-app-on-windows / Problem 1: under debug mode, I cannot create a QgsMapCanvas object. It always exit with code 1. Problem 2: under release mode, I tried to create a raster layer with the following command: QgsRasterLayer * layer = new QgsRasterLayer(http://server.arcgisonline.com/ArcGIS/rest/services/World_Im agery/MapServer?f=jsonpretty=true,raster); It always result in a layer which is invalid. I tried the python equivalent command: layer = QgsRasterLayer(http://server.arcgisonline.com/ArcGIS/rest/services/World_Im agery/MapServer?f=jsonpretty=true,raster); in qgis python console and it works fine. Any help is appreciated. -- View this message in context: http://osgeo-org.1560.x6.nabble.com/Problems-with-developing-custom-c-qgis-a pplication-with-QtCreator-and-MSVC2008-on-Windows-tp5173711.html Sent from the Quantum GIS - Developer mailing list archive at Nabble.com. ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
