On Monday 16 November 2015 10:37:32 Chris Cannam wrote:
>
> On Mon, Nov 16, 2015, at 09:50 AM, David Faure wrote:
> > I suggest to retry from scratch the release-build (with no args) and
> > debug-build, both uninstalled and installed.
>
> What's the proper way to restore an existing checkout to "from scratch"
> condition, as far as cmake is concerned?
>
> I just tried the default build and then a debug build, but using "cmake
> ." in the root directory (in contravention of the instructions that are
> now in the README) instead of a build dir. I did that because it's what
> I used to do when we used cmake before, and it's etched in the muscle
> memory. It actually worked fine -- first time around I got a static
> binary (at least in terms of RG-specific dependencies) and the second
> time I got something with a separate RG shared lib. The static binary
> worked correctly when copied to a different directory as well, no
> problems with absent resources. Only problem is that the outputs are
> created in src/ rather than the root dir, which could be confusing,
> especially if an old rosegarden binary is left over in the root dir as
> well.
>
> I then decided to try a build dir, so I created a directory called
> build, cd'd to it, ran "cmake .." in that directory... and it didn't do
> anything -- no makefile created in the build dir. Presumably it found
> all its stuff already built in the directory above and just left it as
> it was. Hence my question at the top.
Removing Makefile, CMakeCache.txt and the directory "CMakeFiles"
should be enough, unless you actually started to build as well (`make`).
If you did, I'd recommend a good cleanup :)
`svn-clean` comes to mind, it's a script installed by the kdesdk-scripts
package ("kdesdk4-scripts" on OpenSuSE).
Warning, this assumes there are no uncommitted files in your svn checkout
that you'd like to keep around!
--
David Faure, fa...@kde.org, http://www.davidfaure.fr
Working on KDE Frameworks 5
------------------------------------------------------------------------------
Presto, an open source distributed SQL query engine for big data, initially
developed by Facebook, enables you to easily query your data on Hadoop in a
more interactive manner. Teradata is also now providing full enterprise
support for Presto. Download a free open source copy now.
http://pubads.g.doubleclick.net/gampad/clk?id=250295911&iu=/4140
_______________________________________________
Rosegarden-devel mailing list
Rosegarden-devel@lists.sourceforge.net - use the link below to unsubscribe
https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
