I've seen in CMakeLists that the CMAKE_BUILD_TYPE is evaulated to set
QGISDEBUG definition, but there's no entry inside the cmake list of options.
I had to manually add it (and set it to RelWithDebInfo in my case) to
obtain the Debug output enabled message.
Am I doing something wrong?
giovanni
No way, the VS solution doesn't keep the preprocessor directive...
I keep on trying
Inviato da dispositivo mobile
Il giorno 21/apr/2012 18.12, G. Allegri gioha...@gmail.com ha scritto:
I've seen in CMakeLists that the CMAKE_BUILD_TYPE is evaulated to set
QGISDEBUG definition, but there's no
Hmm, so now some tests run crssync. ... during compilation, executables and
libraries are put in the output subfolder of the build folder... but the
relative links in the libraries here are not designed for the folder structure
there (ie @executable_path/../Frameworks/qgis_core.framework/...).
On Apr 21, 2012, at 9:00 AM, William Kyngesburye wrote:
Hmm, so now some tests run crssync. ... during compilation, executables and
libraries are put in the output subfolder of the build folder... but the
relative links in the libraries here are not designed for the folder
structure there
Il 21/04/2012 00:08, Paolo Cavallini ha scritto:
dh_install: python-qgis missing files
(usr/lib/python*/*-packages/pyspatialite/*.py), aborting
make: *** [binary-arch] Error 2
python-pyspatialite is installed from debian unstable, the rest of the
system is debian testing.
all the best
Hi Developers,
I am a developer for OSSIM (Open Source Software Image Map). I am working
on creating Python wrappings for OSSIM and in order to make the
functionalities of OSSIM benefit other open source GIS software users,
particularly the QGIS users, I want to create a downloadable Python
I think the current answer, is that you rely on the user installing
OSSIM and the OSSIM pyhon library (eg. on a linux distro python-ossim,
prebuilt can be shipped with osgeo4w on windows).
That ensure's its on the python path. Then you can write a plugin that
simply imports your lib.
Thanks,
Hi Alex and Peter,
Thanks for your replies.
Sure, I understood the first part of the process regarding the Python path.
As for the second part, will the plugin writing involve all the Qt stuff
too? Since you said it would simply import the Python-wrapped library os
OSSIM, will the plugin need
So you could approach it that way, where every tool you want to expose
has an interface (could be built from templates), look at the QGIS-GRASS
plugin. Or you could approach wrapping it in the new SEXTANTE plugin the
way OTB, SAGA and GRASS are done.
It somewhat depends on what you're trying to
Okay, that clarifies things for now. Thanks for the insight Alex, I will
revert back if I have more doubts.
On Sun, Apr 22, 2012 at 2:19 AM, Alex Mandel tech_...@wildintellect.comwrote:
So you could approach it that way, where every tool you want to expose
has an interface (could be built from
Vipul
As Alex Said, SEXTANTE is the easiest way for you to incorporate OSSIM
into QGIS.
Feel free to ask me for help, I will be pleased to guide you and
explain you how to do it and how to create a SEXTANTE plugin for OSSIM
Regards
El día 21 de abril de 2012 22:55, Vipul Raheja
All-
Dave Burken and Ming Su at GeoEye implemented an OSSIM image provider for
QGIS. The primary motivation was to provide OSSIM users a mature, rich UI to
visualize and analyze raster and vector data. Users would have the option to
use OSSIM instead of GDAL to visualize raster data.
I
12 matches
Mail list logo
