15 Sep
2016
15 Sep
'16
8:55 a.m.
On Thu, 15 Sep 2016 08:56:06 +0200 (CEST), Ffanci Silvain wrote:
Ok, this is very confusing. Running cmake first could replace pushing
"c".
However, in ccmake the next step seems to push "t" and then to use page
down to search the options. On page 2 there's
"CMAKE_INSTALL_PREFIX /usr/local". Then with "/" it's possible to
search
the variable name, instead of scrolling with the cursor keys. But then
editing it becomes a PITA. I didn't try to read the help and to do it.
Anyway, if running
cmake ./ -DCMAKE_INSTALL_PREFIX=/usr/
and after that
ccmake ./
and pushing "t" and "page down"
CMAKE_INSTALL_PREFIX changed to /usr.
On Thu, 15 Sep 2016 08:45:03 +0100, Will Godfrey wrote:
and after
pushing "c" to change e.g. the "--prefix" directory?
Once you
changed an option and pressed 'c' again to configure it Arguments for and against cmake are rather like the
vi-emacs wars.
Both are a PITA for users who just want to edit an option.
[rocketmouse@archlinux tmp]$ grep -i editor ~/.bashrc
export EDITOR="nano"
;)
Believing the Arch PKGBUIL just changing the prefix doesn't do the job.
-DCMAKE_INSTALL_DATAROOTDIR
-DCMAKE_INSTALL_LIBDIR
seems to be required, too, but the INSTALL file does not clarify how to
at least chose the prefix. IMO you should explain this.
What happens when I try to build from git?
[rocketmouse@archlinux tmp]$ git clone git://git.code.sf.net/p/yoshimi/code
Ok, something like ./autogen.sh seems not to be needed, cmake does the
job. This might be an advantage, but apart from this, from a user point
of view, cmake makes things more complicated.
Regards,
Ralf