On Mon, Mar 11, 2013 at 6:46 PM, Larry Shaffer <[email protected]> wrote: > Hi Radim, > > Could you start an issue ticket for this, possibly including some specs, > like which version of cmake, compiler, etc.? I can not discern what might be > causing the problem for your setup, but working for everyone else (I'm > assuming that), and would like to exchange some patches since I can't > reproduce it here.
We have enough serious issues, is not sufficient to set WITH_STAGED_PLUGINS=OFF by default? Radim > Thanks, > > Larry > > On Fri, Mar 8, 2013 at 7:20 AM, Radim Blazek <[email protected]> wrote: >> >> On Fri, Mar 8, 2013 at 2:28 PM, Larry Shaffer <[email protected]> >> wrote: >> > Hi, >> > >> > On Fri, Mar 8, 2013 at 5:47 AM, Radim Blazek <[email protected]> >> > wrote: >> >> >> >> On Fri, Mar 8, 2013 at 12:17 PM, Larry Shaffer <[email protected]> >> >> wrote: >> >> > Hi Radim, >> >> > >> >> > On Fri, Mar 8, 2013 at 3:31 AM, Radim Blazek <[email protected]> >> >> > wrote: >> >> >> >> >> >> I am getting this compilation error: >> >> >> >> >> >> make[2]: *** No rule to make target `staged_plugins', needed by >> >> >> `python/plugins/CMakeFiles/staged_plugins_on_build'. Stop. >> >> >> make[1]: *** >> >> >> [python/plugins/CMakeFiles/staged_plugins_on_build.dir/all] >> >> >> Error 2 >> >> >> >> >> >> How to solve it ? >> >> > >> >> > The staged_plugins_on_build target is created when >> >> > WITH_STAGED_PLUGINS >> >> > is >> >> > set to TRUE [0]. I believe the dependent target staged_plugins should >> >> > always >> >> > be created if WITH_BINDINGS is TRUE. The new staged plugins setup was >> >> > committed over a month ago, with no appreciable changes since then >> >> > [1]. >> >> >> >> It may be that I did not recompile last month. Does it require any new >> >> dependency? >> >> >> >> > What is the make command you ran? >> >> >> >> make >> >> >> >> > Did you try re-generating the cmake build files? >> >> >> >> Yes. >> >> >> >> > Does this happen on make (all target) for the project with an empty >> >> > build >> >> > dir? >> >> >> >> Yes, but with copy of CMakeCache.txt from the old one. >> > >> > >> > Maybe set WITH_STAGED_PLUGINS to FALSE (it's TRUE by default), possibly >> > skipping the build error, since that problematic target won't be >> > auto-built. >> >> Compiles OK. >> >> > Then, if successful build, try 'make staged_plugins' to stage the >> > plugins to >> > the build directory, if you run QGIS from there. >> >> Works OK, but if I set WITH_STAGED_PLUGINS=ON, make fails again, more >> verbose output: >> >> [ 95%] Built target staged_plugins >> make -f python/plugins/CMakeFiles/staged_plugins_on_build.dir/build.make >> python/plugins/CMakeFiles/staged_plugins_on_build.dir/depend >> make[2]: Entering directory `/home/radim/devel/qgis/build' >> cd /home/radim/devel/qgis/build && /usr/bin/cmake -E cmake_depends >> "Unix Makefiles" /home/radim/devel/qgis >> /home/radim/devel/qgis/python/plugins /home/radim/devel/qgis/build >> /home/radim/devel/qgis/build/python/plugins >> >> /home/radim/devel/qgis/build/python/plugins/CMakeFiles/staged_plugins_on_build.dir/DependInfo.cmake >> --color= >> make[2]: Leaving directory `/home/radim/devel/qgis/build' >> make -f python/plugins/CMakeFiles/staged_plugins_on_build.dir/build.make >> python/plugins/CMakeFiles/staged_plugins_on_build.dir/build >> make[2]: Entering directory `/home/radim/devel/qgis/build' >> make[2]: *** No rule to make target `staged_plugins', needed by >> `python/plugins/CMakeFiles/staged_plugins_on_build'. Stop. >> make[2]: Leaving directory `/home/radim/devel/qgis/build' >> make[1]: *** [python/plugins/CMakeFiles/staged_plugins_on_build.dir/all] >> Error 2 >> make[1]: Leaving directory `/home/radim/devel/qgis/build' >> make: *** [all] Error 2 >> >> Radim >> >> >> >> >> > What, if anything, has changed in your cmake setup between your last >> >> > successful build and this error? >> >> >> >> Nothing changed I think, I did git pull and when make failed I run >> >> ccmake. I saw that some new strange things are missing, so I installed >> >> bzr but I have still: DART_ROOT-NOTFOUND, HGCOMMAND-NOTFOUND, >> >> QSCINTILLA_LIBRARY-NOTFOUND - are those necessary? >> > >> > >> > QSCINTILLA_LIBRARY is the C++ library used by the Qsci Python module, >> > used >> > in the new PyQGIS console. Currently only the Python module is linked to >> > it, >> > i.e. no one has used QScintilla in C++ code. So, while it shouldn't >> > matter >> > for current building if not found, it should have been found by the >> > .cmake >> > script. >> > >> > Not sure about the others. DART is probably for reporting test results >> > to >> > the dashboard at [0]. >> > >> > [0] http://dash.orfeo-toolbox.org/index.php?project=QGIS >> > >> > Regards, >> > >> > Larry >> > >> >> Radim >> >> >> >> > Regards, >> >> > >> >> > Larry >> >> > >> >> > >> >> > [0] >> >> > >> >> > >> >> > https://github.com/qgis/Quantum-GIS/blob/master/python/plugins/CMakeLists.txt >> >> > [1] >> >> > >> >> > >> >> > https://github.com/qgis/Quantum-GIS/commit/7717aeed1ca9f81107b72bac3aa127767d8f5ac0 >> >> > >> >> >> Radim >> >> >> _______________________________________________ >> >> >> Qgis-developer mailing list >> >> >> [email protected] >> >> >> http://lists.osgeo.org/mailman/listinfo/qgis-developer >> >> > >> >> > >> > >> > > > _______________________________________________ Qgis-developer mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/qgis-developer
