Hi, I've committed an update to python/plugins/CMakeLists.txt [0] that changes how staged plugins are built (resources generated and copied to [build dir]/output/python/plugins). Staged plugins allow plugins to be available when QGIS is run from the build directory and was originally coded by Sandro Santilli.
When staging all plugins, use the following make targets after a regular QGIS build: * staged_plugins - stage plugins (usually after repo pull/build and project make) * staged_plugins_pyc - stage and byte-compile all Python scripts * clean_staged_plugins - removes the plugins directory and all contents When developing on a plugin, use the following make targets: * staged_[plugin_dir_name] - stage specific plugin, regenerating any changed resources * clean_staged_[plugin_dir_name] - removes the plugin directory and its contents CMake options WITH_STAGED_PLUGINS and WITH_PY_COMPILE are still valid and just run 'staged_plugins' or 'staged_plugins_pyc' respectively (if WITH_STAGED_PLUGINS=TRUE) at the end of a regular project build. In the newly available workflow for running QGIS from build directory, leaving WITH_STAGED_PLUGINS=FALSE (should be as default now?), all above targets are still generated, but not built as part of ALL target. This allows a developer to set up their IDE with custom build process steps like so: * make * make staged_plugins (optional) * make install (optional) with 'make staged_plugins' capable of being built anytime after project build, making those project builds as fast as possible, as done here with QtCreator project setup [1]. If you work on core Python plugins, please let me know how the new workflow for making staged plugins works for you. [0] https://github.com/qgis/Quantum-GIS/commit/e33bd25c62d87b55fc121030638b1f178a9aec36 [1] http://drive.dakotacarto.com/qgis/make_staged_plugins.png Regards, Larry
_______________________________________________ Qgis-developer mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/qgis-developer
