kpriv/freebsd-ports
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
freebsd-ports/Mk/Uses/cargo.mk

406 lines
15 KiB
Makefile
Raw Normal View History

Add USES=cargo to make creating ports of Rust applications easier Approved by: mat (mentor) Reviewed by: dumbbell, mat Differential Revision: https://reviews.freebsd.org/D11162
2017-06-21 18:22:32 +02:00
# This file contains logic to ease porting of Rust packages or
# binaries using the `cargo` command.
#
# Feature: cargo
# Usage: USES=cargo
# Valid ARGS: none
#
Mk/Uses/cargo.mk: Push lib dependencies back down into ports Some crates are optional via Cargo features or are only used during tests, however the framework has no way to discriminate between test or run dependencies using just CARGO_CRATES leading to more run dependencies than necessary for some packages. With more ported Rust applications it's time to let individual ports make that decision now. The environmental setup to use dependencies from ports instead of bundled ones and implied build dependencies (cmake, gmake, pkgconf) are left in place for now. Assign cargo.mk to rust@ while here.
2019-04-17 09:33:34 +02:00
# MAINTAINER: rust@FreeBSD.org
Add USES=cargo to make creating ports of Rust applications easier Approved by: mat (mentor) Reviewed by: dumbbell, mat Differential Revision: https://reviews.freebsd.org/D11162
2017-06-21 18:22:32 +02:00
.if !defined(_INCLUDE_USES_CARGO_MK)
_INCLUDE_USES_CARGO_MK= yes
framework: cleanup conditional-indentations in Mk/ Run Tools/scripts/indent_make_if.pl on all of Mk. These white space changes contribute greatly to the readability of those files. As we have a version control system, finding out the reasons for the changes prior to these white space changes is still easily possible Differential Revision: https://reviews.freebsd.org/D35024 Reviewed by: portmgr (rene, bapt)
2022-04-24 12:00:20 +02:00
. if !empty(cargo_ARGS)
Add USES=cargo to make creating ports of Rust applications easier Approved by: mat (mentor) Reviewed by: dumbbell, mat Differential Revision: https://reviews.freebsd.org/D11162
2017-06-21 18:22:32 +02:00
IGNORE+= USES=cargo takes no arguments
framework: cleanup conditional-indentations in Mk/ Run Tools/scripts/indent_make_if.pl on all of Mk. These white space changes contribute greatly to the readability of those files. As we have a version control system, finding out the reasons for the changes prior to these white space changes is still easily possible Differential Revision: https://reviews.freebsd.org/D35024 Reviewed by: portmgr (rene, bapt)
2022-04-24 12:00:20 +02:00
. endif
Add USES=cargo to make creating ports of Rust applications easier Approved by: mat (mentor) Reviewed by: dumbbell, mat Differential Revision: https://reviews.freebsd.org/D11162
2017-06-21 18:22:32 +02:00
Uses/cargo: Try to load Makefile.crates Some ports stash the `make cargo-crates` output there which might as well be supported by USES=cargo.
2021-09-07 09:26:05 +02:00
.sinclude "${MASTERDIR}/Makefile.crates"
Add USES=cargo to make creating ports of Rust applications easier Approved by: mat (mentor) Reviewed by: dumbbell, mat Differential Revision: https://reviews.freebsd.org/D11162
2017-06-21 18:22:32 +02:00
# List of static dependencies. The format is cratename-version.
Speed up USES=cargo ports ops MASTER_SITES aliases processing in the framework is very inefficient and the CRATESIO indirection is not worth it. Normally ports only have a handful of sites at most, but USES=cargo currently adds one site for each crate by necessity. The inefficiency suddenly matters a lot. By consuming MASTER_SITE_CRATESIO directly we can sidestep this issue without losing anything. Before: $ time make -C www/zola -V MASTER_SITES >/dev/null 4.21 real 4.14 user 0.03 sys After: $ time make -C www/zola -V MASTER_SITES >/dev/null 0.60 real 0.58 user 0.02 sys
2021-04-14 13:53:37 +02:00
# CARGO_CRATES will be downloaded from MASTER_SITE_CRATESIO.
Add USES=cargo to make creating ports of Rust applications easier Approved by: mat (mentor) Reviewed by: dumbbell, mat Differential Revision: https://reviews.freebsd.org/D11162
2017-06-21 18:22:32 +02:00
CARGO_CRATES?=
# List of features to build (space separated list).
Mk/Uses/cargo.mk: Allow disabling default features via CARGO_FEATURES CARGO_FEATURES is overloaded to accept --no-default-features as a special token which will set CARGO_{BUILD,INSTALL,TEST}_ARGS appropriately. This is done in preference over introducing yet another knob.
2020-03-04 16:00:17 +01:00
# Use special token --no-default-features to disable default
# features by passing it to cargo build/install/test.
Add USES=cargo to make creating ports of Rust applications easier Approved by: mat (mentor) Reviewed by: dumbbell, mat Differential Revision: https://reviews.freebsd.org/D11162
2017-06-21 18:22:32 +02:00
CARGO_FEATURES?=
# Name of the local directory for vendoring crates.
CARGO_VENDOR_DIR?= ${WRKSRC}/cargo-crates
# Default path for cargo manifest.
CARGO_CARGOTOML?= ${WRKSRC}/Cargo.toml
CARGO_CARGOLOCK?= ${WRKSRC}/Cargo.lock
# Save crates inside ${DISTDIR}/rust/crates by default.
CARGO_DIST_SUBDIR?= rust/crates
# Generate list of DISTFILES.
Mk/Uses/cargo.mk: Use canonical crate file extension going forward Crates should have the file extension .crate not .tar.gz. Cargo saves them with that extension and it is also what their original name was according to file(1): $ file rust/crates/* rust/crates/better-panic-0.2.0.tar.gz:gzip compressed data, was "better-panic-0.2.0.crate" rust/crates/binary-space-partition-0.1.2.tar.gz:gzip compressed data, was "binary-space-partition-0.1.2.crate" ... The only reason we used .tar.gz is that it was that way in OpenBSD's devel/cargo/cargo.port.mk module. At the moment they are all .tar.gz but they might have a different format in the future. Doing a delayed rollout of this over a change-everything-once approach to - not immeditately invalidate all uncommitted port changes or external ports - not make sweeping changes twice in main and 2021Q2 at the cost of having a transition period where mirrors might have to carry both the .tar.gz and .crate tarballs (all crates combined are ~600 MiB). Reviewed by: jbeich MFH: 2021Q2 (to ease future cherry picks) Differential Revision: https://reviews.freebsd.org/D29760
2021-04-17 07:27:24 +02:00
# Prefer canonical file extension .crate going forward
framework: cleanup conditional-indentations in Mk/ Run Tools/scripts/indent_make_if.pl on all of Mk. These white space changes contribute greatly to the readability of those files. As we have a version control system, finding out the reasons for the changes prior to these white space changes is still easily possible Differential Revision: https://reviews.freebsd.org/D35024 Reviewed by: portmgr (rene, bapt)
2022-04-24 12:00:20 +02:00
. if make(makesum)
Mk/Uses/cargo.mk: Use canonical crate file extension going forward Crates should have the file extension .crate not .tar.gz. Cargo saves them with that extension and it is also what their original name was according to file(1): $ file rust/crates/* rust/crates/better-panic-0.2.0.tar.gz:gzip compressed data, was "better-panic-0.2.0.crate" rust/crates/binary-space-partition-0.1.2.tar.gz:gzip compressed data, was "binary-space-partition-0.1.2.crate" ... The only reason we used .tar.gz is that it was that way in OpenBSD's devel/cargo/cargo.port.mk module. At the moment they are all .tar.gz but they might have a different format in the future. Doing a delayed rollout of this over a change-everything-once approach to - not immeditately invalidate all uncommitted port changes or external ports - not make sweeping changes twice in main and 2021Q2 at the cost of having a transition period where mirrors might have to carry both the .tar.gz and .crate tarballs (all crates combined are ~600 MiB). Reviewed by: jbeich MFH: 2021Q2 (to ease future cherry picks) Differential Revision: https://reviews.freebsd.org/D29760
2021-04-17 07:27:24 +02:00
CARGO_CRATE_EXT= .crate
framework: cleanup conditional-indentations in Mk/ Run Tools/scripts/indent_make_if.pl on all of Mk. These white space changes contribute greatly to the readability of those files. As we have a version control system, finding out the reasons for the changes prior to these white space changes is still easily possible Differential Revision: https://reviews.freebsd.org/D35024 Reviewed by: portmgr (rene, bapt)
2022-04-24 12:00:20 +02:00
. else
Mk/Uses/cargo.mk: Use canonical crate file extension going forward Crates should have the file extension .crate not .tar.gz. Cargo saves them with that extension and it is also what their original name was according to file(1): $ file rust/crates/* rust/crates/better-panic-0.2.0.tar.gz:gzip compressed data, was "better-panic-0.2.0.crate" rust/crates/binary-space-partition-0.1.2.tar.gz:gzip compressed data, was "binary-space-partition-0.1.2.crate" ... The only reason we used .tar.gz is that it was that way in OpenBSD's devel/cargo/cargo.port.mk module. At the moment they are all .tar.gz but they might have a different format in the future. Doing a delayed rollout of this over a change-everything-once approach to - not immeditately invalidate all uncommitted port changes or external ports - not make sweeping changes twice in main and 2021Q2 at the cost of having a transition period where mirrors might have to carry both the .tar.gz and .crate tarballs (all crates combined are ~600 MiB). Reviewed by: jbeich MFH: 2021Q2 (to ease future cherry picks) Differential Revision: https://reviews.freebsd.org/D29760
2021-04-17 07:27:24 +02:00
# If there is a rust/crates/*.tar.gz in distinfo keep using the old
# extension. We need to delay eval until the last moment for
# DISTINFO_FILE. We cache the command output to avoid multiple
# slow grep runs for every CARGO_CRATE_EXT access.
CARGO_CRATE_EXT= ${defined(_CARGO_CRATE_EXT_CACHE):?${_CARGO_CRATE_EXT_CACHE}:${:!if ${GREP} -q '\(${CARGO_DIST_SUBDIR}/.*\.tar\.gz\)' "${DISTINFO_FILE}" 2>/dev/null; then ${ECHO_CMD} .tar.gz; else ${ECHO_CMD} .crate; fi!:_=_CARGO_CRATE_EXT_CACHE}}
framework: cleanup conditional-indentations in Mk/ Run Tools/scripts/indent_make_if.pl on all of Mk. These white space changes contribute greatly to the readability of those files. As we have a version control system, finding out the reasons for the changes prior to these white space changes is still easily possible Differential Revision: https://reviews.freebsd.org/D35024 Reviewed by: portmgr (rene, bapt)
2022-04-24 12:00:20 +02:00
. endif
Uses/cargo: Rework git source support based on patch-in-config sections Git sources from `Cargo.lock` are added to `CARGO_CRATES` through the normal mechanism of `make cargo-crates` by the porter. They are used to populate `MASTER_SITES`, `DISTFILES` with static git-archive(1) tarballs a la `USE_GITHUB`, `USE_GITLAB`. In the configure phase we generate `[patch]` sections in the config file which will cause `cargo update` to auto-update `Cargo.lock` to point to the appropriate extraction directories. Normally `cargo update` would connect to the network to update all Git sources but since rust-1.55.0 our cargo has been patched to skip this when `CARGO_FREEBSD_PORTS_SKIP_GIT_UPDATE` is set in the environment. This replaces the old `CARGO_USE_GITHUB`, `CARGO_USE_GITLAB` hacks where this was done by editing all `Cargo.toml` with sed(1) calls. Additionally, we try to automatically infer the individiual crate sub-directories inside the Git sources based on `package.name` in `Cargo.toml` to remove the need for `CARGO_GIT_SUBDIR`. USES=cargo also now sets `WRKSRC_crate_$name` for each crate to point to the crate extraction directories. PR: 256581 Reviewed by: jbeich
2021-09-07 16:08:46 +02:00
_CARGO_CRATES:= ${CARGO_CRATES:N*@git+*}
_CARGO_GIT_SOURCES:= ${CARGO_CRATES:M*@git+*}
Mk/Uses/cargo.mk: Refactor MASTER_SITES and DISTFILES construction (D30099) Split CARGO_CRATES into (index, crate, name, version) 4-tuples and use them to construct MASTER_SITES and DISTFILES. We can also match crate name and versions more directly below. As a bonus this is slightly faster and will flag a malformed CARGO_CRATES earlier with a "wrong number of words" error. Runtime of the following command was noticeably faster $ <rust-ports /usr/bin/time xe -F make -C {} -V DISTFILES -V MASTER_SITES >/dev/null Before: 56.99 real 50.05 user 6.44 sys Now: 38.89 real 31.63 user 6.86 sys PR: 255608 Exp-run by: antoine
2021-04-29 11:48:10 +02:00
# enumerate crates for unqiue and sane distfile group names
Uses/cargo: Rework git source support based on patch-in-config sections Git sources from `Cargo.lock` are added to `CARGO_CRATES` through the normal mechanism of `make cargo-crates` by the porter. They are used to populate `MASTER_SITES`, `DISTFILES` with static git-archive(1) tarballs a la `USE_GITHUB`, `USE_GITLAB`. In the configure phase we generate `[patch]` sections in the config file which will cause `cargo update` to auto-update `Cargo.lock` to point to the appropriate extraction directories. Normally `cargo update` would connect to the network to update all Git sources but since rust-1.55.0 our cargo has been patched to skip this when `CARGO_FREEBSD_PORTS_SKIP_GIT_UPDATE` is set in the environment. This replaces the old `CARGO_USE_GITHUB`, `CARGO_USE_GITLAB` hacks where this was done by editing all `Cargo.toml` with sed(1) calls. Additionally, we try to automatically infer the individiual crate sub-directories inside the Git sources based on `package.name` in `Cargo.toml` to remove the need for `CARGO_GIT_SUBDIR`. USES=cargo also now sets `WRKSRC_crate_$name` for each crate to point to the crate extraction directories. PR: 256581 Reviewed by: jbeich
2021-09-07 16:08:46 +02:00
_CARGO_CRATES:= ${empty(_CARGO_CRATES):?:${_CARGO_CRATES:range:@i@$i ${_CARGO_CRATES:[$i]}@}}
Mk/Uses/cargo.mk: Refactor MASTER_SITES and DISTFILES construction (D30099) Split CARGO_CRATES into (index, crate, name, version) 4-tuples and use them to construct MASTER_SITES and DISTFILES. We can also match crate name and versions more directly below. As a bonus this is slightly faster and will flag a malformed CARGO_CRATES earlier with a "wrong number of words" error. Runtime of the following command was noticeably faster $ <rust-ports /usr/bin/time xe -F make -C {} -V DISTFILES -V MASTER_SITES >/dev/null Before: 56.99 real 50.05 user 6.44 sys Now: 38.89 real 31.63 user 6.86 sys PR: 255608 Exp-run by: antoine
2021-04-29 11:48:10 +02:00
# split up crates into (index, crate, name, version) 4-tuples
Uses/cargo: Rework git source support based on patch-in-config sections Git sources from `Cargo.lock` are added to `CARGO_CRATES` through the normal mechanism of `make cargo-crates` by the porter. They are used to populate `MASTER_SITES`, `DISTFILES` with static git-archive(1) tarballs a la `USE_GITHUB`, `USE_GITLAB`. In the configure phase we generate `[patch]` sections in the config file which will cause `cargo update` to auto-update `Cargo.lock` to point to the appropriate extraction directories. Normally `cargo update` would connect to the network to update all Git sources but since rust-1.55.0 our cargo has been patched to skip this when `CARGO_FREEBSD_PORTS_SKIP_GIT_UPDATE` is set in the environment. This replaces the old `CARGO_USE_GITHUB`, `CARGO_USE_GITLAB` hacks where this was done by editing all `Cargo.toml` with sed(1) calls. Additionally, we try to automatically infer the individiual crate sub-directories inside the Git sources based on `package.name` in `Cargo.toml` to remove the need for `CARGO_GIT_SUBDIR`. USES=cargo also now sets `WRKSRC_crate_$name` for each crate to point to the crate extraction directories. PR: 256581 Reviewed by: jbeich
2021-09-07 16:08:46 +02:00
_CARGO_CRATES:= ${_CARGO_CRATES:C/^([-_a-zA-Z0-9]+)-([0-9].*)/\0 \1 \2/}
framework: cleanup conditional-indentations in Mk/ Run Tools/scripts/indent_make_if.pl on all of Mk. These white space changes contribute greatly to the readability of those files. As we have a version control system, finding out the reasons for the changes prior to these white space changes is still easily possible Differential Revision: https://reviews.freebsd.org/D35024 Reviewed by: portmgr (rene, bapt)
2022-04-24 12:00:20 +02:00
. for _index _crate _name _version in ${_CARGO_CRATES}
Speed up USES=cargo ports ops MASTER_SITES aliases processing in the framework is very inefficient and the CRATESIO indirection is not worth it. Normally ports only have a handful of sites at most, but USES=cargo currently adds one site for each crate by necessity. The inefficiency suddenly matters a lot. By consuming MASTER_SITE_CRATESIO directly we can sidestep this issue without losing anything. Before: $ time make -C www/zola -V MASTER_SITES >/dev/null 4.21 real 4.14 user 0.03 sys After: $ time make -C www/zola -V MASTER_SITES >/dev/null 0.60 real 0.58 user 0.02 sys
2021-04-14 13:53:37 +02:00
# Resolving CRATESIO alias is very inefficient with many MASTER_SITES, consume MASTER_SITE_CRATESIO directly
Mk/Uses/cargo.mk: Refactor MASTER_SITES and DISTFILES construction (D30099) Split CARGO_CRATES into (index, crate, name, version) 4-tuples and use them to construct MASTER_SITES and DISTFILES. We can also match crate name and versions more directly below. As a bonus this is slightly faster and will flag a malformed CARGO_CRATES earlier with a "wrong number of words" error. Runtime of the following command was noticeably faster $ <rust-ports /usr/bin/time xe -F make -C {} -V DISTFILES -V MASTER_SITES >/dev/null Before: 56.99 real 50.05 user 6.44 sys Now: 38.89 real 31.63 user 6.86 sys PR: 255608 Exp-run by: antoine
2021-04-29 11:48:10 +02:00
MASTER_SITES+= ${MASTER_SITE_CRATESIO:S,%SUBDIR%,${_name}/${_version},:S,$,:_cargo_${_index},}
DISTFILES+= ${CARGO_DIST_SUBDIR}/${_crate}${CARGO_CRATE_EXT}:_cargo_${_index}
Uses/cargo: Rework git source support based on patch-in-config sections Git sources from `Cargo.lock` are added to `CARGO_CRATES` through the normal mechanism of `make cargo-crates` by the porter. They are used to populate `MASTER_SITES`, `DISTFILES` with static git-archive(1) tarballs a la `USE_GITHUB`, `USE_GITLAB`. In the configure phase we generate `[patch]` sections in the config file which will cause `cargo update` to auto-update `Cargo.lock` to point to the appropriate extraction directories. Normally `cargo update` would connect to the network to update all Git sources but since rust-1.55.0 our cargo has been patched to skip this when `CARGO_FREEBSD_PORTS_SKIP_GIT_UPDATE` is set in the environment. This replaces the old `CARGO_USE_GITHUB`, `CARGO_USE_GITLAB` hacks where this was done by editing all `Cargo.toml` with sed(1) calls. Additionally, we try to automatically infer the individiual crate sub-directories inside the Git sources based on `package.name` in `Cargo.toml` to remove the need for `CARGO_GIT_SUBDIR`. USES=cargo also now sets `WRKSRC_crate_$name` for each crate to point to the crate extraction directories. PR: 256581 Reviewed by: jbeich
2021-09-07 16:08:46 +02:00
# Provide pointer to the crate's extraction dir
WRKSRC_crate_${_name}= ${CARGO_VENDOR_DIR}/${_crate}
# ... also with version suffix in case of multiple versions of the
# same crate
WRKSRC_crate_${_crate}= ${CARGO_VENDOR_DIR}/${_crate}
framework: cleanup conditional-indentations in Mk/ Run Tools/scripts/indent_make_if.pl on all of Mk. These white space changes contribute greatly to the readability of those files. As we have a version control system, finding out the reasons for the changes prior to these white space changes is still easily possible Differential Revision: https://reviews.freebsd.org/D35024 Reviewed by: portmgr (rene, bapt)
2022-04-24 12:00:20 +02:00
. endfor
Add USES=cargo to make creating ports of Rust applications easier Approved by: mat (mentor) Reviewed by: dumbbell, mat Differential Revision: https://reviews.freebsd.org/D11162
2017-06-21 18:22:32 +02:00
Uses/cargo: Rework git source support based on patch-in-config sections Git sources from `Cargo.lock` are added to `CARGO_CRATES` through the normal mechanism of `make cargo-crates` by the porter. They are used to populate `MASTER_SITES`, `DISTFILES` with static git-archive(1) tarballs a la `USE_GITHUB`, `USE_GITLAB`. In the configure phase we generate `[patch]` sections in the config file which will cause `cargo update` to auto-update `Cargo.lock` to point to the appropriate extraction directories. Normally `cargo update` would connect to the network to update all Git sources but since rust-1.55.0 our cargo has been patched to skip this when `CARGO_FREEBSD_PORTS_SKIP_GIT_UPDATE` is set in the environment. This replaces the old `CARGO_USE_GITHUB`, `CARGO_USE_GITLAB` hacks where this was done by editing all `Cargo.toml` with sed(1) calls. Additionally, we try to automatically infer the individiual crate sub-directories inside the Git sources based on `package.name` in `Cargo.toml` to remove the need for `CARGO_GIT_SUBDIR`. USES=cargo also now sets `WRKSRC_crate_$name` for each crate to point to the crate extraction directories. PR: 256581 Reviewed by: jbeich
2021-09-07 16:08:46 +02:00
_CARGO_AWK= ${AWK} -vCP="${CP}" -vFIND="${FIND}" -vGREP="${GREP}" \
-vCARGO_VENDOR_DIR="${CARGO_VENDOR_DIR}" \
-vGIT_SOURCES="${_CARGO_GIT_SOURCES}" \
-vWRKDIR="${WRKDIR}" -vWRKSRC="${WRKSRC}" \
-f${SCRIPTSDIR}/split-url.awk \
-f${SCRIPTSDIR}/cargo-crates-git-common.awk -f
framework: cleanup conditional-indentations in Mk/ Run Tools/scripts/indent_make_if.pl on all of Mk. These white space changes contribute greatly to the readability of those files. As we have a version control system, finding out the reasons for the changes prior to these white space changes is still easily possible Differential Revision: https://reviews.freebsd.org/D35024 Reviewed by: portmgr (rene, bapt)
2022-04-24 12:00:20 +02:00
. if !empty(_CARGO_GIT_SOURCES)
. for _index _site _filename _wrksrc _crates in ${:!${_CARGO_AWK} ${SCRIPTSDIR}/cargo-crates-git-fetch.awk /dev/null!}
Uses/cargo: Rework git source support based on patch-in-config sections Git sources from `Cargo.lock` are added to `CARGO_CRATES` through the normal mechanism of `make cargo-crates` by the porter. They are used to populate `MASTER_SITES`, `DISTFILES` with static git-archive(1) tarballs a la `USE_GITHUB`, `USE_GITLAB`. In the configure phase we generate `[patch]` sections in the config file which will cause `cargo update` to auto-update `Cargo.lock` to point to the appropriate extraction directories. Normally `cargo update` would connect to the network to update all Git sources but since rust-1.55.0 our cargo has been patched to skip this when `CARGO_FREEBSD_PORTS_SKIP_GIT_UPDATE` is set in the environment. This replaces the old `CARGO_USE_GITHUB`, `CARGO_USE_GITLAB` hacks where this was done by editing all `Cargo.toml` with sed(1) calls. Additionally, we try to automatically infer the individiual crate sub-directories inside the Git sources based on `package.name` in `Cargo.toml` to remove the need for `CARGO_GIT_SUBDIR`. USES=cargo also now sets `WRKSRC_crate_$name` for each crate to point to the crate extraction directories. PR: 256581 Reviewed by: jbeich
2021-09-07 16:08:46 +02:00
MASTER_SITES+= ${_site}:_cargo_git${_index}
DISTFILES+= ${_filename}:_cargo_git${_index}
framework: cleanup conditional-indentations in Mk/ Run Tools/scripts/indent_make_if.pl on all of Mk. These white space changes contribute greatly to the readability of those files. As we have a version control system, finding out the reasons for the changes prior to these white space changes is still easily possible Differential Revision: https://reviews.freebsd.org/D35024 Reviewed by: portmgr (rene, bapt)
2022-04-24 12:00:20 +02:00
. for _crate in ${_crates:S/,/ /g}
Uses/cargo: Rework git source support based on patch-in-config sections Git sources from `Cargo.lock` are added to `CARGO_CRATES` through the normal mechanism of `make cargo-crates` by the porter. They are used to populate `MASTER_SITES`, `DISTFILES` with static git-archive(1) tarballs a la `USE_GITHUB`, `USE_GITLAB`. In the configure phase we generate `[patch]` sections in the config file which will cause `cargo update` to auto-update `Cargo.lock` to point to the appropriate extraction directories. Normally `cargo update` would connect to the network to update all Git sources but since rust-1.55.0 our cargo has been patched to skip this when `CARGO_FREEBSD_PORTS_SKIP_GIT_UPDATE` is set in the environment. This replaces the old `CARGO_USE_GITHUB`, `CARGO_USE_GITLAB` hacks where this was done by editing all `Cargo.toml` with sed(1) calls. Additionally, we try to automatically infer the individiual crate sub-directories inside the Git sources based on `package.name` in `Cargo.toml` to remove the need for `CARGO_GIT_SUBDIR`. USES=cargo also now sets `WRKSRC_crate_$name` for each crate to point to the crate extraction directories. PR: 256581 Reviewed by: jbeich
2021-09-07 16:08:46 +02:00
# Make sure the build dependencies checks below can work for git sourced crates too
_CARGO_CRATES+= @git ${_crate} ${_crate} @git
# Provide pointer to the crate's extraction dir
#
# This might not point to the actual crate's sources since a
# single git source can contain multiple crates. We cannot collect
# subdir information until after the full extraction is done and we
# cannot set make variables at that point. This is better than
# nothing.
WRKSRC_crate_${_crate}= ${WRKDIR}/${_wrksrc}
framework: cleanup conditional-indentations in Mk/ Run Tools/scripts/indent_make_if.pl on all of Mk. These white space changes contribute greatly to the readability of those files. As we have a version control system, finding out the reasons for the changes prior to these white space changes is still easily possible Differential Revision: https://reviews.freebsd.org/D35024 Reviewed by: portmgr (rene, bapt)
2022-04-24 12:00:20 +02:00
. endfor
Uses/cargo: Rework git source support based on patch-in-config sections Git sources from `Cargo.lock` are added to `CARGO_CRATES` through the normal mechanism of `make cargo-crates` by the porter. They are used to populate `MASTER_SITES`, `DISTFILES` with static git-archive(1) tarballs a la `USE_GITHUB`, `USE_GITLAB`. In the configure phase we generate `[patch]` sections in the config file which will cause `cargo update` to auto-update `Cargo.lock` to point to the appropriate extraction directories. Normally `cargo update` would connect to the network to update all Git sources but since rust-1.55.0 our cargo has been patched to skip this when `CARGO_FREEBSD_PORTS_SKIP_GIT_UPDATE` is set in the environment. This replaces the old `CARGO_USE_GITHUB`, `CARGO_USE_GITLAB` hacks where this was done by editing all `Cargo.toml` with sed(1) calls. Additionally, we try to automatically infer the individiual crate sub-directories inside the Git sources based on `package.name` in `Cargo.toml` to remove the need for `CARGO_GIT_SUBDIR`. USES=cargo also now sets `WRKSRC_crate_$name` for each crate to point to the crate extraction directories. PR: 256581 Reviewed by: jbeich
2021-09-07 16:08:46 +02:00
. endfor
framework: cleanup conditional-indentations in Mk/ Run Tools/scripts/indent_make_if.pl on all of Mk. These white space changes contribute greatly to the readability of those files. As we have a version control system, finding out the reasons for the changes prior to these white space changes is still easily possible Differential Revision: https://reviews.freebsd.org/D35024 Reviewed by: portmgr (rene, bapt)
2022-04-24 12:00:20 +02:00
. endif
Uses/cargo: Rework git source support based on patch-in-config sections Git sources from `Cargo.lock` are added to `CARGO_CRATES` through the normal mechanism of `make cargo-crates` by the porter. They are used to populate `MASTER_SITES`, `DISTFILES` with static git-archive(1) tarballs a la `USE_GITHUB`, `USE_GITLAB`. In the configure phase we generate `[patch]` sections in the config file which will cause `cargo update` to auto-update `Cargo.lock` to point to the appropriate extraction directories. Normally `cargo update` would connect to the network to update all Git sources but since rust-1.55.0 our cargo has been patched to skip this when `CARGO_FREEBSD_PORTS_SKIP_GIT_UPDATE` is set in the environment. This replaces the old `CARGO_USE_GITHUB`, `CARGO_USE_GITLAB` hacks where this was done by editing all `Cargo.toml` with sed(1) calls. Additionally, we try to automatically infer the individiual crate sub-directories inside the Git sources based on `package.name` in `Cargo.toml` to remove the need for `CARGO_GIT_SUBDIR`. USES=cargo also now sets `WRKSRC_crate_$name` for each crate to point to the crate extraction directories. PR: 256581 Reviewed by: jbeich
2021-09-07 16:08:46 +02:00
Add USES=cargo to make creating ports of Rust applications easier Approved by: mat (mentor) Reviewed by: dumbbell, mat Differential Revision: https://reviews.freebsd.org/D11162
2017-06-21 18:22:32 +02:00
# Build dependencies.
CARGO_BUILDDEP?= yes
framework: cleanup conditional-indentations in Mk/ Run Tools/scripts/indent_make_if.pl on all of Mk. These white space changes contribute greatly to the readability of those files. As we have a version control system, finding out the reasons for the changes prior to these white space changes is still easily possible Differential Revision: https://reviews.freebsd.org/D35024 Reviewed by: portmgr (rene, bapt)
2022-04-24 12:00:20 +02:00
. if ${CARGO_BUILDDEP:tl} == "yes"
lang/rust: Update to 1.62.0 Announce: https://blog.rust-lang.org/2022/06/30/Rust-1.62.0.html ChangeLog: https://github.com/rust-lang/rust/blob/master/RELEASES.md#version-1610-2022-06-30 Tested by: mikael, pkubaj Differential Revision: https://reviews.freebsd.org/D35675
2022-06-29 14:21:31 +02:00
BUILD_DEPENDS+= ${RUST_DEFAULT}>=1.62.0:lang/${RUST_DEFAULT}
framework: cleanup conditional-indentations in Mk/ Run Tools/scripts/indent_make_if.pl on all of Mk. These white space changes contribute greatly to the readability of those files. As we have a version control system, finding out the reasons for the changes prior to these white space changes is still easily possible Differential Revision: https://reviews.freebsd.org/D35024 Reviewed by: portmgr (rene, bapt)
2022-04-24 12:00:20 +02:00
. endif
Add USES=cargo to make creating ports of Rust applications easier Approved by: mat (mentor) Reviewed by: dumbbell, mat Differential Revision: https://reviews.freebsd.org/D11162
2017-06-21 18:22:32 +02:00
Uses/cargo: Make it easier to build ports with out-of-tree toolchain - CARGO_CARGO_BIN -> CARGO - Add RUSTC and RUSTDOC for overriding rustc and rustdoc
2021-11-07 15:08:57 +01:00
# Location of toolchain (default to lang/rust's toolchain)
CARGO?= ${LOCALBASE}/bin/cargo
RUSTC?= ${LOCALBASE}/bin/rustc
RUSTDOC?= ${LOCALBASE}/bin/rustdoc
Add USES=cargo to make creating ports of Rust applications easier Approved by: mat (mentor) Reviewed by: dumbbell, mat Differential Revision: https://reviews.freebsd.org/D11162
2017-06-21 18:22:32 +02:00
# Location of the cargo output directory.
CARGO_TARGET_DIR?= ${WRKDIR}/target
Uses/cargo: respect CC when --target is passed devel/cargo-c always passes --target when building consumers. Some other USES=cargo consumers may also pass --target. Differential Revision: https://reviews.freebsd.org/D31568
2021-09-07 11:14:10 +02:00
# Default target platform (affects some RUSTFLAGS if passed)
Uses/cargo: Mirror _RUST_ARCH_* mapping from lang/rust
2021-11-07 15:15:07 +01:00
CARGO_BUILD_TARGET?= ${_CARGO_RUST_ARCH_${ARCH}:U${ARCH}}-unknown-${OPSYS:tl}
_CARGO_RUST_ARCH_amd64= x86_64
_CARGO_RUST_ARCH_i386= i686
lang/rust: Add riscv64 (riscv64gc-unknown-freebsd) support A kernel with COMPAT_FREEBSD11 is required for now like on all other FreeBSD archs. FreeBSD11 never had riscv64 support, so GENERIC does not have it and a kernel rebuild is required. The same issue existed on powerpc64le. The riscv64gc-unknown-freebsd target was upstreamed and will be part of Rust 1.59.0 (2021-02-24). Reviewed by: jrtc27, pkubaj Differential Revision: https://reviews.freebsd.org/D32881
2021-11-05 11:25:23 +01:00
_CARGO_RUST_ARCH_riscv64= riscv64gc
Uses/cargo: respect CC when --target is passed devel/cargo-c always passes --target when building consumers. Some other USES=cargo consumers may also pass --target. Differential Revision: https://reviews.freebsd.org/D31568
2021-09-07 11:14:10 +02:00
Add USES=cargo to make creating ports of Rust applications easier Approved by: mat (mentor) Reviewed by: dumbbell, mat Differential Revision: https://reviews.freebsd.org/D11162
2017-06-21 18:22:32 +02:00
# Environment for cargo
# - CARGO_HOME: local cache of the registry index
# - CARGO_BUILD_JOBS: configure number of jobs to run
# - CARGO_TARGET_DIR: location of where to place all generated artifacts
lang/rust: Update to 1.41.0 - Force rebuild all consumers to catch regressions early - Switch to cross-compiled (from amd64) bootstraps for all architectures generated with the incoming lang/rust-bootstrap - Update cargo-c to 0.5.2 to unbreak librav1e build - Make use of regular MAKE_ENV/TEST_ENV in lang/rust - Turn on RUST_BACKTRACE in lang/rust and USES=cargo to hopefully produce more useful failure logs when something panics during builds Changes: https://blog.rust-lang.org/2020/01/30/Rust-1.41.0.html Tested by: mikael, tobik With hat: rust Differential Revision: https://reviews.freebsd.org/D23385
2020-01-30 21:00:06 +01:00
# - RUST_BACKTRACE: produce backtraces when something in the build panics
Add USES=cargo to make creating ports of Rust applications easier Approved by: mat (mentor) Reviewed by: dumbbell, mat Differential Revision: https://reviews.freebsd.org/D11162
2017-06-21 18:22:32 +02:00
# - RUSTC: path of rustc binary (default to lang/rust)
# - RUSTDOC: path of rustdoc binary (default to lang/rust)
# - RUSTFLAGS: custom flags to pass to all compiler invocations that Cargo performs
CARGO_ENV+= \
CARGO_HOME=${WRKDIR}/cargo-home \
CARGO_BUILD_JOBS=${MAKE_JOBS_NUMBER} \
Uses/cargo: respect CC when --target is passed devel/cargo-c always passes --target when building consumers. Some other USES=cargo consumers may also pass --target. Differential Revision: https://reviews.freebsd.org/D31568
2021-09-07 11:14:10 +02:00
CARGO_BUILD_TARGET=${CARGO_BUILD_TARGET} \
Add USES=cargo to make creating ports of Rust applications easier Approved by: mat (mentor) Reviewed by: dumbbell, mat Differential Revision: https://reviews.freebsd.org/D11162
2017-06-21 18:22:32 +02:00
CARGO_TARGET_DIR=${CARGO_TARGET_DIR} \
Uses/cargo: respect CC when --target is passed devel/cargo-c always passes --target when building consumers. Some other USES=cargo consumers may also pass --target. Differential Revision: https://reviews.freebsd.org/D31568
2021-09-07 11:14:10 +02:00
CARGO_TARGET_${CARGO_BUILD_TARGET:S/-/_/g:tu}_LINKER="${CC}" \
Uses/cargo: Make it easier to build ports with out-of-tree toolchain - CARGO_CARGO_BIN -> CARGO - Add RUSTC and RUSTDOC for overriding rustc and rustdoc
2021-11-07 15:08:57 +01:00
RUSTC=${RUSTC} \
RUSTDOC=${RUSTDOC} \
Uses/cargo: respect CC when --target is passed devel/cargo-c always passes --target when building consumers. Some other USES=cargo consumers may also pass --target. Differential Revision: https://reviews.freebsd.org/D31568
2021-09-07 11:14:10 +02:00
RUSTFLAGS="${RUSTFLAGS} ${LDFLAGS:C/.+/-C link-arg=&/}"
Add USES=cargo to make creating ports of Rust applications easier Approved by: mat (mentor) Reviewed by: dumbbell, mat Differential Revision: https://reviews.freebsd.org/D11162
2017-06-21 18:22:32 +02:00
framework: cleanup conditional-indentations in Mk/ Run Tools/scripts/indent_make_if.pl on all of Mk. These white space changes contribute greatly to the readability of those files. As we have a version control system, finding out the reasons for the changes prior to these white space changes is still easily possible Differential Revision: https://reviews.freebsd.org/D35024 Reviewed by: portmgr (rene, bapt)
2022-04-24 12:00:20 +02:00
. if ${ARCH} != powerpc
Mk/Uses/cargo.mk: disable RUST_BACKTRACE on powerpc following cargo segfaults on 13.1
2022-03-29 20:24:27 +02:00
CARGO_ENV+= RUST_BACKTRACE=1
framework: cleanup conditional-indentations in Mk/ Run Tools/scripts/indent_make_if.pl on all of Mk. These white space changes contribute greatly to the readability of those files. As we have a version control system, finding out the reasons for the changes prior to these white space changes is still easily possible Differential Revision: https://reviews.freebsd.org/D35024 Reviewed by: portmgr (rene, bapt)
2022-04-24 12:00:20 +02:00
. endif
Mk/Uses/cargo.mk: disable RUST_BACKTRACE on powerpc following cargo segfaults on 13.1
2022-03-29 20:24:27 +02:00
Mk/Uses/cargo.mk: Respect CPUTYPE C and C++ code can be built targeting newer CPUs if user defined CPUTYPE in make.conf. Let's opt-in for Rust as well. PR: 223939 Submitted by: jbeich
2017-11-29 12:06:11 +01:00
# Adjust -C target-cpu if -march/-mcpu is set by bsd.cpu.mk
framework: cleanup conditional-indentations in Mk/ Run Tools/scripts/indent_make_if.pl on all of Mk. These white space changes contribute greatly to the readability of those files. As we have a version control system, finding out the reasons for the changes prior to these white space changes is still easily possible Differential Revision: https://reviews.freebsd.org/D35024 Reviewed by: portmgr (rene, bapt)
2022-04-24 12:00:20 +02:00
. if ${ARCH} == amd64 || ${ARCH} == i386
Mk/Uses/cargo.mk: Respect CPUTYPE C and C++ code can be built targeting newer CPUs if user defined CPUTYPE in make.conf. Let's opt-in for Rust as well. PR: 223939 Submitted by: jbeich
2017-11-29 12:06:11 +01:00
RUSTFLAGS+= ${CFLAGS:M-march=*:S/-march=/-C target-cpu=/}
framework: cleanup conditional-indentations in Mk/ Run Tools/scripts/indent_make_if.pl on all of Mk. These white space changes contribute greatly to the readability of those files. As we have a version control system, finding out the reasons for the changes prior to these white space changes is still easily possible Differential Revision: https://reviews.freebsd.org/D35024 Reviewed by: portmgr (rene, bapt)
2022-04-24 12:00:20 +02:00
. elif ${ARCH:Mpowerpc*}
Use correct target-cpu for power* CPU's Using CPUTYPE?=power9 causes warnings and emits unoptimized code. Rust supports pwr* instead of power*, e.g.: pwr3 pwr4 pwr5 pwr5x pwr6 pwr6x pwr7 pwr8 pwr9
2020-09-19 15:01:35 +02:00
RUSTFLAGS+= ${CFLAGS:M-mcpu=*:S/-mcpu=/-C target-cpu=/:S/power/pwr/}
framework: cleanup conditional-indentations in Mk/ Run Tools/scripts/indent_make_if.pl on all of Mk. These white space changes contribute greatly to the readability of those files. As we have a version control system, finding out the reasons for the changes prior to these white space changes is still easily possible Differential Revision: https://reviews.freebsd.org/D35024 Reviewed by: portmgr (rene, bapt)
2022-04-24 12:00:20 +02:00
. else
Mk/Uses/cargo.mk: Respect CPUTYPE C and C++ code can be built targeting newer CPUs if user defined CPUTYPE in make.conf. Let's opt-in for Rust as well. PR: 223939 Submitted by: jbeich
2017-11-29 12:06:11 +01:00
RUSTFLAGS+= ${CFLAGS:M-mcpu=*:S/-mcpu=/-C target-cpu=/}
framework: cleanup conditional-indentations in Mk/ Run Tools/scripts/indent_make_if.pl on all of Mk. These white space changes contribute greatly to the readability of those files. As we have a version control system, finding out the reasons for the changes prior to these white space changes is still easily possible Differential Revision: https://reviews.freebsd.org/D35024 Reviewed by: portmgr (rene, bapt)
2022-04-24 12:00:20 +02:00
. endif
Mk/Uses/cargo.mk: Respect CPUTYPE C and C++ code can be built targeting newer CPUs if user defined CPUTYPE in make.conf. Let's opt-in for Rust as well. PR: 223939 Submitted by: jbeich
2017-11-29 12:06:11 +01:00
framework: cleanup conditional-indentations in Mk/ Run Tools/scripts/indent_make_if.pl on all of Mk. These white space changes contribute greatly to the readability of those files. As we have a version control system, finding out the reasons for the changes prior to these white space changes is still easily possible Differential Revision: https://reviews.freebsd.org/D35024 Reviewed by: portmgr (rene, bapt)
2022-04-24 12:00:20 +02:00
. if defined(PPC_ABI) && ${PPC_ABI} == ELFv1
Mk/Uses/cargo.mk: Require ports gcc on powerpc64 same as lang/rust PR: 235063
2019-03-02 01:35:33 +01:00
USE_GCC?= yes
lang/rust: Update to 1.52.1 - Add 32-bit powerpc support from bdragon@ - Unbreak build with LibreSSL 3.3.x [1] - Add an update script Changes: https://blog.rust-lang.org/2021/05/06/Rust-1.52.0.html Changes: https://blog.rust-lang.org/2021/05/10/Rust-1.52.1.html PR: 255608, 255652 [1] Reviewed by: mikael, pkubaj Exp-run by: antoine Differential Revision: https://reviews.freebsd.org/D30099
2021-05-04 08:05:04 +02:00
STRIP_CMD= ${LOCALBASE}/bin/strip # unsupported e_type with base strip
framework: cleanup conditional-indentations in Mk/ Run Tools/scripts/indent_make_if.pl on all of Mk. These white space changes contribute greatly to the readability of those files. As we have a version control system, finding out the reasons for the changes prior to these white space changes is still easily possible Differential Revision: https://reviews.freebsd.org/D35024 Reviewed by: portmgr (rene, bapt)
2022-04-24 12:00:20 +02:00
. endif
Mk/Uses/cargo.mk: Require ports gcc on powerpc64 same as lang/rust PR: 235063
2019-03-02 01:35:33 +01:00
Add USES=cargo to make creating ports of Rust applications easier Approved by: mat (mentor) Reviewed by: dumbbell, mat Differential Revision: https://reviews.freebsd.org/D11162
2017-06-21 18:22:32 +02:00
# Helper to shorten cargo calls.
Uses/cargo: Make it easier to build ports with out-of-tree toolchain - CARGO_CARGO_BIN -> CARGO - Add RUSTC and RUSTDOC for overriding rustc and rustdoc
2021-11-07 15:08:57 +01:00
_CARGO_RUN= ${SETENV} ${MAKE_ENV} ${CARGO_ENV} ${CARGO}
Uses/cargo: Rework git source support based on patch-in-config sections Git sources from `Cargo.lock` are added to `CARGO_CRATES` through the normal mechanism of `make cargo-crates` by the porter. They are used to populate `MASTER_SITES`, `DISTFILES` with static git-archive(1) tarballs a la `USE_GITHUB`, `USE_GITLAB`. In the configure phase we generate `[patch]` sections in the config file which will cause `cargo update` to auto-update `Cargo.lock` to point to the appropriate extraction directories. Normally `cargo update` would connect to the network to update all Git sources but since rust-1.55.0 our cargo has been patched to skip this when `CARGO_FREEBSD_PORTS_SKIP_GIT_UPDATE` is set in the environment. This replaces the old `CARGO_USE_GITHUB`, `CARGO_USE_GITLAB` hacks where this was done by editing all `Cargo.toml` with sed(1) calls. Additionally, we try to automatically infer the individiual crate sub-directories inside the Git sources based on `package.name` in `Cargo.toml` to remove the need for `CARGO_GIT_SUBDIR`. USES=cargo also now sets `WRKSRC_crate_$name` for each crate to point to the crate extraction directories. PR: 256581 Reviewed by: jbeich
2021-09-07 16:08:46 +02:00
CARGO_CARGO_RUN= cd ${WRKSRC}; ${SETENV} CARGO_FREEBSD_PORTS_SKIP_GIT_UPDATE=1 ${_CARGO_RUN}
Add USES=cargo to make creating ports of Rust applications easier Approved by: mat (mentor) Reviewed by: dumbbell, mat Differential Revision: https://reviews.freebsd.org/D11162
2017-06-21 18:22:32 +02:00
# User arguments for cargo targets.
CARGO_BUILD_ARGS?=
CARGO_INSTALL_ARGS?=
Mk/Uses/cargo.mk: Add CARGO_INSTALL_PATH knob It can be used to overwrite the --path argument when calling `cargo install` to point cargo to different local crates to install. This might be necessary when ${WRKSRC}/Cargo.toml is only a virtual manifest.
2019-06-10 12:56:04 +02:00
CARGO_INSTALL_PATH?= .
Add USES=cargo to make creating ports of Rust applications easier Approved by: mat (mentor) Reviewed by: dumbbell, mat Differential Revision: https://reviews.freebsd.org/D11162
2017-06-21 18:22:32 +02:00
CARGO_TEST_ARGS?=
CARGO_UPDATE_ARGS?=
# Use module targets ?
CARGO_BUILD?= yes
CARGO_CONFIGURE?= yes
CARGO_INSTALL?= yes
CARGO_TEST?= yes
lang/rust*: Mk/Uses/cargo.mk: Move TMPDIR to WRKDIR rustc stashes intermediary files in TMPDIR (default /tmp) which might cause issues for users that for some reason space limit their /tmp. WRKDIR should have plenty of space. Other ports that use rustc might be affected too, but set it only in USES=cargo and lang/rust* ports for now. PR: 258126 With hat: rust
2021-09-06 19:16:38 +02:00
# rustc stashes intermediary files in TMPDIR (default /tmp) which
# might cause issues for users that for some reason space limit
# their /tmp. WRKDIR should have plenty of space.
# Allow users and ports to still overwrite it.
framework: cleanup conditional-indentations in Mk/ Run Tools/scripts/indent_make_if.pl on all of Mk. These white space changes contribute greatly to the readability of those files. As we have a version control system, finding out the reasons for the changes prior to these white space changes is still easily possible Differential Revision: https://reviews.freebsd.org/D35024 Reviewed by: portmgr (rene, bapt)
2022-04-24 12:00:20 +02:00
. if ${TMPDIR:U/tmp} == /tmp
lang/rust*: Mk/Uses/cargo.mk: Move TMPDIR to WRKDIR rustc stashes intermediary files in TMPDIR (default /tmp) which might cause issues for users that for some reason space limit their /tmp. WRKDIR should have plenty of space. Other ports that use rustc might be affected too, but set it only in USES=cargo and lang/rust* ports for now. PR: 258126 With hat: rust
2021-09-06 19:16:38 +02:00
TMPDIR= ${WRKDIR}
framework: cleanup conditional-indentations in Mk/ Run Tools/scripts/indent_make_if.pl on all of Mk. These white space changes contribute greatly to the readability of those files. As we have a version control system, finding out the reasons for the changes prior to these white space changes is still easily possible Differential Revision: https://reviews.freebsd.org/D35024 Reviewed by: portmgr (rene, bapt)
2022-04-24 12:00:20 +02:00
. endif
lang/rust*: Mk/Uses/cargo.mk: Move TMPDIR to WRKDIR rustc stashes intermediary files in TMPDIR (default /tmp) which might cause issues for users that for some reason space limit their /tmp. WRKDIR should have plenty of space. Other ports that use rustc might be affected too, but set it only in USES=cargo and lang/rust* ports for now. PR: 258126 With hat: rust
2021-09-06 19:16:38 +02:00
Add USES=cargo to make creating ports of Rust applications easier Approved by: mat (mentor) Reviewed by: dumbbell, mat Differential Revision: https://reviews.freebsd.org/D11162
2017-06-21 18:22:32 +02:00
# Manage crate features.
framework: cleanup conditional-indentations in Mk/ Run Tools/scripts/indent_make_if.pl on all of Mk. These white space changes contribute greatly to the readability of those files. As we have a version control system, finding out the reasons for the changes prior to these white space changes is still easily possible Differential Revision: https://reviews.freebsd.org/D35024 Reviewed by: portmgr (rene, bapt)
2022-04-24 12:00:20 +02:00
. if !empty(CARGO_FEATURES:M--no-default-features)
Mk/Uses/cargo.mk: Allow disabling default features via CARGO_FEATURES CARGO_FEATURES is overloaded to accept --no-default-features as a special token which will set CARGO_{BUILD,INSTALL,TEST}_ARGS appropriately. This is done in preference over introducing yet another knob.
2020-03-04 16:00:17 +01:00
CARGO_BUILD_ARGS+= --no-default-features
CARGO_INSTALL_ARGS+= --no-default-features
CARGO_TEST_ARGS+= --no-default-features
framework: cleanup conditional-indentations in Mk/ Run Tools/scripts/indent_make_if.pl on all of Mk. These white space changes contribute greatly to the readability of those files. As we have a version control system, finding out the reasons for the changes prior to these white space changes is still easily possible Differential Revision: https://reviews.freebsd.org/D35024 Reviewed by: portmgr (rene, bapt)
2022-04-24 12:00:20 +02:00
. endif
. if !empty(CARGO_FEATURES:N--no-default-features)
Mk/Uses/cargo.mk: Allow disabling default features via CARGO_FEATURES CARGO_FEATURES is overloaded to accept --no-default-features as a special token which will set CARGO_{BUILD,INSTALL,TEST}_ARGS appropriately. This is done in preference over introducing yet another knob.
2020-03-04 16:00:17 +01:00
CARGO_BUILD_ARGS+= --features='${CARGO_FEATURES:N--no-default-features}'
CARGO_INSTALL_ARGS+= --features='${CARGO_FEATURES:N--no-default-features}'
CARGO_TEST_ARGS+= --features='${CARGO_FEATURES:N--no-default-features}'
framework: cleanup conditional-indentations in Mk/ Run Tools/scripts/indent_make_if.pl on all of Mk. These white space changes contribute greatly to the readability of those files. As we have a version control system, finding out the reasons for the changes prior to these white space changes is still easily possible Differential Revision: https://reviews.freebsd.org/D35024 Reviewed by: portmgr (rene, bapt)
2022-04-24 12:00:20 +02:00
. endif
Add USES=cargo to make creating ports of Rust applications easier Approved by: mat (mentor) Reviewed by: dumbbell, mat Differential Revision: https://reviews.freebsd.org/D11162
2017-06-21 18:22:32 +02:00
framework: cleanup conditional-indentations in Mk/ Run Tools/scripts/indent_make_if.pl on all of Mk. These white space changes contribute greatly to the readability of those files. As we have a version control system, finding out the reasons for the changes prior to these white space changes is still easily possible Differential Revision: https://reviews.freebsd.org/D35024 Reviewed by: portmgr (rene, bapt)
2022-04-24 12:00:20 +02:00
. if !defined(WITH_DEBUG)
Add USES=cargo to make creating ports of Rust applications easier Approved by: mat (mentor) Reviewed by: dumbbell, mat Differential Revision: https://reviews.freebsd.org/D11162
2017-06-21 18:22:32 +02:00
CARGO_BUILD_ARGS+= --release
CARGO_TEST_ARGS+= --release
framework: cleanup conditional-indentations in Mk/ Run Tools/scripts/indent_make_if.pl on all of Mk. These white space changes contribute greatly to the readability of those files. As we have a version control system, finding out the reasons for the changes prior to these white space changes is still easily possible Differential Revision: https://reviews.freebsd.org/D35024 Reviewed by: portmgr (rene, bapt)
2022-04-24 12:00:20 +02:00
. else
Add USES=cargo to make creating ports of Rust applications easier Approved by: mat (mentor) Reviewed by: dumbbell, mat Differential Revision: https://reviews.freebsd.org/D11162
2017-06-21 18:22:32 +02:00
CARGO_INSTALL_ARGS+= --debug
framework: cleanup conditional-indentations in Mk/ Run Tools/scripts/indent_make_if.pl on all of Mk. These white space changes contribute greatly to the readability of those files. As we have a version control system, finding out the reasons for the changes prior to these white space changes is still easily possible Differential Revision: https://reviews.freebsd.org/D35024 Reviewed by: portmgr (rene, bapt)
2022-04-24 12:00:20 +02:00
. endif
Add USES=cargo to make creating ports of Rust applications easier Approved by: mat (mentor) Reviewed by: dumbbell, mat Differential Revision: https://reviews.freebsd.org/D11162
2017-06-21 18:22:32 +02:00
framework: cleanup conditional-indentations in Mk/ Run Tools/scripts/indent_make_if.pl on all of Mk. These white space changes contribute greatly to the readability of those files. As we have a version control system, finding out the reasons for the changes prior to these white space changes is still easily possible Differential Revision: https://reviews.freebsd.org/D35024 Reviewed by: portmgr (rene, bapt)
2022-04-24 12:00:20 +02:00
. if ${_CARGO_CRATES:Mcmake}
Mk/Uses/cargo.mk: Encode more crate build dependencies - Add build/lib dependencies, environment variables to ports using the backtrace-sys, freetype-sys, gettext-sys, onig_sys, thrussh-libsodium crates instead of doing this individually for every port. - Add a DEV_WARNING when using libc versions < 0.2.37 to prevent instability of Rust applications on 12.0-CURRENT [1] - Sort cargo-crates-licenses output Reviewed by: pizzamig, jbeich [1] Differential Revision: https://reviews.freebsd.org/D15463
2018-06-14 11:56:02 +02:00
BUILD_DEPENDS+= cmake:devel/cmake
framework: cleanup conditional-indentations in Mk/ Run Tools/scripts/indent_make_if.pl on all of Mk. These white space changes contribute greatly to the readability of those files. As we have a version control system, finding out the reasons for the changes prior to these white space changes is still easily possible Differential Revision: https://reviews.freebsd.org/D35024 Reviewed by: portmgr (rene, bapt)
2022-04-24 12:00:20 +02:00
. endif
Mk/Uses/cargo.mk: Encode more crate build dependencies - Add build/lib dependencies, environment variables to ports using the backtrace-sys, freetype-sys, gettext-sys, onig_sys, thrussh-libsodium crates instead of doing this individually for every port. - Add a DEV_WARNING when using libc versions < 0.2.37 to prevent instability of Rust applications on 12.0-CURRENT [1] - Sort cargo-crates-licenses output Reviewed by: pizzamig, jbeich [1] Differential Revision: https://reviews.freebsd.org/D15463
2018-06-14 11:56:02 +02:00
framework: cleanup conditional-indentations in Mk/ Run Tools/scripts/indent_make_if.pl on all of Mk. These white space changes contribute greatly to the readability of those files. As we have a version control system, finding out the reasons for the changes prior to these white space changes is still easily possible Differential Revision: https://reviews.freebsd.org/D35024 Reviewed by: portmgr (rene, bapt)
2022-04-24 12:00:20 +02:00
. if ${_CARGO_CRATES:Mgettext-sys}
Mk/Uses/cargo.mk: Encode more crate build dependencies - Add build/lib dependencies, environment variables to ports using the backtrace-sys, freetype-sys, gettext-sys, onig_sys, thrussh-libsodium crates instead of doing this individually for every port. - Add a DEV_WARNING when using libc versions < 0.2.37 to prevent instability of Rust applications on 12.0-CURRENT [1] - Sort cargo-crates-licenses output Reviewed by: pizzamig, jbeich [1] Differential Revision: https://reviews.freebsd.org/D15463
2018-06-14 11:56:02 +02:00
CARGO_ENV+= GETTEXT_BIN_DIR=${LOCALBASE}/bin \
GETTEXT_INCLUDE_DIR=${LOCALBASE}/include \
GETTEXT_LIB_DIR=${LOCALBASE}/lib
framework: cleanup conditional-indentations in Mk/ Run Tools/scripts/indent_make_if.pl on all of Mk. These white space changes contribute greatly to the readability of those files. As we have a version control system, finding out the reasons for the changes prior to these white space changes is still easily possible Differential Revision: https://reviews.freebsd.org/D35024 Reviewed by: portmgr (rene, bapt)
2022-04-24 12:00:20 +02:00
. endif
Mk/Uses/cargo.mk: Encode more crate build dependencies - Add build/lib dependencies, environment variables to ports using the backtrace-sys, freetype-sys, gettext-sys, onig_sys, thrussh-libsodium crates instead of doing this individually for every port. - Add a DEV_WARNING when using libc versions < 0.2.37 to prevent instability of Rust applications on 12.0-CURRENT [1] - Sort cargo-crates-licenses output Reviewed by: pizzamig, jbeich [1] Differential Revision: https://reviews.freebsd.org/D15463
2018-06-14 11:56:02 +02:00
framework: cleanup conditional-indentations in Mk/ Run Tools/scripts/indent_make_if.pl on all of Mk. These white space changes contribute greatly to the readability of those files. As we have a version control system, finding out the reasons for the changes prior to these white space changes is still easily possible Differential Revision: https://reviews.freebsd.org/D35024 Reviewed by: portmgr (rene, bapt)
2022-04-24 12:00:20 +02:00
. if ${_CARGO_CRATES:Mjemalloc-sys}
Mk/Uses/cargo.mk: Add gmake build dependency for jemalloc-sys
2019-09-16 14:39:57 +02:00
BUILD_DEPENDS+= gmake:devel/gmake
framework: cleanup conditional-indentations in Mk/ Run Tools/scripts/indent_make_if.pl on all of Mk. These white space changes contribute greatly to the readability of those files. As we have a version control system, finding out the reasons for the changes prior to these white space changes is still easily possible Differential Revision: https://reviews.freebsd.org/D35024 Reviewed by: portmgr (rene, bapt)
2022-04-24 12:00:20 +02:00
. endif
Mk/Uses/cargo.mk: Add gmake build dependency for jemalloc-sys
2019-09-16 14:39:57 +02:00
framework: cleanup conditional-indentations in Mk/ Run Tools/scripts/indent_make_if.pl on all of Mk. These white space changes contribute greatly to the readability of those files. As we have a version control system, finding out the reasons for the changes prior to these white space changes is still easily possible Differential Revision: https://reviews.freebsd.org/D35024 Reviewed by: portmgr (rene, bapt)
2022-04-24 12:00:20 +02:00
. if ${_CARGO_CRATES:Mlibgit2-sys}
Add USES=cargo to make creating ports of Rust applications easier Approved by: mat (mentor) Reviewed by: dumbbell, mat Differential Revision: https://reviews.freebsd.org/D11162
2017-06-21 18:22:32 +02:00
# Use the system's libgit2 instead of building the bundled version
CARGO_ENV+= LIBGIT2_SYS_USE_PKG_CONFIG=1
framework: cleanup conditional-indentations in Mk/ Run Tools/scripts/indent_make_if.pl on all of Mk. These white space changes contribute greatly to the readability of those files. As we have a version control system, finding out the reasons for the changes prior to these white space changes is still easily possible Differential Revision: https://reviews.freebsd.org/D35024 Reviewed by: portmgr (rene, bapt)
2022-04-24 12:00:20 +02:00
. endif
Add USES=cargo to make creating ports of Rust applications easier Approved by: mat (mentor) Reviewed by: dumbbell, mat Differential Revision: https://reviews.freebsd.org/D11162
2017-06-21 18:22:32 +02:00
framework: cleanup conditional-indentations in Mk/ Run Tools/scripts/indent_make_if.pl on all of Mk. These white space changes contribute greatly to the readability of those files. As we have a version control system, finding out the reasons for the changes prior to these white space changes is still easily possible Differential Revision: https://reviews.freebsd.org/D35024 Reviewed by: portmgr (rene, bapt)
2022-04-24 12:00:20 +02:00
. if ${_CARGO_CRATES:Mlibssh2-sys}
lang/rust: unbundle libgit2/libssh2 - libgit2 in ports is nowadays newer than bundled version - libssh2 was already unbundled until 1.29.0 update - Unbundle libssh2 for USES=cargo (unused atm) PR: 231411 Approved by: rust (dumbbell, tobik)
2018-09-21 13:16:08 +02:00
# Use the system's libssh2 instead of building the bundled version
CARGO_ENV+= LIBSSH2_SYS_USE_PKG_CONFIG=1
framework: cleanup conditional-indentations in Mk/ Run Tools/scripts/indent_make_if.pl on all of Mk. These white space changes contribute greatly to the readability of those files. As we have a version control system, finding out the reasons for the changes prior to these white space changes is still easily possible Differential Revision: https://reviews.freebsd.org/D35024 Reviewed by: portmgr (rene, bapt)
2022-04-24 12:00:20 +02:00
. endif
lang/rust: unbundle libgit2/libssh2 - libgit2 in ports is nowadays newer than bundled version - libssh2 was already unbundled until 1.29.0 update - Unbundle libssh2 for USES=cargo (unused atm) PR: 231411 Approved by: rust (dumbbell, tobik)
2018-09-21 13:16:08 +02:00
framework: cleanup conditional-indentations in Mk/ Run Tools/scripts/indent_make_if.pl on all of Mk. These white space changes contribute greatly to the readability of those files. As we have a version control system, finding out the reasons for the changes prior to these white space changes is still easily possible Differential Revision: https://reviews.freebsd.org/D35024 Reviewed by: portmgr (rene, bapt)
2022-04-24 12:00:20 +02:00
. if ${_CARGO_CRATES:Monig_sys}
Mk/Uses/cargo.mk: Encode more crate build dependencies - Add build/lib dependencies, environment variables to ports using the backtrace-sys, freetype-sys, gettext-sys, onig_sys, thrussh-libsodium crates instead of doing this individually for every port. - Add a DEV_WARNING when using libc versions < 0.2.37 to prevent instability of Rust applications on 12.0-CURRENT [1] - Sort cargo-crates-licenses output Reviewed by: pizzamig, jbeich [1] Differential Revision: https://reviews.freebsd.org/D15463
2018-06-14 11:56:02 +02:00
# onig_sys always prefers the system library but will try to link
# statically with it. Since devel/oniguruma doesn't provide a static
# library it'll link to libonig.so instead. Strictly speaking setting
# RUSTONIG_SYSTEM_LIBONIG is not necessary, but will force onig_sys to
# always use the system's libonig as returned by `pkg-config oniguruma`.
CARGO_ENV+= RUSTONIG_SYSTEM_LIBONIG=1
framework: cleanup conditional-indentations in Mk/ Run Tools/scripts/indent_make_if.pl on all of Mk. These white space changes contribute greatly to the readability of those files. As we have a version control system, finding out the reasons for the changes prior to these white space changes is still easily possible Differential Revision: https://reviews.freebsd.org/D35024 Reviewed by: portmgr (rene, bapt)
2022-04-24 12:00:20 +02:00
. endif
Mk/Uses/cargo.mk: Encode more crate build dependencies - Add build/lib dependencies, environment variables to ports using the backtrace-sys, freetype-sys, gettext-sys, onig_sys, thrussh-libsodium crates instead of doing this individually for every port. - Add a DEV_WARNING when using libc versions < 0.2.37 to prevent instability of Rust applications on 12.0-CURRENT [1] - Sort cargo-crates-licenses output Reviewed by: pizzamig, jbeich [1] Differential Revision: https://reviews.freebsd.org/D15463
2018-06-14 11:56:02 +02:00
framework: cleanup conditional-indentations in Mk/ Run Tools/scripts/indent_make_if.pl on all of Mk. These white space changes contribute greatly to the readability of those files. As we have a version control system, finding out the reasons for the changes prior to these white space changes is still easily possible Differential Revision: https://reviews.freebsd.org/D35024 Reviewed by: portmgr (rene, bapt)
2022-04-24 12:00:20 +02:00
. if ${_CARGO_CRATES:Mopenssl-src}
Mk/Uses/cargo.mk: Add a warning about the openssl-src crate PR: 245337
2020-04-04 09:40:38 +02:00
DEV_WARNING+= "Please make sure this port uses the system OpenSSL and consider removing CARGO_CRATES=${CARGO_CRATES:Mopenssl-src-[0-9]*} (a vendored copy of OpenSSL) from the build, e.g., by patching Cargo.toml appropriately."
framework: cleanup conditional-indentations in Mk/ Run Tools/scripts/indent_make_if.pl on all of Mk. These white space changes contribute greatly to the readability of those files. As we have a version control system, finding out the reasons for the changes prior to these white space changes is still easily possible Differential Revision: https://reviews.freebsd.org/D35024 Reviewed by: portmgr (rene, bapt)
2022-04-24 12:00:20 +02:00
. endif
Mk/Uses/cargo.mk: Add a warning about the openssl-src crate PR: 245337
2020-04-04 09:40:38 +02:00
framework: cleanup conditional-indentations in Mk/ Run Tools/scripts/indent_make_if.pl on all of Mk. These white space changes contribute greatly to the readability of those files. As we have a version control system, finding out the reasons for the changes prior to these white space changes is still easily possible Differential Revision: https://reviews.freebsd.org/D35024 Reviewed by: portmgr (rene, bapt)
2022-04-24 12:00:20 +02:00
. if ${_CARGO_CRATES:Mopenssl-sys}
Add USES=cargo to make creating ports of Rust applications easier Approved by: mat (mentor) Reviewed by: dumbbell, mat Differential Revision: https://reviews.freebsd.org/D11162
2017-06-21 18:22:32 +02:00
# Make sure that openssl-sys can find the correct version of OpenSSL
CARGO_ENV+= OPENSSL_LIB_DIR=${OPENSSLLIB} \
OPENSSL_INCLUDE_DIR=${OPENSSLINC}
framework: cleanup conditional-indentations in Mk/ Run Tools/scripts/indent_make_if.pl on all of Mk. These white space changes contribute greatly to the readability of those files. As we have a version control system, finding out the reasons for the changes prior to these white space changes is still easily possible Differential Revision: https://reviews.freebsd.org/D35024 Reviewed by: portmgr (rene, bapt)
2022-04-24 12:00:20 +02:00
. endif
Add USES=cargo to make creating ports of Rust applications easier Approved by: mat (mentor) Reviewed by: dumbbell, mat Differential Revision: https://reviews.freebsd.org/D11162
2017-06-21 18:22:32 +02:00
framework: cleanup conditional-indentations in Mk/ Run Tools/scripts/indent_make_if.pl on all of Mk. These white space changes contribute greatly to the readability of those files. As we have a version control system, finding out the reasons for the changes prior to these white space changes is still easily possible Differential Revision: https://reviews.freebsd.org/D35024 Reviewed by: portmgr (rene, bapt)
2022-04-24 12:00:20 +02:00
. if ${_CARGO_CRATES:Mpkg-config}
Add USES=cargo to make creating ports of Rust applications easier Approved by: mat (mentor) Reviewed by: dumbbell, mat Differential Revision: https://reviews.freebsd.org/D11162
2017-06-21 18:22:32 +02:00
.include "${USESDIR}/pkgconfig.mk"
framework: cleanup conditional-indentations in Mk/ Run Tools/scripts/indent_make_if.pl on all of Mk. These white space changes contribute greatly to the readability of those files. As we have a version control system, finding out the reasons for the changes prior to these white space changes is still easily possible Differential Revision: https://reviews.freebsd.org/D35024 Reviewed by: portmgr (rene, bapt)
2022-04-24 12:00:20 +02:00
. endif
Add USES=cargo to make creating ports of Rust applications easier Approved by: mat (mentor) Reviewed by: dumbbell, mat Differential Revision: https://reviews.freebsd.org/D11162
2017-06-21 18:22:32 +02:00
framework: cleanup conditional-indentations in Mk/ Run Tools/scripts/indent_make_if.pl on all of Mk. These white space changes contribute greatly to the readability of those files. As we have a version control system, finding out the reasons for the changes prior to these white space changes is still easily possible Differential Revision: https://reviews.freebsd.org/D35024 Reviewed by: portmgr (rene, bapt)
2022-04-24 12:00:20 +02:00
. for _index _crate _name _version in ${_CARGO_CRATES}
Mk/Uses/cargo.mk: Refactor MASTER_SITES and DISTFILES construction (D30099) Split CARGO_CRATES into (index, crate, name, version) 4-tuples and use them to construct MASTER_SITES and DISTFILES. We can also match crate name and versions more directly below. As a bonus this is slightly faster and will flag a malformed CARGO_CRATES earlier with a "wrong number of words" error. Runtime of the following command was noticeably faster $ <rust-ports /usr/bin/time xe -F make -C {} -V DISTFILES -V MASTER_SITES >/dev/null Before: 56.99 real 50.05 user 6.44 sys Now: 38.89 real 31.63 user 6.86 sys PR: 255608 Exp-run by: antoine
2021-04-29 11:48:10 +02:00
# Split up semantic version and try to sanitize it by removing
# pre-release identifier (-) or build metadata (+)
framework: cleanup conditional-indentations in Mk/ Run Tools/scripts/indent_make_if.pl on all of Mk. These white space changes contribute greatly to the readability of those files. As we have a version control system, finding out the reasons for the changes prior to these white space changes is still easily possible Differential Revision: https://reviews.freebsd.org/D35024 Reviewed by: portmgr (rene, bapt)
2022-04-24 12:00:20 +02:00
. if ${_version:S/./ /:S/./ /:C/[-+].*//:_:[#]} == 3
. for _major _minor _patch in $_
Mk/Uses/cargo.mk: Refactor MASTER_SITES and DISTFILES construction (D30099) Split CARGO_CRATES into (index, crate, name, version) 4-tuples and use them to construct MASTER_SITES and DISTFILES. We can also match crate name and versions more directly below. As a bonus this is slightly faster and will flag a malformed CARGO_CRATES earlier with a "wrong number of words" error. Runtime of the following command was noticeably faster $ <rust-ports /usr/bin/time xe -F make -C {} -V DISTFILES -V MASTER_SITES >/dev/null Before: 56.99 real 50.05 user 6.44 sys Now: 38.89 real 31.63 user 6.86 sys PR: 255608 Exp-run by: antoine
2021-04-29 11:48:10 +02:00
# FreeBSD 12.0 changed ABI: r318736 and r320043
# https://github.com/rust-lang/libc/commit/78f93220d70e
# https://github.com/rust-lang/libc/commit/969ad2b73cdc
framework: cleanup conditional-indentations in Mk/ Run Tools/scripts/indent_make_if.pl on all of Mk. These white space changes contribute greatly to the readability of those files. As we have a version control system, finding out the reasons for the changes prior to these white space changes is still easily possible Differential Revision: https://reviews.freebsd.org/D35024 Reviewed by: portmgr (rene, bapt)
2022-04-24 12:00:20 +02:00
. if ${_name} == libc && ${_major} == 0 && (${_minor} < 2 || (${_minor} == 2 && ${_patch} < 38))
Mk/Uses/cargo.mk: Refactor MASTER_SITES and DISTFILES construction (D30099) Split CARGO_CRATES into (index, crate, name, version) 4-tuples and use them to construct MASTER_SITES and DISTFILES. We can also match crate name and versions more directly below. As a bonus this is slightly faster and will flag a malformed CARGO_CRATES earlier with a "wrong number of words" error. Runtime of the following command was noticeably faster $ <rust-ports /usr/bin/time xe -F make -C {} -V DISTFILES -V MASTER_SITES >/dev/null Before: 56.99 real 50.05 user 6.44 sys Now: 38.89 real 31.63 user 6.86 sys PR: 255608 Exp-run by: antoine
2021-04-29 11:48:10 +02:00
DEV_ERROR+= "CARGO_CRATES=${_crate} may be unstable on FreeBSD 12.0. Consider updating to the latest version \(higher than 0.2.37\)."
framework: cleanup conditional-indentations in Mk/ Run Tools/scripts/indent_make_if.pl on all of Mk. These white space changes contribute greatly to the readability of those files. As we have a version control system, finding out the reasons for the changes prior to these white space changes is still easily possible Differential Revision: https://reviews.freebsd.org/D35024 Reviewed by: portmgr (rene, bapt)
2022-04-24 12:00:20 +02:00
. endif
. if ${_name} == libc && ${_major} == 0 && (${_minor} < 2 || (${_minor} == 2 && ${_patch} < 49))
Mk/Uses/cargo.mk: Refactor MASTER_SITES and DISTFILES construction (D30099) Split CARGO_CRATES into (index, crate, name, version) 4-tuples and use them to construct MASTER_SITES and DISTFILES. We can also match crate name and versions more directly below. As a bonus this is slightly faster and will flag a malformed CARGO_CRATES earlier with a "wrong number of words" error. Runtime of the following command was noticeably faster $ <rust-ports /usr/bin/time xe -F make -C {} -V DISTFILES -V MASTER_SITES >/dev/null Before: 56.99 real 50.05 user 6.44 sys Now: 38.89 real 31.63 user 6.86 sys PR: 255608 Exp-run by: antoine
2021-04-29 11:48:10 +02:00
DEV_ERROR+= "CARGO_CRATES=${_crate} may be unstable on aarch64 or not build on armv6, armv7, powerpc64. Consider updating to the latest version \(higher than 0.2.49\)."
framework: cleanup conditional-indentations in Mk/ Run Tools/scripts/indent_make_if.pl on all of Mk. These white space changes contribute greatly to the readability of those files. As we have a version control system, finding out the reasons for the changes prior to these white space changes is still easily possible Differential Revision: https://reviews.freebsd.org/D35024 Reviewed by: portmgr (rene, bapt)
2022-04-24 12:00:20 +02:00
. endif
Mk/Uses/cargo.mk: Refactor MASTER_SITES and DISTFILES construction (D30099) Split CARGO_CRATES into (index, crate, name, version) 4-tuples and use them to construct MASTER_SITES and DISTFILES. We can also match crate name and versions more directly below. As a bonus this is slightly faster and will flag a malformed CARGO_CRATES earlier with a "wrong number of words" error. Runtime of the following command was noticeably faster $ <rust-ports /usr/bin/time xe -F make -C {} -V DISTFILES -V MASTER_SITES >/dev/null Before: 56.99 real 50.05 user 6.44 sys Now: 38.89 real 31.63 user 6.86 sys PR: 255608 Exp-run by: antoine
2021-04-29 11:48:10 +02:00
# FreeBSD 12.0 updated base OpenSSL in r339270:
# https://github.com/sfackler/rust-openssl/commit/276577553501
framework: cleanup conditional-indentations in Mk/ Run Tools/scripts/indent_make_if.pl on all of Mk. These white space changes contribute greatly to the readability of those files. As we have a version control system, finding out the reasons for the changes prior to these white space changes is still easily possible Differential Revision: https://reviews.freebsd.org/D35024 Reviewed by: portmgr (rene, bapt)
2022-04-24 12:00:20 +02:00
. if ${_name} == openssl && !exists(${PATCHDIR}/patch-openssl-1.1.1) && ${_major} == 0 && (${_minor} < 10 || (${_minor} == 10 && ${_patch} < 4))
Mk/Uses/cargo.mk: Refactor MASTER_SITES and DISTFILES construction (D30099) Split CARGO_CRATES into (index, crate, name, version) 4-tuples and use them to construct MASTER_SITES and DISTFILES. We can also match crate name and versions more directly below. As a bonus this is slightly faster and will flag a malformed CARGO_CRATES earlier with a "wrong number of words" error. Runtime of the following command was noticeably faster $ <rust-ports /usr/bin/time xe -F make -C {} -V DISTFILES -V MASTER_SITES >/dev/null Before: 56.99 real 50.05 user 6.44 sys Now: 38.89 real 31.63 user 6.86 sys PR: 255608 Exp-run by: antoine
2021-04-29 11:48:10 +02:00
DEV_WARNING+= "CARGO_CRATES=${_crate} does not support OpenSSL 1.1.1. Consider updating to the latest version \(higher than 0.10.3\)."
framework: cleanup conditional-indentations in Mk/ Run Tools/scripts/indent_make_if.pl on all of Mk. These white space changes contribute greatly to the readability of those files. As we have a version control system, finding out the reasons for the changes prior to these white space changes is still easily possible Differential Revision: https://reviews.freebsd.org/D35024 Reviewed by: portmgr (rene, bapt)
2022-04-24 12:00:20 +02:00
. endif
. endfor
. endif
. endfor
Mk/Uses/cargo.mk: Refactor MASTER_SITES and DISTFILES construction (D30099) Split CARGO_CRATES into (index, crate, name, version) 4-tuples and use them to construct MASTER_SITES and DISTFILES. We can also match crate name and versions more directly below. As a bonus this is slightly faster and will flag a malformed CARGO_CRATES earlier with a "wrong number of words" error. Runtime of the following command was noticeably faster $ <rust-ports /usr/bin/time xe -F make -C {} -V DISTFILES -V MASTER_SITES >/dev/null Before: 56.99 real 50.05 user 6.44 sys Now: 38.89 real 31.63 user 6.86 sys PR: 255608 Exp-run by: antoine
2021-04-29 11:48:10 +02:00
Add USES=cargo to make creating ports of Rust applications easier Approved by: mat (mentor) Reviewed by: dumbbell, mat Differential Revision: https://reviews.freebsd.org/D11162
2017-06-21 18:22:32 +02:00
_USES_extract+= 600:cargo-extract
cargo-extract:
# target for preparing crates directory. It will put all crates in
# the local crates directory.
@${ECHO_MSG} "===> Moving crates to ${CARGO_VENDOR_DIR}"
@${MKDIR} ${CARGO_VENDOR_DIR}
framework: cleanup conditional-indentations in Mk/ Run Tools/scripts/indent_make_if.pl on all of Mk. These white space changes contribute greatly to the readability of those files. As we have a version control system, finding out the reasons for the changes prior to these white space changes is still easily possible Differential Revision: https://reviews.freebsd.org/D35024 Reviewed by: portmgr (rene, bapt)
2022-04-24 12:00:20 +02:00
. for _index _crate _name _version in ${_CARGO_CRATES}
. if ${_index} != @git
Add USES=cargo to make creating ports of Rust applications easier Approved by: mat (mentor) Reviewed by: dumbbell, mat Differential Revision: https://reviews.freebsd.org/D11162
2017-06-21 18:22:32 +02:00
@${MV} ${WRKDIR}/${_crate} ${CARGO_VENDOR_DIR}/${_crate}
@${PRINTF} '{"package":"%s","files":{}}' \
Mk/Uses/cargo.mk: Use canonical crate file extension going forward Crates should have the file extension .crate not .tar.gz. Cargo saves them with that extension and it is also what their original name was according to file(1): $ file rust/crates/* rust/crates/better-panic-0.2.0.tar.gz:gzip compressed data, was "better-panic-0.2.0.crate" rust/crates/binary-space-partition-0.1.2.tar.gz:gzip compressed data, was "binary-space-partition-0.1.2.crate" ... The only reason we used .tar.gz is that it was that way in OpenBSD's devel/cargo/cargo.port.mk module. At the moment they are all .tar.gz but they might have a different format in the future. Doing a delayed rollout of this over a change-everything-once approach to - not immeditately invalidate all uncommitted port changes or external ports - not make sweeping changes twice in main and 2021Q2 at the cost of having a transition period where mirrors might have to carry both the .tar.gz and .crate tarballs (all crates combined are ~600 MiB). Reviewed by: jbeich MFH: 2021Q2 (to ease future cherry picks) Differential Revision: https://reviews.freebsd.org/D29760
2021-04-17 07:27:24 +02:00
$$(${SHA256} -q ${DISTDIR}/${CARGO_DIST_SUBDIR}/${_crate}${CARGO_CRATE_EXT}) \
Add USES=cargo to make creating ports of Rust applications easier Approved by: mat (mentor) Reviewed by: dumbbell, mat Differential Revision: https://reviews.freebsd.org/D11162
2017-06-21 18:22:32 +02:00
> ${CARGO_VENDOR_DIR}/${_crate}/.cargo-checksum.json
Mk/Uses/cargo.mk: QoL improvement during makepatch Cargo normalizes Cargo.toml when crates are published. It creates a Cargo.toml.orig to preserve the original. Rename them to not interfere with makepatch and avoid creating a bunch of useless and wrong files/patch-*Cargo.toml. Suggested by: mat
2019-05-24 09:57:11 +02:00
@if [ -r ${CARGO_VENDOR_DIR}/${_crate}/Cargo.toml.orig ]; then \
${MV} ${CARGO_VENDOR_DIR}/${_crate}/Cargo.toml.orig \
${CARGO_VENDOR_DIR}/${_crate}/Cargo.toml.orig-cargo; \
fi
framework: cleanup conditional-indentations in Mk/ Run Tools/scripts/indent_make_if.pl on all of Mk. These white space changes contribute greatly to the readability of those files. As we have a version control system, finding out the reasons for the changes prior to these white space changes is still easily possible Differential Revision: https://reviews.freebsd.org/D35024 Reviewed by: portmgr (rene, bapt)
2022-04-24 12:00:20 +02:00
. endif
. endfor
Add USES=cargo to make creating ports of Rust applications easier Approved by: mat (mentor) Reviewed by: dumbbell, mat Differential Revision: https://reviews.freebsd.org/D11162
2017-06-21 18:22:32 +02:00
framework: cleanup conditional-indentations in Mk/ Run Tools/scripts/indent_make_if.pl on all of Mk. These white space changes contribute greatly to the readability of those files. As we have a version control system, finding out the reasons for the changes prior to these white space changes is still easily possible Differential Revision: https://reviews.freebsd.org/D35024 Reviewed by: portmgr (rene, bapt)
2022-04-24 12:00:20 +02:00
. if ${CARGO_CONFIGURE:tl} == "yes"
Mk/Uses/cargo.mk: Do not override do-configure Cargo vendoring can be useful even for ports that use other build systems like Meson to call Cargo for the actual build. Often they use the framework's default do-configure which USES=cargo should not overwrite. Remove hacks from games/jaggedalliance2 and x11/squeekboard. Reviewed by: jbeich Differential Revision: https://reviews.freebsd.org/D22619
2019-12-01 09:43:43 +01:00
_USES_configure+= 250:cargo-configure
Add USES=cargo to make creating ports of Rust applications easier Approved by: mat (mentor) Reviewed by: dumbbell, mat Differential Revision: https://reviews.freebsd.org/D11162
2017-06-21 18:22:32 +02:00
# configure hook. Place a config file for overriding crates-io index
# by local source directory.
Mk/Uses/cargo.mk: Do not override do-configure Cargo vendoring can be useful even for ports that use other build systems like Meson to call Cargo for the actual build. Often they use the framework's default do-configure which USES=cargo should not overwrite. Remove hacks from games/jaggedalliance2 and x11/squeekboard. Reviewed by: jbeich Differential Revision: https://reviews.freebsd.org/D22619
2019-12-01 09:43:43 +01:00
cargo-configure:
lang/rust: Add COMPAT_FREEBSD11 canary This attempts to provide a nicer error message for the subset of users who build their own kernels without COMPAT_FREEBSD11 and then attempt to build lang/rust. The Rust ecosystem currently uses pre-ino64 syscalls, so building lang/rust without COMPAT_FREEBSD11 is not going to work. The error message for this is non-obvious and there is a new bug for this at least every 1-2 months. Hopefully this will improve the situation a little. Cargo and Gecko ports are similarly affected, so add the pre-build check to them too. Reviewed by: jbeich, mikael.urankar@gmail.com Tested by: madpilot (negative case) Approved by: gecko (jbeich) Differential Revision: https://reviews.freebsd.org/D23100
2020-01-13 19:36:04 +01:00
# Check that the running kernel has COMPAT_FREEBSD11 required by lang/rust post-ino64
@${SETENV} CC="${CC}" OPSYS="${OPSYS}" OSVERSION="${OSVERSION}" WRKDIR="${WRKDIR}" \
${SH} ${SCRIPTSDIR}/rust-compat11-canary.sh
Uses/cargo: Rework git source support based on patch-in-config sections Git sources from `Cargo.lock` are added to `CARGO_CRATES` through the normal mechanism of `make cargo-crates` by the porter. They are used to populate `MASTER_SITES`, `DISTFILES` with static git-archive(1) tarballs a la `USE_GITHUB`, `USE_GITLAB`. In the configure phase we generate `[patch]` sections in the config file which will cause `cargo update` to auto-update `Cargo.lock` to point to the appropriate extraction directories. Normally `cargo update` would connect to the network to update all Git sources but since rust-1.55.0 our cargo has been patched to skip this when `CARGO_FREEBSD_PORTS_SKIP_GIT_UPDATE` is set in the environment. This replaces the old `CARGO_USE_GITHUB`, `CARGO_USE_GITLAB` hacks where this was done by editing all `Cargo.toml` with sed(1) calls. Additionally, we try to automatically infer the individiual crate sub-directories inside the Git sources based on `package.name` in `Cargo.toml` to remove the need for `CARGO_GIT_SUBDIR`. USES=cargo also now sets `WRKSRC_crate_$name` for each crate to point to the crate extraction directories. PR: 256581 Reviewed by: jbeich
2021-09-07 16:08:46 +02:00
@${ECHO_MSG} "===> Cargo config:"
Add USES=cargo to make creating ports of Rust applications easier Approved by: mat (mentor) Reviewed by: dumbbell, mat Differential Revision: https://reviews.freebsd.org/D11162
2017-06-21 18:22:32 +02:00
@${MKDIR} ${WRKDIR}/.cargo
Uses/cargo: Rework git source support based on patch-in-config sections Git sources from `Cargo.lock` are added to `CARGO_CRATES` through the normal mechanism of `make cargo-crates` by the porter. They are used to populate `MASTER_SITES`, `DISTFILES` with static git-archive(1) tarballs a la `USE_GITHUB`, `USE_GITLAB`. In the configure phase we generate `[patch]` sections in the config file which will cause `cargo update` to auto-update `Cargo.lock` to point to the appropriate extraction directories. Normally `cargo update` would connect to the network to update all Git sources but since rust-1.55.0 our cargo has been patched to skip this when `CARGO_FREEBSD_PORTS_SKIP_GIT_UPDATE` is set in the environment. This replaces the old `CARGO_USE_GITHUB`, `CARGO_USE_GITLAB` hacks where this was done by editing all `Cargo.toml` with sed(1) calls. Additionally, we try to automatically infer the individiual crate sub-directories inside the Git sources based on `package.name` in `Cargo.toml` to remove the need for `CARGO_GIT_SUBDIR`. USES=cargo also now sets `WRKSRC_crate_$name` for each crate to point to the crate extraction directories. PR: 256581 Reviewed by: jbeich
2021-09-07 16:08:46 +02:00
@: > ${WRKDIR}/.cargo/config.toml
@${ECHO_CMD} "[source.cargo]" >> ${WRKDIR}/.cargo/config.toml
@${ECHO_CMD} "directory = '${CARGO_VENDOR_DIR}'" >> ${WRKDIR}/.cargo/config.toml
@${ECHO_CMD} "[source.crates-io]" >> ${WRKDIR}/.cargo/config.toml
@${ECHO_CMD} "replace-with = 'cargo'" >> ${WRKDIR}/.cargo/config.toml
framework: cleanup conditional-indentations in Mk/ Run Tools/scripts/indent_make_if.pl on all of Mk. These white space changes contribute greatly to the readability of those files. As we have a version control system, finding out the reasons for the changes prior to these white space changes is still easily possible Differential Revision: https://reviews.freebsd.org/D35024 Reviewed by: portmgr (rene, bapt)
2022-04-24 12:00:20 +02:00
. if !empty(_CARGO_GIT_SOURCES)
Uses/cargo: Rework git source support based on patch-in-config sections Git sources from `Cargo.lock` are added to `CARGO_CRATES` through the normal mechanism of `make cargo-crates` by the porter. They are used to populate `MASTER_SITES`, `DISTFILES` with static git-archive(1) tarballs a la `USE_GITHUB`, `USE_GITLAB`. In the configure phase we generate `[patch]` sections in the config file which will cause `cargo update` to auto-update `Cargo.lock` to point to the appropriate extraction directories. Normally `cargo update` would connect to the network to update all Git sources but since rust-1.55.0 our cargo has been patched to skip this when `CARGO_FREEBSD_PORTS_SKIP_GIT_UPDATE` is set in the environment. This replaces the old `CARGO_USE_GITHUB`, `CARGO_USE_GITLAB` hacks where this was done by editing all `Cargo.toml` with sed(1) calls. Additionally, we try to automatically infer the individiual crate sub-directories inside the Git sources based on `package.name` in `Cargo.toml` to remove the need for `CARGO_GIT_SUBDIR`. USES=cargo also now sets `WRKSRC_crate_$name` for each crate to point to the crate extraction directories. PR: 256581 Reviewed by: jbeich
2021-09-07 16:08:46 +02:00
@${_CARGO_AWK} ${SCRIPTSDIR}/cargo-crates-git-configure.awk \
/dev/null >> ${WRKDIR}/.cargo/config.toml
framework: cleanup conditional-indentations in Mk/ Run Tools/scripts/indent_make_if.pl on all of Mk. These white space changes contribute greatly to the readability of those files. As we have a version control system, finding out the reasons for the changes prior to these white space changes is still easily possible Differential Revision: https://reviews.freebsd.org/D35024 Reviewed by: portmgr (rene, bapt)
2022-04-24 12:00:20 +02:00
. endif
Uses/cargo: Rework git source support based on patch-in-config sections Git sources from `Cargo.lock` are added to `CARGO_CRATES` through the normal mechanism of `make cargo-crates` by the porter. They are used to populate `MASTER_SITES`, `DISTFILES` with static git-archive(1) tarballs a la `USE_GITHUB`, `USE_GITLAB`. In the configure phase we generate `[patch]` sections in the config file which will cause `cargo update` to auto-update `Cargo.lock` to point to the appropriate extraction directories. Normally `cargo update` would connect to the network to update all Git sources but since rust-1.55.0 our cargo has been patched to skip this when `CARGO_FREEBSD_PORTS_SKIP_GIT_UPDATE` is set in the environment. This replaces the old `CARGO_USE_GITHUB`, `CARGO_USE_GITLAB` hacks where this was done by editing all `Cargo.toml` with sed(1) calls. Additionally, we try to automatically infer the individiual crate sub-directories inside the Git sources based on `package.name` in `Cargo.toml` to remove the need for `CARGO_GIT_SUBDIR`. USES=cargo also now sets `WRKSRC_crate_$name` for each crate to point to the crate extraction directories. PR: 256581 Reviewed by: jbeich
2021-09-07 16:08:46 +02:00
@${CAT} ${WRKDIR}/.cargo/config.toml
Add USES=cargo to make creating ports of Rust applications easier Approved by: mat (mentor) Reviewed by: dumbbell, mat Differential Revision: https://reviews.freebsd.org/D11162
2017-06-21 18:22:32 +02:00
@if ! ${GREP} -qF '[profile.release]' ${CARGO_CARGOTOML}; then \
${ECHO_CMD} "" >> ${CARGO_CARGOTOML}; \
${ECHO_CMD} "[profile.release]" >> ${CARGO_CARGOTOML}; \
${ECHO_CMD} "opt-level = 2" >> ${CARGO_CARGOTOML}; \
${ECHO_CMD} "debug = false" >> ${CARGO_CARGOTOML}; \
fi
Uses/cargo: Rework git source support based on patch-in-config sections Git sources from `Cargo.lock` are added to `CARGO_CRATES` through the normal mechanism of `make cargo-crates` by the porter. They are used to populate `MASTER_SITES`, `DISTFILES` with static git-archive(1) tarballs a la `USE_GITHUB`, `USE_GITLAB`. In the configure phase we generate `[patch]` sections in the config file which will cause `cargo update` to auto-update `Cargo.lock` to point to the appropriate extraction directories. Normally `cargo update` would connect to the network to update all Git sources but since rust-1.55.0 our cargo has been patched to skip this when `CARGO_FREEBSD_PORTS_SKIP_GIT_UPDATE` is set in the environment. This replaces the old `CARGO_USE_GITHUB`, `CARGO_USE_GITLAB` hacks where this was done by editing all `Cargo.toml` with sed(1) calls. Additionally, we try to automatically infer the individiual crate sub-directories inside the Git sources based on `package.name` in `Cargo.toml` to remove the need for `CARGO_GIT_SUBDIR`. USES=cargo also now sets `WRKSRC_crate_$name` for each crate to point to the crate extraction directories. PR: 256581 Reviewed by: jbeich
2021-09-07 16:08:46 +02:00
@${ECHO_MSG} "===> Updating Cargo.lock"
Add USES=cargo to make creating ports of Rust applications easier Approved by: mat (mentor) Reviewed by: dumbbell, mat Differential Revision: https://reviews.freebsd.org/D11162
2017-06-21 18:22:32 +02:00
@${CARGO_CARGO_RUN} update \
--manifest-path ${CARGO_CARGOTOML} \
--verbose \
Mk/Uses/cargo.mk: Make build scripts more verbose Build scripts might build bundled libraries but non-error output is hiddden by cargo. Given a crate with large enough bundled library (looking at you rusty_v8) the build just sits there in silence forever and you do not know what is happening or if anything is happening at all. This also makes Poudriere build logs less useful. Pass an additional --verbose to cargo to get more noisy output. https://doc.rust-lang.org/cargo/reference/build-scripts.html#outputs-of-the-build-script
2021-04-13 09:01:20 +02:00
--verbose \
Add USES=cargo to make creating ports of Rust applications easier Approved by: mat (mentor) Reviewed by: dumbbell, mat Differential Revision: https://reviews.freebsd.org/D11162
2017-06-21 18:22:32 +02:00
${CARGO_UPDATE_ARGS}
framework: cleanup conditional-indentations in Mk/ Run Tools/scripts/indent_make_if.pl on all of Mk. These white space changes contribute greatly to the readability of those files. As we have a version control system, finding out the reasons for the changes prior to these white space changes is still easily possible Differential Revision: https://reviews.freebsd.org/D35024 Reviewed by: portmgr (rene, bapt)
2022-04-24 12:00:20 +02:00
. endif
Add USES=cargo to make creating ports of Rust applications easier Approved by: mat (mentor) Reviewed by: dumbbell, mat Differential Revision: https://reviews.freebsd.org/D11162
2017-06-21 18:22:32 +02:00
framework: cleanup conditional-indentations in Mk/ Run Tools/scripts/indent_make_if.pl on all of Mk. These white space changes contribute greatly to the readability of those files. As we have a version control system, finding out the reasons for the changes prior to these white space changes is still easily possible Differential Revision: https://reviews.freebsd.org/D35024 Reviewed by: portmgr (rene, bapt)
2022-04-24 12:00:20 +02:00
. if !target(do-build) && ${CARGO_BUILD:tl} == "yes"
Add USES=cargo to make creating ports of Rust applications easier Approved by: mat (mentor) Reviewed by: dumbbell, mat Differential Revision: https://reviews.freebsd.org/D11162
2017-06-21 18:22:32 +02:00
do-build:
@${CARGO_CARGO_RUN} build \
--manifest-path ${CARGO_CARGOTOML} \
--verbose \
Mk/Uses/cargo.mk: Make build scripts more verbose Build scripts might build bundled libraries but non-error output is hiddden by cargo. Given a crate with large enough bundled library (looking at you rusty_v8) the build just sits there in silence forever and you do not know what is happening or if anything is happening at all. This also makes Poudriere build logs less useful. Pass an additional --verbose to cargo to get more noisy output. https://doc.rust-lang.org/cargo/reference/build-scripts.html#outputs-of-the-build-script
2021-04-13 09:01:20 +02:00
--verbose \
Add USES=cargo to make creating ports of Rust applications easier Approved by: mat (mentor) Reviewed by: dumbbell, mat Differential Revision: https://reviews.freebsd.org/D11162
2017-06-21 18:22:32 +02:00
${CARGO_BUILD_ARGS}
framework: cleanup conditional-indentations in Mk/ Run Tools/scripts/indent_make_if.pl on all of Mk. These white space changes contribute greatly to the readability of those files. As we have a version control system, finding out the reasons for the changes prior to these white space changes is still easily possible Differential Revision: https://reviews.freebsd.org/D35024 Reviewed by: portmgr (rene, bapt)
2022-04-24 12:00:20 +02:00
. endif
Add USES=cargo to make creating ports of Rust applications easier Approved by: mat (mentor) Reviewed by: dumbbell, mat Differential Revision: https://reviews.freebsd.org/D11162
2017-06-21 18:22:32 +02:00
framework: cleanup conditional-indentations in Mk/ Run Tools/scripts/indent_make_if.pl on all of Mk. These white space changes contribute greatly to the readability of those files. As we have a version control system, finding out the reasons for the changes prior to these white space changes is still easily possible Differential Revision: https://reviews.freebsd.org/D35024 Reviewed by: portmgr (rene, bapt)
2022-04-24 12:00:20 +02:00
. if !target(do-install) && ${CARGO_INSTALL:tl} == "yes"
Add USES=cargo to make creating ports of Rust applications easier Approved by: mat (mentor) Reviewed by: dumbbell, mat Differential Revision: https://reviews.freebsd.org/D11162
2017-06-21 18:22:32 +02:00
do-install:
framework: cleanup conditional-indentations in Mk/ Run Tools/scripts/indent_make_if.pl on all of Mk. These white space changes contribute greatly to the readability of those files. As we have a version control system, finding out the reasons for the changes prior to these white space changes is still easily possible Differential Revision: https://reviews.freebsd.org/D35024 Reviewed by: portmgr (rene, bapt)
2022-04-24 12:00:20 +02:00
. for path in ${CARGO_INSTALL_PATH}
Add USES=cargo to make creating ports of Rust applications easier Approved by: mat (mentor) Reviewed by: dumbbell, mat Differential Revision: https://reviews.freebsd.org/D11162
2017-06-21 18:22:32 +02:00
@${CARGO_CARGO_RUN} install \
lang/rust: Update to 1.41.0 - Force rebuild all consumers to catch regressions early - Switch to cross-compiled (from amd64) bootstraps for all architectures generated with the incoming lang/rust-bootstrap - Update cargo-c to 0.5.2 to unbreak librav1e build - Make use of regular MAKE_ENV/TEST_ENV in lang/rust - Turn on RUST_BACKTRACE in lang/rust and USES=cargo to hopefully produce more useful failure logs when something panics during builds Changes: https://blog.rust-lang.org/2020/01/30/Rust-1.41.0.html Tested by: mikael, tobik With hat: rust Differential Revision: https://reviews.freebsd.org/D23385
2020-01-30 21:00:06 +01:00
--no-track \
Mk/Uses/cargo.mk: Add CARGO_INSTALL_PATH knob It can be used to overwrite the --path argument when calling `cargo install` to point cargo to different local crates to install. This might be necessary when ${WRKSRC}/Cargo.toml is only a virtual manifest.
2019-06-10 12:56:04 +02:00
--path "${path}" \
Add USES=cargo to make creating ports of Rust applications easier Approved by: mat (mentor) Reviewed by: dumbbell, mat Differential Revision: https://reviews.freebsd.org/D11162
2017-06-21 18:22:32 +02:00
--root "${STAGEDIR}${PREFIX}" \
--verbose \
Mk/Uses/cargo.mk: Make build scripts more verbose Build scripts might build bundled libraries but non-error output is hiddden by cargo. Given a crate with large enough bundled library (looking at you rusty_v8) the build just sits there in silence forever and you do not know what is happening or if anything is happening at all. This also makes Poudriere build logs less useful. Pass an additional --verbose to cargo to get more noisy output. https://doc.rust-lang.org/cargo/reference/build-scripts.html#outputs-of-the-build-script
2021-04-13 09:01:20 +02:00
--verbose \
Add USES=cargo to make creating ports of Rust applications easier Approved by: mat (mentor) Reviewed by: dumbbell, mat Differential Revision: https://reviews.freebsd.org/D11162
2017-06-21 18:22:32 +02:00
${CARGO_INSTALL_ARGS}
framework: cleanup conditional-indentations in Mk/ Run Tools/scripts/indent_make_if.pl on all of Mk. These white space changes contribute greatly to the readability of those files. As we have a version control system, finding out the reasons for the changes prior to these white space changes is still easily possible Differential Revision: https://reviews.freebsd.org/D35024 Reviewed by: portmgr (rene, bapt)
2022-04-24 12:00:20 +02:00
. endfor
. endif
Add USES=cargo to make creating ports of Rust applications easier Approved by: mat (mentor) Reviewed by: dumbbell, mat Differential Revision: https://reviews.freebsd.org/D11162
2017-06-21 18:22:32 +02:00
framework: cleanup conditional-indentations in Mk/ Run Tools/scripts/indent_make_if.pl on all of Mk. These white space changes contribute greatly to the readability of those files. As we have a version control system, finding out the reasons for the changes prior to these white space changes is still easily possible Differential Revision: https://reviews.freebsd.org/D35024 Reviewed by: portmgr (rene, bapt)
2022-04-24 12:00:20 +02:00
. if !target(do-test) && ${CARGO_TEST:tl} == "yes"
Add USES=cargo to make creating ports of Rust applications easier Approved by: mat (mentor) Reviewed by: dumbbell, mat Differential Revision: https://reviews.freebsd.org/D11162
2017-06-21 18:22:32 +02:00
do-test:
@${CARGO_CARGO_RUN} test \
--manifest-path ${CARGO_CARGOTOML} \
--verbose \
Mk/Uses/cargo.mk: Make build scripts more verbose Build scripts might build bundled libraries but non-error output is hiddden by cargo. Given a crate with large enough bundled library (looking at you rusty_v8) the build just sits there in silence forever and you do not know what is happening or if anything is happening at all. This also makes Poudriere build logs less useful. Pass an additional --verbose to cargo to get more noisy output. https://doc.rust-lang.org/cargo/reference/build-scripts.html#outputs-of-the-build-script
2021-04-13 09:01:20 +02:00
--verbose \
Add USES=cargo to make creating ports of Rust applications easier Approved by: mat (mentor) Reviewed by: dumbbell, mat Differential Revision: https://reviews.freebsd.org/D11162
2017-06-21 18:22:32 +02:00
${CARGO_TEST_ARGS}
framework: cleanup conditional-indentations in Mk/ Run Tools/scripts/indent_make_if.pl on all of Mk. These white space changes contribute greatly to the readability of those files. As we have a version control system, finding out the reasons for the changes prior to these white space changes is still easily possible Differential Revision: https://reviews.freebsd.org/D35024 Reviewed by: portmgr (rene, bapt)
2022-04-24 12:00:20 +02:00
. endif
Add USES=cargo to make creating ports of Rust applications easier Approved by: mat (mentor) Reviewed by: dumbbell, mat Differential Revision: https://reviews.freebsd.org/D11162
2017-06-21 18:22:32 +02:00
#
# Helper targets for port maintainers
#
Uses/cargo: Add cargo-audit maintainer target It wraps security/cargo-audit and generates a report about vulnerable crates. Many ports have those. Based on D17448.
2022-04-15 13:51:18 +02:00
# cargo-audit generates a vulnerability report using
# security/cargo-audit based on the crates in Cargo.lock.
cargo-audit: configure
@if ! type cargo-audit > /dev/null 2>&1; then \
${ECHO_MSG} "===> Please install \"security/cargo-audit\""; exit 1; \
fi
@${ECHO_MSG} "===> Checking for vulnerable crates"
@${CARGO} audit --file ${CARGO_CARGOLOCK}
Mk/Uses/cargo.mk: Let 'cargo-crates' generate Cargo.lock if it does not exist This will make maintaining ports easier when upstream does not provide a Cargo.lock on its own. It uses the crate registry and will output the newest crate versions available based on the restrictions in Cargo.toml. As such subsequent runs of `make cargo-crates` might not generate the same output. Upstream should still be encouraged to provide Cargo.lock if possible. Requested by: mat Differential Revision: https://reviews.freebsd.org/D17003
2018-09-04 09:26:02 +02:00
# cargo-crates will output the crates list from Cargo.lock. If there
# is no Cargo.lock for some reason, try and generate it first.
Uses/cargo: Add a cargo-crates-merge maintainer target It is the in-place version of cargo-crates and updates CARGO_CRATES in the port's Makefile for you via portedit from ports-mgmt/portfmt.
2021-10-26 13:01:27 +02:00
cargo-crates: cargo-crates-generate-lockfile
@${_CARGO_AWK} ${SCRIPTSDIR}/cargo-crates.awk ${CARGO_CARGOLOCK}
# cargo-crates-generate-lockfile will try to generate a Cargo.lock file
# if it does not exist.
cargo-crates-generate-lockfile: extract
Mk/Uses/cargo.mk: Let 'cargo-crates' generate Cargo.lock if it does not exist This will make maintaining ports easier when upstream does not provide a Cargo.lock on its own. It uses the crate registry and will output the newest crate versions available based on the restrictions in Cargo.toml. As such subsequent runs of `make cargo-crates` might not generate the same output. Upstream should still be encouraged to provide Cargo.lock if possible. Requested by: mat Differential Revision: https://reviews.freebsd.org/D17003
2018-09-04 09:26:02 +02:00
@if [ ! -r "${CARGO_CARGOLOCK}" ]; then \
${ECHO_MSG} "===> ${CARGO_CARGOLOCK} not found. Trying to generate it..."; \
Uses/cargo: Rework git source support based on patch-in-config sections Git sources from `Cargo.lock` are added to `CARGO_CRATES` through the normal mechanism of `make cargo-crates` by the porter. They are used to populate `MASTER_SITES`, `DISTFILES` with static git-archive(1) tarballs a la `USE_GITHUB`, `USE_GITLAB`. In the configure phase we generate `[patch]` sections in the config file which will cause `cargo update` to auto-update `Cargo.lock` to point to the appropriate extraction directories. Normally `cargo update` would connect to the network to update all Git sources but since rust-1.55.0 our cargo has been patched to skip this when `CARGO_FREEBSD_PORTS_SKIP_GIT_UPDATE` is set in the environment. This replaces the old `CARGO_USE_GITHUB`, `CARGO_USE_GITLAB` hacks where this was done by editing all `Cargo.toml` with sed(1) calls. Additionally, we try to automatically infer the individiual crate sub-directories inside the Git sources based on `package.name` in `Cargo.toml` to remove the need for `CARGO_GIT_SUBDIR`. USES=cargo also now sets `WRKSRC_crate_$name` for each crate to point to the crate extraction directories. PR: 256581 Reviewed by: jbeich
2021-09-07 16:08:46 +02:00
cd ${WRKSRC}; ${_CARGO_RUN} generate-lockfile \
Mk/Uses/cargo.mk: Let 'cargo-crates' generate Cargo.lock if it does not exist This will make maintaining ports easier when upstream does not provide a Cargo.lock on its own. It uses the crate registry and will output the newest crate versions available based on the restrictions in Cargo.toml. As such subsequent runs of `make cargo-crates` might not generate the same output. Upstream should still be encouraged to provide Cargo.lock if possible. Requested by: mat Differential Revision: https://reviews.freebsd.org/D17003
2018-09-04 09:26:02 +02:00
--manifest-path ${CARGO_CARGOTOML} \
--verbose; \
fi
Add USES=cargo to make creating ports of Rust applications easier Approved by: mat (mentor) Reviewed by: dumbbell, mat Differential Revision: https://reviews.freebsd.org/D11162
2017-06-21 18:22:32 +02:00
# cargo-crates-licenses will try to grab license information from
# all downloaded crates.
cargo-crates-licenses: configure
@${FIND} ${CARGO_VENDOR_DIR} -name 'Cargo.toml' -maxdepth 2 \
-exec ${GREP} -H '^license' {} \; \
| ${SED} \
-e 's@^${CARGO_VENDOR_DIR}/@@' \
-e 's@/Cargo.toml:license.*= *"@|@' \
Mk/Uses/cargo.mk: Encode more crate build dependencies - Add build/lib dependencies, environment variables to ports using the backtrace-sys, freetype-sys, gettext-sys, onig_sys, thrussh-libsodium crates instead of doing this individually for every port. - Add a DEV_WARNING when using libc versions < 0.2.37 to prevent instability of Rust applications on 12.0-CURRENT [1] - Sort cargo-crates-licenses output Reviewed by: pizzamig, jbeich [1] Differential Revision: https://reviews.freebsd.org/D15463
2018-06-14 11:56:02 +02:00
-e 's@"$$@@g' | sort | /usr/bin/column -t -s '|'
Uses/cargo: Add a cargo-crates-merge maintainer target It is the in-place version of cargo-crates and updates CARGO_CRATES in the port's Makefile for you via portedit from ports-mgmt/portfmt.
2021-10-26 13:01:27 +02:00
# cargo-crates-merge will in-place update CARGO_CRATES in the port
# based on the crates list from Cargo.lock. If there is no Cargo.lock
# for some reason, try and generate it first.
Uses/cargo: Try to simplify cargo-crates-merge usage Always start with a clean work directory state and end with one too. Automatically run makesum too.
2022-04-15 10:45:54 +02:00
cargo-crates-merge:
Uses/cargo: Add a cargo-crates-merge maintainer target It is the in-place version of cargo-crates and updates CARGO_CRATES in the port's Makefile for you via portedit from ports-mgmt/portfmt.
2021-10-26 13:01:27 +02:00
@if ! type portedit > /dev/null 2>&1; then \
${ECHO_MSG} "===> Please install \"ports-mgmt/portfmt\""; exit 1; \
fi
Uses/cargo: Try to simplify cargo-crates-merge usage Always start with a clean work directory state and end with one too. Automatically run makesum too.
2022-04-15 10:45:54 +02:00
@${MAKE} clean cargo-crates-generate-lockfile
Uses/cargo: Add a cargo-crates-merge maintainer target It is the in-place version of cargo-crates and updates CARGO_CRATES in the port's Makefile for you via portedit from ports-mgmt/portfmt.
2021-10-26 13:01:27 +02:00
@f="${MASTERDIR}/Makefile"; [ -r "${MASTERDIR}/Makefile.crates" ] && f="${MASTERDIR}/Makefile.crates"; \
${_CARGO_AWK} ${SCRIPTSDIR}/cargo-crates.awk ${CARGO_CARGOLOCK} | \
portedit merge -i $$f; \
Uses/cargo: Try to simplify cargo-crates-merge usage Always start with a clean work directory state and end with one too. Automatically run makesum too.
2022-04-15 10:45:54 +02:00
${MAKE} clean makesum; \
${ECHO_MSG} "${DISTINFO_FILE} and CARGO_CRATES in $$f were updated";
Uses/cargo: Add a cargo-crates-merge maintainer target It is the in-place version of cargo-crates and updates CARGO_CRATES in the port's Makefile for you via portedit from ports-mgmt/portfmt.
2021-10-26 13:01:27 +02:00
Add USES=cargo to make creating ports of Rust applications easier Approved by: mat (mentor) Reviewed by: dumbbell, mat Differential Revision: https://reviews.freebsd.org/D11162
2017-06-21 18:22:32 +02:00
.endif
Reference in a new issue Copy permalink