mirror/curl
2
0
Fork 0
mirror of https://github.com/curl/curl.git synced 2024-12-21 06:50:10 +08:00
Code Issues Packages Projects Releases Wiki Activity
9bee39bfed
curl/Makefile.am

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

253 lines
8.0 KiB
Makefile
Raw Normal View History

source header added
2004-01-13 16:57:24 +08:00
#***************************************************************************
# _ _ ____ _
# Project ___| | | | _ \| |
# / __| | | | |_) | |
# | (__| |_| | _ <| |___
# \___|\___/|_| \_\_____|
Initial revision
1999-12-29 22:20:26 +08:00
#
copyright: update all copyright lines and remove year ranges - they are mostly pointless in all major jurisdictions - many big corporations and projects already don't use them - saves us from pointless churn - git keeps history for us - the year range is kept in COPYING checksrc is updated to allow non-year using copyright statements Closes #10205
2023-01-02 20:51:48 +08:00
# Copyright (C) Daniel Stenberg, <daniel@haxx.se>, et al.
source header added
2004-01-13 16:57:24 +08:00
#
# This software is licensed as described in the file COPYING, which
# you should have received as part of this distribution. The terms
curl.se: new home Closes #6172
2020-11-04 21:02:01 +08:00
# are also available at https://curl.se/docs/copyright.html.
source header added
2004-01-13 16:57:24 +08:00
#
# You may opt to use, copy, modify, merge, publish, distribute and/or sell
# copies of the Software, and permit persons to whom the Software is
# furnished to do so, under the terms of the COPYING file.
Initial revision
1999-12-29 22:20:26 +08:00
#
source header added
2004-01-13 16:57:24 +08:00
# This software is distributed on an "AS IS" basis, WITHOUT WARRANTY OF ANY
# KIND, either express or implied.
#
# SPDX-License-Identifier: curl
copyright: make repository REUSE compliant Add licensing and copyright information for all files in this repository. This either happens in the file itself as a comment header or in the file `.reuse/dep5`. This commit also adds a Github workflow to check pull requests and adapts copyright.pl to the changes. Closes #8869
2022-05-17 17:16:50 +08:00
#
source header added
2004-01-13 16:57:24 +08:00
###########################################################################
Initial revision
1999-12-29 22:20:26 +08:00
automake usage and options cleanup
2002-02-25 22:08:18 +08:00
AUTOMAKE_OPTIONS = foreign
Initial revision
1999-12-29 22:20:26 +08:00
Reinstate the 'aclocal -I m4' in buildconf and 'ACLOCAL_AMFLAGS = -I m4' way of including our local m4/reentrant.m4 file. This even takes care of including the file in the distribution tarball.
2008-07-30 11:10:03 +08:00
ACLOCAL_AMFLAGS = -I m4
cmake: add support for building with wolfSSL My working build cmdline: $ cmake -DCMAKE_PREFIX_PATH=$HOME/build-wolfssl -DCMAKE_USE_WOLFSSL=ON . Assisted-by: Brad King Closes #5095
2020-03-13 00:18:40 +08:00
CMAKE_DIST = \
CMake/cmake_uninstall.cmake.in \
CMake/CMakeConfigurableFile.in \
CMake/curl-config.cmake.in \
CMake/CurlSymbolHiding.cmake \
CMake/CurlTests.c \
CMake/FindBearSSL.cmake \
dist: add missing CMake Find modules to the distribution Closes #5836
2020-08-21 01:41:39 +08:00
CMake/FindBrotli.cmake \
cmake: rename Find modules - `FindCARES` -> `FindCares` - `FindLibPSL` -> `FindLibpsl` - `FindLibSSH2` -> `FindLibssh2` - `FindQUICHE` -> `FindQuiche` - `Findrustls` -> `FindRustls` Our convention for naming Find modules (the part after the `Find` prefix, also called as 'package name') is: Always start with uppercase. Follow with lowercase, unless there is a clear preference for a stylized name. E.g. the project itself uses it that way with a matching `<Name>Config.cmake` file, or we use it that way elsewhere, or the name is an acronym. Ref: #14580 Closes #14601
2024-08-20 06:47:55 +08:00
CMake/FindCares.cmake \
cmake: add support for building with wolfSSL My working build cmdline: $ cmake -DCMAKE_PREFIX_PATH=$HOME/build-wolfssl -DCMAKE_USE_WOLFSSL=ON . Assisted-by: Brad King Closes #5095
2020-03-13 00:18:40 +08:00
CMake/FindGSS.cmake \
cmake: migrate dependency detections to Find modules For: libgsasl, libidn2, libssh, libuv. The new Find modules retain using `pkg-config` natively, not as a "hint" for the CMake-native detection. Of the pre-existing Find modules, only FindNettle, and FindGSS (with customized code) work this way. Align detection code for the new modules and add version detection for the CMake-native paths. Also, add CMake-native detection for `libgsasl`. The remaining outlier in `CMakeLists.txt` is GnuTLS, which has a CMake built-in Find module, but which lacks `pkg-config` support, required for vcpkg. It remains unchanged. Another part-outlier is `libssh`, which keeps requiring the trick `find_package(libssh CONFIG QUIET)` for reasons I could not yet figure out. Closes #14555
2024-08-19 20:27:51 +08:00
CMake/FindLibgsasl.cmake \
CMake/FindLibidn2.cmake \
cmake: rename Find modules - `FindCARES` -> `FindCares` - `FindLibPSL` -> `FindLibpsl` - `FindLibSSH2` -> `FindLibssh2` - `FindQUICHE` -> `FindQuiche` - `Findrustls` -> `FindRustls` Our convention for naming Find modules (the part after the `Find` prefix, also called as 'package name') is: Always start with uppercase. Follow with lowercase, unless there is a clear preference for a stylized name. E.g. the project itself uses it that way with a matching `<Name>Config.cmake` file, or we use it that way elsewhere, or the name is an acronym. Ref: #14580 Closes #14601
2024-08-20 06:47:55 +08:00
CMake/FindLibpsl.cmake \
cmake: migrate dependency detections to Find modules For: libgsasl, libidn2, libssh, libuv. The new Find modules retain using `pkg-config` natively, not as a "hint" for the CMake-native detection. Of the pre-existing Find modules, only FindNettle, and FindGSS (with customized code) work this way. Align detection code for the new modules and add version detection for the CMake-native paths. Also, add CMake-native detection for `libgsasl`. The remaining outlier in `CMakeLists.txt` is GnuTLS, which has a CMake built-in Find module, but which lacks `pkg-config` support, required for vcpkg. It remains unchanged. Another part-outlier is `libssh`, which keeps requiring the trick `find_package(libssh CONFIG QUIET)` for reasons I could not yet figure out. Closes #14555
2024-08-19 20:27:51 +08:00
CMake/FindLibssh.cmake \
cmake: rename Find modules - `FindCARES` -> `FindCares` - `FindLibPSL` -> `FindLibpsl` - `FindLibSSH2` -> `FindLibssh2` - `FindQUICHE` -> `FindQuiche` - `Findrustls` -> `FindRustls` Our convention for naming Find modules (the part after the `Find` prefix, also called as 'package name') is: Always start with uppercase. Follow with lowercase, unless there is a clear preference for a stylized name. E.g. the project itself uses it that way with a matching `<Name>Config.cmake` file, or we use it that way elsewhere, or the name is an acronym. Ref: #14580 Closes #14601
2024-08-20 06:47:55 +08:00
CMake/FindLibssh2.cmake \
cmake: migrate dependency detections to Find modules For: libgsasl, libidn2, libssh, libuv. The new Find modules retain using `pkg-config` natively, not as a "hint" for the CMake-native detection. Of the pre-existing Find modules, only FindNettle, and FindGSS (with customized code) work this way. Align detection code for the new modules and add version detection for the CMake-native paths. Also, add CMake-native detection for `libgsasl`. The remaining outlier in `CMakeLists.txt` is GnuTLS, which has a CMake built-in Find module, but which lacks `pkg-config` support, required for vcpkg. It remains unchanged. Another part-outlier is `libssh`, which keeps requiring the trick `find_package(libssh CONFIG QUIET)` for reasons I could not yet figure out. Closes #14555
2024-08-19 20:27:51 +08:00
CMake/FindLibuv.cmake \
cmake: add support for building with wolfSSL My working build cmdline: $ cmake -DCMAKE_PREFIX_PATH=$HOME/build-wolfssl -DCMAKE_USE_WOLFSSL=ON . Assisted-by: Brad King Closes #5095
2020-03-13 00:18:40 +08:00
CMake/FindMbedTLS.cmake \
msh3: add support for QUIC and HTTP/3 using msh3 Considered experimental, as the other HTTP/3 backends. Closes #8517
2022-04-11 00:21:37 +08:00
CMake/FindMSH3.cmake \
cmake: migrate dependency detections to Find modules For: libgsasl, libidn2, libssh, libuv. The new Find modules retain using `pkg-config` natively, not as a "hint" for the CMake-native detection. Of the pre-existing Find modules, only FindNettle, and FindGSS (with customized code) work this way. Align detection code for the new modules and add version detection for the CMake-native paths. Also, add CMake-native detection for `libgsasl`. The remaining outlier in `CMakeLists.txt` is GnuTLS, which has a CMake built-in Find module, but which lacks `pkg-config` support, required for vcpkg. It remains unchanged. Another part-outlier is `libssh`, which keeps requiring the trick `find_package(libssh CONFIG QUIET)` for reasons I could not yet figure out. Closes #14555
2024-08-19 20:27:51 +08:00
CMake/FindMbedTLS.cmake \
cmake: add support for building with wolfSSL My working build cmdline: $ cmake -DCMAKE_PREFIX_PATH=$HOME/build-wolfssl -DCMAKE_USE_WOLFSSL=ON . Assisted-by: Brad King Closes #5095
2020-03-13 00:18:40 +08:00
CMake/FindNGHTTP2.cmake \
CMake: add HTTP/3 support (ngtcp2+nghttp3, quiche) Add three new CMake Find modules (using the curl license, but I grant others the right to apply the CMake BSD license instead). This CMake config is simpler than the autotools one because it assumes ngtcp2 and nghttp3 to be used together. Another difference is that this CMake config checks whether QUIC is actually supported by the TLS library (patched OpenSSL or boringssl) since this can be a common configuration mistake that could result in build errors later. Unlike autotools, CMake does not warn you that the features are experimental. The user is supposed to already know that and read the documentation. It requires a very special build environment anyway. Tested with ngtcp2+OpenSSL+nghttp3 and quiche+boringssl, both built from current git master. Use `LD_DEBUG=files src/curl |& grep need` to figure out which features (libldap-2.4, libssh2) to disable due to conflicts with boringssl. Closes #5359
2020-05-09 05:13:46 +08:00
CMake/FindNGHTTP3.cmake \
CMake/FindNGTCP2.cmake \
dist: add missing `FindNettle.cmake` Follow-up to 669ce42275635dc1f881dab3dfc9a55c9ab49b21 #14285 Reported-by: Christoph Reiter Bug: https://github.com/curl/curl/pull/14285#issuecomment-2259880050 Closes #14320
2024-07-31 16:02:13 +08:00
CMake/FindNettle.cmake \
cmake: rename Find modules - `FindCARES` -> `FindCares` - `FindLibPSL` -> `FindLibpsl` - `FindLibSSH2` -> `FindLibssh2` - `FindQUICHE` -> `FindQuiche` - `Findrustls` -> `FindRustls` Our convention for naming Find modules (the part after the `Find` prefix, also called as 'package name') is: Always start with uppercase. Follow with lowercase, unless there is a clear preference for a stylized name. E.g. the project itself uses it that way with a matching `<Name>Config.cmake` file, or we use it that way elsewhere, or the name is an acronym. Ref: #14580 Closes #14601
2024-08-20 06:47:55 +08:00
CMake/FindQuiche.cmake \
CMake/FindRustls.cmake \
cmake: add wolfSSH support Enable with CMake option `-DCURL_USE_WOLFSSH=ON`. Customize with `-DWOLFSSH_INCLUDE_DIR=<path-to-wolfssh>/include`, `-DWOLFSSH_LIBRARY=<path-to-wolfssh>/lib/libwolfssh.a`. It requires the wolfSSL TLS backend. Closes #14568
2024-08-16 05:38:10 +08:00
CMake/FindWolfSSH.cmake \
cmake: add support for building with wolfSSL My working build cmdline: $ cmake -DCMAKE_PREFIX_PATH=$HOME/build-wolfssl -DCMAKE_USE_WOLFSSL=ON . Assisted-by: Brad King Closes #5095
2020-03-13 00:18:40 +08:00
CMake/FindWolfSSL.cmake \
dist: add missing CMake Find modules to the distribution Closes #5836
2020-08-21 01:41:39 +08:00
CMake/FindZstd.cmake \
cmake: add support for building with wolfSSL My working build cmdline: $ cmake -DCMAKE_PREFIX_PATH=$HOME/build-wolfssl -DCMAKE_USE_WOLFSSL=ON . Assisted-by: Brad King Closes #5095
2020-03-13 00:18:40 +08:00
CMake/Macros.cmake \
CMake/OtherTests.cmake \
cmake: speed up and extend picky clang/gcc options Extend existing picky compiler options with ones missing compared to autotools builds. Also sync options between clang and gcc. Redesign the way we enable these options to avoid the slow option detection almost completely. This reduces the number of detections from 35 to zero for clang and 3 for gcc, even after adding a bunch of new options. clang 3.0 (2011-11-29) and gcc 2.95 (1999-07-31) now required. Also show enabled picky options. Ref: https://github.com/libssh2/libssh2/pull/952 Reviewed-by: Daniel Stenberg Closes #10973
2023-04-17 06:28:25 +08:00
CMake/PickyWarnings.cmake \
cmake: add support for building with wolfSSL My working build cmdline: $ cmake -DCMAKE_PREFIX_PATH=$HOME/build-wolfssl -DCMAKE_USE_WOLFSSL=ON . Assisted-by: Brad King Closes #5095
2020-03-13 00:18:40 +08:00
CMake/Platforms/WindowsCache.cmake \
CMake/Utilities.cmake \
CMakeLists.txt
first take at bundling cmake-related files in the tarball
2009-04-15 06:00:37 +08:00
projects/README: converted to markdown Closes #8652
2022-03-30 20:35:56 +08:00
VC_DIST = projects/README.md \
projects: Update VC version names for VS2017, VS2022 - Rename VC15 -> VC14.10, VC17 -> VC14.30. The projects directory that holds the pre-generated Visual Studio project files uses VC<ver> to indicate the MSVC version. At some point support for Visual Studio 2017 (Visual Studio version 15 which uses MSVC 14.10) was added as VC15. Visual Studio 2022 (Visual Studio version 17 which uses MSVC 14.30) project files were recently added and followed that same format using VC17. There is no such MSVC version (yet) as VC15 or VC17. For VS 2017 for example, the name we use is correct as either VS17, VS2017, VC14.10. I opted for the latter since we use VC for earlier versions (eg VC10, VC12, etc). Ref: https://github.com/curl/curl/pull/8438#issuecomment-1037070192 Closes https://github.com/curl/curl/pull/8447
2022-02-14 05:58:04 +08:00
projects/build-openssl.bat \
projects/build-wolfssl.bat \
projects/checksrc.bat \
projects/generate.bat \
projects/wolfssl_options.h \
dist: add missing files to the tarball
2017-03-31 05:56:55 +08:00
projects/wolfssl_override.props
dist: include the projects/ files in releases ... the recent MSVC project files added by Steve Holme
2014-04-08 16:17:03 +08:00
winbuild: convert the instruction text to README.md Closes #5861
2020-08-26 18:59:05 +08:00
WINBUILD_DIST = winbuild/README.md winbuild/gen_resp_file.bat \
winbuild: MS-DOS batch tidy-ups - prefer `.bat` extension over `.cmd` for MS-DOS batch, which also avoids confusion with OS/400 `.cmd` files. - cleanup `echo` quotes, drop them consistently. - delete empty output line from one of the error branches. - prefer lowercase commands like the rest of MS-DOS batches. - delete a contraction. - drop backticks from error message. - use `nmake.exe` consistently. - use equal/not-equal operator style consistently. - inline a single-line `if` branch. - delete exceptions and rules dealing with Windows `.cmd` extension. Closes #14084
2024-07-02 16:41:35 +08:00
winbuild/MakefileBuild.vc winbuild/Makefile.vc winbuild/makedebug.bat
Windows build: alternative makefile This is a separate makefile for MSVC builds. It is deliberately put in another dir than src/ and lib/ to allow a different build experience than the previous - at least during a period. Eventually we should unify.
2011-01-29 05:19:44 +08:00
plan9: add support for running on Plan 9 Closes #3701
2019-03-26 21:26:05 +08:00
PLAN9_DIST = plan9/include/mkfile \
plan9/include/mkfile \
plan9/mkfile.proto \
plan9/mkfile \
copyright: fix out-of-date copyright ranges and missing headers Reported by the new script 'scripts/copyright.pl'. The script has a regex whitelist for the files that don't need copyright headers. Removed three (mostly usesless) README files from docs/ Closes #5141
2020-03-23 21:44:29 +08:00
plan9/README \
plan9: add support for running on Plan 9 Closes #3701
2019-03-26 21:26:05 +08:00
plan9/lib/mkfile.inc \
plan9/lib/mkfile \
plan9/src/mkfile.inc \
plan9/src/mkfile
dist: drop `.in` files from `EXTRA_DIST` Some of the `.in` files were listed in `EXTRA_DIST`. Delete them. `.in` files (passed to `AC_CONFIG_FILES`) are added automatically to the distro by autotools. Closes #14821
2024-09-07 16:03:25 +08:00
EXTRA_DIST = CHANGES.md COPYING Makefile.dist \
RELEASE-NOTES $(CMAKE_DIST) $(VC_DIST) $(WINBUILD_DIST) \
$(PLAN9_DIST) buildconf.bat Dockerfile
move msvc IDE related files to 'vc' directory tree
2013-02-12 02:11:14 +08:00
Makefile.am: fix the MSVC project generation It made the vcxproj files not get included in dist tarballs. Regression since 74423b5df4c8117891eb89 (8.5.0) Reported-by: iAroc on github Fixes #12564 Closes #12567
2023-12-21 06:10:38 +08:00
CLEANFILES = $(VC14_LIBVCXPROJ) $(VC14_SRCVCXPROJ) \
$(VC14_10_LIBVCXPROJ) $(VC14_10_SRCVCXPROJ) \
$(VC14_20_LIBVCXPROJ) $(VC14_20_SRCVCXPROJ) \
projects: Update VC version names for VS2017, VS2022 - Rename VC15 -> VC14.10, VC17 -> VC14.30. The projects directory that holds the pre-generated Visual Studio project files uses VC<ver> to indicate the MSVC version. At some point support for Visual Studio 2017 (Visual Studio version 15 which uses MSVC 14.10) was added as VC15. Visual Studio 2022 (Visual Studio version 17 which uses MSVC 14.30) project files were recently added and followed that same format using VC17. There is no such MSVC version (yet) as VC15 or VC17. For VS 2017 for example, the name we use is correct as either VS17, VS2017, VC14.10. I opted for the latter since we use VC for earlier versions (eg VC10, VC12, etc). Ref: https://github.com/curl/curl/pull/8438#issuecomment-1037070192 Closes https://github.com/curl/curl/pull/8447
2022-02-14 05:58:04 +08:00
$(VC14_30_LIBVCXPROJ) $(VC14_30_SRCVCXPROJ)
Makefile.am: Added new Visual Studio project file generation for libcurl
2014-05-17 22:43:12 +08:00
build: `buildinfo.txt` improvements - cmake: drop `configure.os`. This also includes OS version, but thus far it's not important enough to include it. - autotools: drop redundant, autotools-only `{target|host}.vendor`. (it's part of the triplet in `{target|host}`.) - swap order to `*.cpu` -> `*.os` to match triplet-order. - cmake: drop redundant `target`. It's manually filled and only in a (so far) few CI jobs. Let's revisit when this becomes useful. - move `buildinfo.txt` to build root. - dist: add `buildinfo.txt` to `DISTCLEANFILES`. - autotools: detect human readable compiler version. - autotools: replace `XXYY` `compiler.version` with "X.Y"-style. (also to match cmake.) - autotools: use distinct `compiler_id` for Apple clang: `APPLECLANG`. To match cmake and also because the the "X.Y"-style version number is the Apple version, while `XXYY` was a value roughly translated to mainline llvm/clang version. - show buildinfo at the end of the configure stage, when run in CI, or when `CURL_BUILDINFO` or `CURL_CI` env is set. Follow-up to 1fdea1684602a1ae2870c67b5f3e8fd34f63da95 #14802 Assisted-by: Dan Fandrich Ref: https://github.com/curl/curl/pull/14802#issuecomment-2334942991 Closes #14822
2024-09-07 08:43:35 +08:00
DISTCLEANFILES = buildinfo.txt
Added curl-config as a script that now gets installed
2001-04-17 20:33:02 +08:00
bin_SCRIPTS = curl-config
docs: ascii version of manpage without nroff Create ASCII version of manpage without nroff - build src/tool_hugegelp.c from the ascii manpage - move the the manpage and the ascii version build to docs/cmdline-opts - remove all use of nroff from the build process - should make the build entirely reproducible (by avoiding nroff) - partly reverts 2620aa9 to build libcurl option man pages one by one in cmake because the appveyor builds got all crazy until I did The ASCII version of the manpage - is built with gen.pl, just like the manpage is - has a right-justified column making the appearance similar to the previous version - uses a 4-space indent per level (instead of the old version's 7) - does not do hyphenation of words (which nroff does) History We first made the curl build use nroff for building the hugehelp file in December 1998, for curl 5.2. Closes #13047
2024-03-05 00:22:17 +08:00
SUBDIRS = lib docs src scripts
Makefile: remove 'scripts' duplicate from DIST_SUBDIRS Also fix the .dist replacing by avoiding all Makefiles because it otherwise also went into the temporary release folder and got confused about the Makefile.dist in there.
2024-08-02 15:49:31 +08:00
DIST_SUBDIRS = $(SUBDIRS) tests packages include docs
Initial revision
1999-12-29 22:20:26 +08:00
Revert "libcurl.pc: make it relocatable" This reverts commit 3862c37b6373a55ca704171d45ba5ee91dec2c9f. That fix should either be done differently or with an option. Reported-by: asavah on github Fixes #6157 Closes #6183
2020-11-08 01:26:38 +08:00
pkgconfigdir = $(libdir)/pkgconfig
Applied Albert Chin's patch that makes the libcurl.pc pkgconfig file get installed on 'make install' time.
2005-11-16 15:20:57 +08:00
pkgconfig_DATA = libcurl.pc
Makefile.am: Added new Visual Studio project file generation for curl tool
2014-05-18 07:05:55 +08:00
# List of files required to generate VC IDE .dsp, .vcproj and .vcxproj files
move msvc IDE related files to 'vc' directory tree
2013-02-12 02:11:14 +08:00
include lib/Makefile.inc
Makefile.am: Added new Visual Studio project file generation for curl tool
2014-05-18 07:05:55 +08:00
include src/Makefile.inc
move msvc IDE related files to 'vc' directory tree
2013-02-12 02:11:14 +08:00
'make distcheck' works now
2001-01-09 01:38:23 +08:00
dist-hook:
added dist-hook that clears the tests/log dir properly as otherwise 'make distcheck' doesn't pass
2003-03-31 19:37:47 +08:00
rm -rf $(top_builddir)/tests/log
dist: fix reproducible build from release tarball Make it possible to rebuild an identical copy from a release tarball. It was previously only possible from a checked out git repository. - add release-tools.sh to dist - keep Makefile.dist around to include it in dist - regenerate tool_huge.c with the new version in dist - fix the dist CI job to not do make clean like before Closes #14336
2024-08-01 19:51:43 +08:00
find $(distdir) -name "*.dist" -a \! -name Makefile.dist -exec rm {} \;
Makefile: remove 'scripts' duplicate from DIST_SUBDIRS Also fix the .dist replacing by avoiding all Makefiles because it otherwise also went into the temporary release folder and got confused about the Makefile.dist in there.
2024-08-02 15:49:31 +08:00
(distit=`find $(srcdir) -name "*.dist" | grep -v Makefile`; \
Made the dist-hook more generic for adding more files named .dist into the dist archive. Preparing for a new maketgz.
2003-10-30 20:48:19 +08:00
for file in $$distit; do \
strip=`echo $$file | sed -e s/^$(srcdir)// -e s/\.dist//`; \
dist: make the hugehelp.c not get regenerated unnecessarily The maketgz script now makes sure the generated hugehelp.c file in the tarball is newer than the generated curl.1 man page, so that it doesn't have to get unnecessarily rebuilt first thing in a typical build. It thus also removes the need for perl to build off a plain release tarball. Fixes #1565
2017-06-14 04:03:37 +08:00
cp -p $$file $(distdir)$$strip; \
Made the dist-hook more generic for adding more files named .dist into the dist archive. Preparing for a new maketgz.
2003-10-30 20:48:19 +08:00
done)
Loic Dachary's updates to get 'make distcheck' work, including running the test suite
2001-01-09 06:18:30 +08:00
docs/libcurl: check that all options with man pages are referenced If a man page exists in the opts/ directory, it must also be referenced either in curl_easy_setopt.3 or curl_multi_setopt.3
2015-03-19 06:21:46 +08:00
check: test examples check-docs
'make distcheck' works now
2001-01-09 01:38:23 +08:00
Add an alert already here if 'make test' is attempted for a cross-compile since there's no use building the whole test suite first and _then_ tell it doesn't work anyway...
2005-03-11 08:44:32 +08:00
if CROSSCOMPILING
test-full: test
build: add pytest targets It enables running pytests in cmake jobs, regardless of underlying build tool choice (= makes it work with ninja.) Also: - drop pytest logic launching `make` and exiting in case of failure. Maybe there is a better way and keep this functionality somehow, bind it to a command-line option? make it fail softly? - GHA/linux: invoke pytest via the build, not directly. - autotools: add missing dummy runtests targets when cross-compiling. Closes #15034
2024-09-24 07:53:27 +08:00
test-nonflaky: test
Add an alert already here if 'make test' is attempted for a cross-compile since there's no use building the whole test suite first and _then_ tell it doesn't work anyway...
2005-03-11 08:44:32 +08:00
test-torture: test
build: add pytest targets It enables running pytests in cmake jobs, regardless of underlying build tool choice (= makes it work with ninja.) Also: - drop pytest logic launching `make` and exiting in case of failure. Maybe there is a better way and keep this functionality somehow, bind it to a command-line option? make it fail softly? - GHA/linux: invoke pytest via the build, not directly. - autotools: add missing dummy runtests targets when cross-compiling. Closes #15034
2024-09-24 07:53:27 +08:00
test-event: test
test-am: test
test-ci: test
pytest: test
pytest-ci: test
Add an alert already here if 'make test' is attempted for a cross-compile since there's no use building the whole test suite first and _then_ tell it doesn't work anyway...
2005-03-11 08:44:32 +08:00
test:
@echo "NOTICE: we can't run the tests when cross-compiling!"
else
the tests dir is added
2000-11-10 22:42:06 +08:00
test:
Only build in lib and src by default, make the others dist-subdirs. Make the test stuff get built when we run 'make test' instead.
2003-05-27 16:51:09 +08:00
@(cd tests; $(MAKE) all quiet-test)
Loic Dachary's makefile/dist/rpm fixes
2001-01-08 18:00:14 +08:00
Added a 'test-full' target to run the tests in verbose mode.
2003-01-21 18:32:40 +08:00
test-full:
Only build in lib and src by default, make the others dist-subdirs. Make the test stuff get built when we run 'make test' instead.
2003-05-27 16:51:09 +08:00
@(cd tests; $(MAKE) all full-test)
Added a 'test-full' target to run the tests in verbose mode.
2003-01-21 18:32:40 +08:00
make: introduce 'test-nonflaky' target Running this in the root build dir will invoke the test suite to only run tests not marked as 'flaky'.
2017-03-22 17:48:20 +08:00
test-nonflaky:
@(cd tests; $(MAKE) all nonflaky-test)
'make test-torture' in the root now runs a full torture test
2004-05-17 18:54:00 +08:00
test-torture:
@(cd tests; $(MAKE) all torture-test)
coverage: run event tests too ... the torture ones are commented out only because they are slooooow.
2017-06-02 15:25:02 +08:00
test-event:
@(cd tests; $(MAKE) all event-test)
test: offer "automake" output and check for perl better runtests.pl -am now uses the "PASS/FAIL: [desc]" output for each executed test. You can run 'make test-am' in the root build directory to invoke that. The reason for this output style is to better allow generic test suite parsers to also grok our test output. The test Makefile now also tests that perl was indeed found and that the PERL variable points to an executable before it tries to run the main test perl script runtests.pl,
2012-11-23 18:56:26 +08:00
test-am:
@(cd tests; $(MAKE) all am-test)
CI/makefiles: introduce dedicated test target Make it easy to use the same set of test flags throughout all current and future CI builds. Reviewed-by: Jay Satiro Follow up to #7690 Closes #7785
2021-09-28 03:17:29 +08:00
test-ci:
@(cd tests; $(MAKE) all ci-test)
build: add pytest targets It enables running pytests in cmake jobs, regardless of underlying build tool choice (= makes it work with ninja.) Also: - drop pytest logic launching `make` and exiting in case of failure. Maybe there is a better way and keep this functionality somehow, bind it to a command-line option? make it fail softly? - GHA/linux: invoke pytest via the build, not directly. - autotools: add missing dummy runtests targets when cross-compiling. Closes #15034
2024-09-24 07:53:27 +08:00
pytest:
@(cd tests; $(MAKE) all default-pytest)
pytest-ci:
@(cd tests; $(MAKE) all ci-pytest)
Add an alert already here if 'make test' is attempted for a cross-compile since there's no use building the whole test suite first and _then_ tell it doesn't work anyway...
2005-03-11 08:44:32 +08:00
endif
Compile most of the example apps in docs/examples when doing a 'make check'.
2007-07-13 04:38:54 +08:00
examples:
Changed the makefile so the doc/examples/ programs are never built in a normal build/install (only with the 'make check' target), so that a build failure in the examples isn't fatal.
2008-03-31 11:01:13 +08:00
@(cd docs/examples; $(MAKE) check)
Compile most of the example apps in docs/examples when doing a 'make check'.
2007-07-13 04:38:54 +08:00
docs/libcurl: check that all options with man pages are referenced If a man page exists in the opts/ directory, it must also be referenced either in curl_easy_setopt.3 or curl_multi_setopt.3
2015-03-19 06:21:46 +08:00
check-docs:
@(cd docs/libcurl; $(MAKE) check)
Loic Dachary's makefile/dist/rpm fixes
2001-01-08 18:00:14 +08:00
# Build source and binary rpms. For rpm-3.0 and above, the ~/.rpmmacros
# must contain the following line:
# %_topdir /home/loic/local/rpm
# and that /home/loic/local/rpm contains the directory SOURCES, BUILD etc.
#
Additional "docs" about 'make rpms' added by Loic
2001-01-09 18:09:13 +08:00
# cd /home/loic/local/rpm ; mkdir -p SOURCES BUILD RPMS/i386 SPECS SRPMS
#
Loic Dachary's makefile/dist/rpm fixes
2001-01-08 18:00:14 +08:00
# If additional configure flags are needed to build the package, add the
# following in ~/.rpmmacros
# %configure CFLAGS="%{optflags}" ./configure %{_target_platform} --prefix=%{_prefix} ${AM_CONFIGFLAGS}
# and run make rpm in the following way:
# AM_CONFIGFLAGS='--with-uri=/home/users/loic/local/RedHat-6.2' make rpm
#
rpms:
$(MAKE) RPMDIST=curl rpm
$(MAKE) RPMDIST=curl-ssl rpm
rpm:
RPM_TOPDIR=`rpm --showrc | $(PERL) -n -e 'print if(s/.*_topdir\s+(.*)/$$1/)'` ; \
adjusted to work with automake 'make dist'
2001-01-08 21:39:21 +08:00
cp $(srcdir)/packages/Linux/RPM/$(RPMDIST).spec $$RPM_TOPDIR/SPECS ; \
Loic Dachary's makefile/dist/rpm fixes
2001-01-08 18:00:14 +08:00
cp $(PACKAGE)-$(VERSION).tar.gz $$RPM_TOPDIR/SOURCES ; \
rpm -ba --clean --rmsource $$RPM_TOPDIR/SPECS/$(RPMDIST).spec ; \
mv $$RPM_TOPDIR/RPMS/i386/$(RPMDIST)-*.rpm . ; \
mv $$RPM_TOPDIR/SRPMS/$(RPMDIST)-*.src.rpm .
Added Solaris 'pkgadd' building support to packages collection and autoconf/automake files
2001-05-30 12:31:32 +08:00
#
"make clean" now cleans out the docs and tests directories, too.
2008-10-02 02:29:13 +08:00
# Build a Solaris pkgadd format file
Added Solaris 'pkgadd' building support to packages collection and autoconf/automake files
2001-05-30 12:31:32 +08:00
# run 'make pkgadd' once you've done './configure' and 'make' to make a Solaris pkgadd format
# file (which ends up back in this directory).
# The pkgadd file is in 'pkgtrans' format, so to install on Solaris, do
# pkgadd -d ./HAXXcurl-*
#
spelling fixes Closes #1356
2017-03-26 23:02:22 +08:00
# gak - libtool requires an absolute directory, hence the pwd below...
Added Solaris 'pkgadd' building support to packages collection and autoconf/automake files
2001-05-30 12:31:32 +08:00
pkgadd:
umask 022 ; \
make: use the variable MAKE for recursive calls Closes #1366
2017-03-29 06:20:32 +08:00
$(MAKE) install DESTDIR=`/bin/pwd`/packages/Solaris/root ; \
fixed the pkgadd target
2002-09-05 16:24:21 +08:00
cat COPYING > $(srcdir)/packages/Solaris/copyright ; \
Added Solaris 'pkgadd' building support to packages collection and autoconf/automake files
2001-05-30 12:31:32 +08:00
cd $(srcdir)/packages/Solaris && $(MAKE) package
Kevin Roth's cygwin fixes
2001-10-22 14:26:30 +08:00
#
tidy-up: OS names Use these words and casing more consistently across text, comments and one curl tool output: AIX, ALPN, ANSI, BSD, Cygwin, Darwin, FreeBSD, GitHub, HP-UX, Linux, macOS, MS-DOS, MSYS, MinGW, NTLM, POSIX, Solaris, UNIX, Unix, Unicode, WINE, WebDAV, Win32, winbind, WinIDN, Windows, Windows CE, Winsock. Mostly OS names and a few more. Also a couple of other minor text fixups. Closes #14360
2024-08-03 07:09:57 +08:00
# Build a Cygwin binary tarball installation file
Kevin Roth's cygwin package fixes
2001-10-29 18:32:39 +08:00
# resulting .tar.bz2 file will end up at packages/Win32/cygwin
Kevin Roth's cygwin fixes
2001-10-22 14:26:30 +08:00
cygwinbin:
Kevin Roth's cygwin package fixes
2001-10-29 18:32:39 +08:00
$(MAKE) -C packages/Win32/cygwin cygwinbin
When I introduced the DIST_SUBDIRS usage, I broken the 'make install' for include files and docs, so now I've added a custom install hook to run make install for docs and install when data is installed at the top-level.
2003-06-27 22:37:38 +08:00
# We extend the standard install with a custom hook:
configure: add --disable-docs flag Building man pages from curldown sources now requires perl. Add a --disable-docs flag to configure to enable building and installing without documentation where perl is not available or man pages are not required. This is selected automatically (with a warning) when perl is not found by configure. Fixes #12832 Closes #12857
2024-02-04 05:05:59 +08:00
if BUILD_DOCS
When I introduced the DIST_SUBDIRS usage, I broken the 'make install' for include files and docs, so now I've added a custom install hook to run make install for docs and install when data is installed at the top-level.
2003-06-27 22:37:38 +08:00
install-data-hook:
Makefile: run the cd commands in a subshell In bmake, if the directory is changed (with cd or anything else), bmake won't return to the "root directory" on the next command (in the same Makefile rule). This commit runs the cd command in a subshell so it would work in bmake. Closes #5073
2020-03-11 07:51:05 +08:00
(cd include && $(MAKE) install)
(cd docs && $(MAKE) install)
(cd docs/libcurl && $(MAKE) install)
configure: add --disable-docs flag Building man pages from curldown sources now requires perl. Add a --disable-docs flag to configure to enable building and installing without documentation where perl is not available or man pages are not required. This is selected automatically (with a warning) when perl is not found by configure. Fixes #12832 Closes #12857
2024-02-04 05:05:59 +08:00
else
install-data-hook:
(cd include && $(MAKE) install)
docs: dist curl*.1 and install without perl Drop docs/mk-ca-bundle.1 from the tarball. It can be generated at will. Closes #12959 Fixes #12921 Reported-by: Michael Forney
2024-02-19 16:32:07 +08:00
(cd docs && $(MAKE) install)
configure: add --disable-docs flag Building man pages from curldown sources now requires perl. Add a --disable-docs flag to configure to enable building and installing without documentation where perl is not available or man pages are not required. This is selected automatically (with a warning) when perl is not found by configure. Fixes #12832 Closes #12857
2024-02-04 05:05:59 +08:00
endif
make an uninstall hook in the same manner we already did an install hook as otherwise will make distcheck fail
2003-08-07 06:15:12 +08:00
# We extend the standard uninstall with a custom hook:
uninstall-hook:
Makefile: run the cd commands in a subshell In bmake, if the directory is changed (with cd or anything else), bmake won't return to the "root directory" on the next command (in the same Makefile rule). This commit runs the cd command in a subshell so it would work in bmake. Closes #5073
2020-03-11 07:51:05 +08:00
(cd include && $(MAKE) uninstall)
(cd docs && $(MAKE) uninstall)
(cd docs/libcurl && $(MAKE) uninstall)
provide the ca-bundle target the same way as the Makefile.dist does it so that it works the same way for configure-based platforms as for non-configure ones
2008-02-08 19:11:59 +08:00
Makefile.am: fix portability issues Commit a04f0b961333e1a19848d073d8c7db9c20b2a371 made me notice that there is a portability issue in curl's top-level Makefile.am. $< can only be used in rules that deal with .SUFFIXES. Its use for general prerequisites is a GNU make extension. $< could be replaced by $?, but I think in an autotools context, something like this is better: Bug: https://curl.se/mail/lib-2022-05/0024.html Closes #8861
2022-05-19 21:45:07 +08:00
ca-bundle: $(srcdir)/scripts/mk-ca-bundle.pl
Makefile.am: Corrected a couple of grammar errors
2014-05-18 07:09:06 +08:00
@echo "generating a fresh ca-bundle.crt"
Makefile.am: fix portability issues Commit a04f0b961333e1a19848d073d8c7db9c20b2a371 made me notice that there is a portability issue in curl's top-level Makefile.am. $< can only be used in rules that deal with .SUFFIXES. Its use for general prerequisites is a GNU make extension. $< could be replaced by $?, but I think in an autotools context, something like this is better: Bug: https://curl.se/mail/lib-2022-05/0024.html Closes #8861
2022-05-19 21:45:07 +08:00
@perl $(srcdir)/scripts/mk-ca-bundle.pl -b -l -u lib/ca-bundle.crt
- Running 'make ca-firefox' in the root build dir will now run the new firefox-db2pem.sh conversion script that converts a local Firefox db of ca certs into PEM format, suitable for use with a OpenSSL or GnuTLS built libcurl.
2008-08-24 06:02:41 +08:00
Makefile.am: fix portability issues Commit a04f0b961333e1a19848d073d8c7db9c20b2a371 made me notice that there is a portability issue in curl's top-level Makefile.am. $< can only be used in rules that deal with .SUFFIXES. Its use for general prerequisites is a GNU make extension. $< could be replaced by $?, but I think in an autotools context, something like this is better: Bug: https://curl.se/mail/lib-2022-05/0024.html Closes #8861
2022-05-19 21:45:07 +08:00
ca-firefox: $(srcdir)/scripts/firefox-db2pem.sh
Makefile.am: Corrected a couple of grammar errors
2014-05-18 07:09:06 +08:00
@echo "generating a fresh ca-bundle.crt"
Makefile.am: fix portability issues Commit a04f0b961333e1a19848d073d8c7db9c20b2a371 made me notice that there is a portability issue in curl's top-level Makefile.am. $< can only be used in rules that deal with .SUFFIXES. Its use for general prerequisites is a GNU make extension. $< could be replaced by $?, but I think in an autotools context, something like this is better: Bug: https://curl.se/mail/lib-2022-05/0024.html Closes #8861
2022-05-19 21:45:07 +08:00
$(srcdir)/scripts/firefox-db2pem.sh lib/ca-bundle.crt
make: add 'checksrc' as target to check code style The make target checksrc now works in the root makefile and in both the src and lib directories. It is also run automatically on "all" if configure --enable-debug was used.
2011-04-27 16:23:27 +08:00
checksrc:
Makefile: run the cd commands in a subshell In bmake, if the directory is changed (with cd or anything else), bmake won't return to the "root directory" on the next command (in the same Makefile rule). This commit runs the cd command in a subshell so it would work in bmake. Closes #5073
2020-03-11 07:51:05 +08:00
(cd lib && $(MAKE) checksrc)
(cd src && $(MAKE) checksrc)
(cd tests && $(MAKE) checksrc)
(cd include/curl && $(MAKE) checksrc)
(cd docs/examples && $(MAKE) checksrc)
packages/OS400: make the source code-style compliant ... and make sure 'make checksrc' in the root dir also verifies the packages/OS400 sources. Closes https://github.com/curl/curl/pull/6085
2020-10-15 16:07:00 +08:00
(cd packages && $(MAKE) checksrc)
move msvc IDE related files to 'vc' directory tree
2013-02-12 02:11:14 +08:00
Makefile: add 'tidy' target that runs clang-tidy Available in the root, src and lib dirs. Closes #3163
2018-10-23 06:33:27 +08:00
tidy:
(cd src && $(MAKE) tidy)
(cd lib && $(MAKE) tidy)
Reference in New Issue Copy Permalink