Compile GNU screen from source

• $ git clone git://git.savannah.gnu.org/screen.git
• $ cd screen/src
• $ aclocal --force
• $ libtoolize --copy --force
• $ autoconf --force
• $ autoheader --force
• $ automake --add-missing --copy --force-missing
• $ ./configure --prefix=/usr/local/screen-dev --enable-colors256
• $ make && make install

N.B.: Run mktar.pl to make traditional screen-X.X.X.tar.gz

CMake Modules of KDE

svn co svn://anonsvn.kde.org/home/kde/trunk/KDE/kdelibs/cmake/modules

[cmake] INSTALL_RPATH does not work on Mac OS X?

There are a few properties used to specify RPATH rules. INSTALL_RPATH is a semicolon-separated list specifying the rpath to use in installed targets (for platforms that support it). INSTALL_RPATH_USE_LINK_PATH is a boolean that if set to true will append directories in the linker search path and outside the project to the INSTALL_RPATH. SKIP_BUILD_RPATH is a boolean specifying whether to skip automatic generation of an rpath allowing the target to run from the build tree. BUILD_WITH_INSTALL_RPATH is a boolean specifying whether to link the target in the build tree with the INSTALL_RPATH. This takes precedence over SKIP_BUILD_RPATH and avoids the need for relinking before installation. INSTALL_NAME_DIR is a string specify- ing the directory portion of the "install_name" field of shared libraries on Mac OS X to use in the installed targets. When the target is created the values of the variables CMAKE_INSTALL_RPATH, CMAKE_INSTALL_RPATH_USE_LINK_PATH, CMAKE_SKIP_BUILD_RPATH, CMAKE_BUILD_WITH_INSTALL_RPATH, and CMAKE_INSTALL_NAME_DIR are used to initialize these properties.

[cmake] SET(CMAKE_VERBOSE_MAKEFILE OFF)

CMAKE_VERBOSE_MAKEFILE 默认是 OFF 的, 可以在 CMakeLists.txt 中将其设成 ON, 或者 make 的时候加上 VERBOSE=1 选项.

CMake: SET(CMAKE_VERBOSE_MAKEFILE ON)

• SET(CMAKE_VERBOSE_MAKEFILE ON) 只有放在 PROJECT(XXX) 之后才有效果.
• subdir 中的 SET(), INCLUDE_DIRECTORIES() 等命令不会影响到上层目录.
  

KDE switches to CMake

The KDE4 build system is now centered around CMake. If you are a developer, CMake will be much easier to learn, handle and maintain than what you are used to so far. Alexander Neundorf, who took upon himself a big share of the actual work required for the switch, has published Why the KDE project switched to CMake -- and how on the LWN.net development pages. He outlines the considerations that led to choosing CMake over competing tools, shows why CMake is a better fit than the autotools used in KDE 1, 2 & 3, provides a short introduction into CMake file syntax. He even allows some insights into the current KDE4 development state. Hot on the heels of KDE, Scribus is switching as well.

-- KDE.org

SEE ALSO: KDE CMake Intro

GNU Make Debugger

刚在 bashdb 上浏览时, 发现那儿还有个 make debugger, 新奇, 有时间试用一把.