kpriv/pkgsrc
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
pkgsrc/devel/cmake/Makefile

25 lines
593 B
Makefile
Raw Normal View History

Remove USE_GNU_TOOLS and replace with the correct USE_TOOLS definitions: USE_GNU_TOOLS -> USE_TOOLS awk -> gawk m4 -> gm4 make -> gmake sed -> gsed yacc -> bison
2005-05-22 22:07:36 +02:00
# $NetBSD: Makefile,v 1.17 2005/05/22 20:07:49 jlam Exp $
import cmake-1.6.6 CMake is an extensible, open-source system that manages the build process in an operating system and compiler independent manner. Unlike many cross-platform systems, CMake is designed to be used in conjunction with the native build environment. Simple configuration files placed in each source directory (called CMakeLists.txt files) are used to generate standard build files (e.g., makefiles on Unix and projects/workspaces in Windows MSVC) which are used in the usual way. CMake can compile source code, create libraries, generate wrappers, and build executables in arbitrary combinations. CMake supports in-place and out-of-place builds, and can therefore support multiple builds from a single source tree. CMake also supports static and dynamic library builds. Another nice feature of CMake is that it generates a cache file that is designed to be used with a graphical editor. For example, when CMake runs, it locates include files, libraries, and executable, and may encounter optional build directives. This information is gathered into the cache, which may be changed by the user prior to the generation of the native build files.
2003-05-07 13:55:03 +02:00
Changes 2.0.5: * Bug fixes
2005-01-06 14:07:59 +01:00
DISTNAME= cmake-2.0.5
import cmake-1.6.6 CMake is an extensible, open-source system that manages the build process in an operating system and compiler independent manner. Unlike many cross-platform systems, CMake is designed to be used in conjunction with the native build environment. Simple configuration files placed in each source directory (called CMakeLists.txt files) are used to generate standard build files (e.g., makefiles on Unix and projects/workspaces in Windows MSVC) which are used in the usual way. CMake can compile source code, create libraries, generate wrappers, and build executables in arbitrary combinations. CMake supports in-place and out-of-place builds, and can therefore support multiple builds from a single source tree. CMake also supports static and dynamic library builds. Another nice feature of CMake is that it generates a cache file that is designed to be used with a graphical editor. For example, when CMake runs, it locates include files, libraries, and executable, and may encounter optional build directives. This information is gathered into the cache, which may be changed by the user prior to the generation of the native build files.
2003-05-07 13:55:03 +02:00
CATEGORIES= devel
update to 2.0.2 2.0 was a major feature release - too many to list here, see the included ChangeLog.* files for details. 2.0.x fixed bugs.
2004-08-02 15:08:09 +02:00
MASTER_SITES= http://www.cmake.org/files/v2.0/
import cmake-1.6.6 CMake is an extensible, open-source system that manages the build process in an operating system and compiler independent manner. Unlike many cross-platform systems, CMake is designed to be used in conjunction with the native build environment. Simple configuration files placed in each source directory (called CMakeLists.txt files) are used to generate standard build files (e.g., makefiles on Unix and projects/workspaces in Windows MSVC) which are used in the usual way. CMake can compile source code, create libraries, generate wrappers, and build executables in arbitrary combinations. CMake supports in-place and out-of-place builds, and can therefore support multiple builds from a single source tree. CMake also supports static and dynamic library builds. Another nice feature of CMake is that it generates a cache file that is designed to be used with a graphical editor. For example, when CMake runs, it locates include files, libraries, and executable, and may encounter optional build directives. This information is gathered into the cache, which may be changed by the user prior to the generation of the native build files.
2003-05-07 13:55:03 +02:00
s/netbsd.org/NetBSD.org/
2003-07-17 23:21:03 +02:00
MAINTAINER= tech-pkg@NetBSD.org
Add trailing / on HOMEPAGEs
2003-12-30 18:21:54 +01:00
HOMEPAGE= http://www.cmake.org/
update to 2.0.2 2.0 was a major feature release - too many to list here, see the included ChangeLog.* files for details. 2.0.x fixed bugs.
2004-08-02 15:08:09 +02:00
COMMENT= Cross platform make
import cmake-1.6.6 CMake is an extensible, open-source system that manages the build process in an operating system and compiler independent manner. Unlike many cross-platform systems, CMake is designed to be used in conjunction with the native build environment. Simple configuration files placed in each source directory (called CMakeLists.txt files) are used to generate standard build files (e.g., makefiles on Unix and projects/workspaces in Windows MSVC) which are used in the usual way. CMake can compile source code, create libraries, generate wrappers, and build executables in arbitrary combinations. CMake supports in-place and out-of-place builds, and can therefore support multiple builds from a single source tree. CMake also supports static and dynamic library builds. Another nice feature of CMake is that it generates a cache file that is designed to be used with a graphical editor. For example, when CMake runs, it locates include files, libraries, and executable, and may encounter optional build directives. This information is gathered into the cache, which may be changed by the user prior to the generation of the native build files.
2003-05-07 13:55:03 +02:00
Remove USE_GNU_TOOLS and replace with the correct USE_TOOLS definitions: USE_GNU_TOOLS -> USE_TOOLS awk -> gawk m4 -> gm4 make -> gmake sed -> gsed yacc -> bison
2005-05-22 22:07:36 +02:00
USE_TOOLS+= gmake
Changes 2.0.5: * Bug fixes
2005-01-06 14:07:59 +01:00
USE_LANGUAGES= c c++
USE_NCURSES= yes
GNU_CONFIGURE= yes
BUILD_TARGET= default_target
import cmake-1.6.6 CMake is an extensible, open-source system that manages the build process in an operating system and compiler independent manner. Unlike many cross-platform systems, CMake is designed to be used in conjunction with the native build environment. Simple configuration files placed in each source directory (called CMakeLists.txt files) are used to generate standard build files (e.g., makefiles on Unix and projects/workspaces in Windows MSVC) which are used in the usual way. CMake can compile source code, create libraries, generate wrappers, and build executables in arbitrary combinations. CMake supports in-place and out-of-place builds, and can therefore support multiple builds from a single source tree. CMake also supports static and dynamic library builds. Another nice feature of CMake is that it generates a cache file that is designed to be used with a graphical editor. For example, when CMake runs, it locates include files, libraries, and executable, and may encounter optional build directives. This information is gathered into the cache, which may be changed by the user prior to the generation of the native build files.
2003-05-07 13:55:03 +02:00
post-patch:
bl3ify, and set USE_LANGUAGES appropriately
2004-02-10 03:44:24 +01:00
for file in ${WRKSRC}/Modules/FindCurses.cmake; do \
${MV} -f $$file $$file.bak; \
${SED} "s|@prefix@|${PREFIX}|g" $$file.bak > $$file; \
done
import cmake-1.6.6 CMake is an extensible, open-source system that manages the build process in an operating system and compiler independent manner. Unlike many cross-platform systems, CMake is designed to be used in conjunction with the native build environment. Simple configuration files placed in each source directory (called CMakeLists.txt files) are used to generate standard build files (e.g., makefiles on Unix and projects/workspaces in Windows MSVC) which are used in the usual way. CMake can compile source code, create libraries, generate wrappers, and build executables in arbitrary combinations. CMake supports in-place and out-of-place builds, and can therefore support multiple builds from a single source tree. CMake also supports static and dynamic library builds. Another nice feature of CMake is that it generates a cache file that is designed to be used with a graphical editor. For example, when CMake runs, it locates include files, libraries, and executable, and may encounter optional build directives. This information is gathered into the cache, which may be changed by the user prior to the generation of the native build files.
2003-05-07 13:55:03 +02:00
bl3ify, and set USE_LANGUAGES appropriately
2004-02-10 03:44:24 +01:00
.include "../../devel/ncurses/buildlink3.mk"
import cmake-1.6.6 CMake is an extensible, open-source system that manages the build process in an operating system and compiler independent manner. Unlike many cross-platform systems, CMake is designed to be used in conjunction with the native build environment. Simple configuration files placed in each source directory (called CMakeLists.txt files) are used to generate standard build files (e.g., makefiles on Unix and projects/workspaces in Windows MSVC) which are used in the usual way. CMake can compile source code, create libraries, generate wrappers, and build executables in arbitrary combinations. CMake supports in-place and out-of-place builds, and can therefore support multiple builds from a single source tree. CMake also supports static and dynamic library builds. Another nice feature of CMake is that it generates a cache file that is designed to be used with a graphical editor. For example, when CMake runs, it locates include files, libraries, and executable, and may encounter optional build directives. This information is gathered into the cache, which may be changed by the user prior to the generation of the native build files.
2003-05-07 13:55:03 +02:00
.include "../../mk/bsd.pkg.mk"
Reference in a new issue Copy permalink