On Tue, Mar 12, 2013 at 10:34:28AM +0100, Radim Blazek wrote: > On Tue, Mar 12, 2013 at 10:18 AM, Sandro Santilli <[email protected]> wrote: > > On Tue, Mar 12, 2013 at 10:05:59AM +0100, Radim Blazek wrote: > >> 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? > > > > I think the default should be that output/bin/qgis works and can load > > all new core plugins, so developers can test and users can use multiple > > versions. That seems to currently mean "staged plugins". > > > > I can't find any issue filed on hub where [Subject contains "staged"] > > > > You mentioned that WITH_STAGED_PLUGINS=OFF works for you, right ? > > Does "make staged-plugins" work after that ? > > Yes, as I already reported. It is > > make staged-plugins-on-build > > causing the problem: > > *** No rule to make target `staged-plugins', needed by > `python/plugins/CMakeFiles/staged-plugins-on-build'. Stop.
Do you have a `python/plugins/CMakeFiles/staged-plugins-on-build.dir' directory ? What version of cmake are you running ? --strk; _______________________________________________ Qgis-developer mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/qgis-developer
