|
From: | Hartmut Goebel |
Subject: | Re: Building hexyl (a rust app) without cargo, with antioxidant-build-system |
Date: | Wed, 6 Apr 2022 17:49:30 +0200 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.7.0 |
Am 05.04.22 um 18:10 schrieb Maxime Devos:
Some other improvements that weren't announced previously:
Wow! Impressive!I'd be eager to tr it with sequoia-openpgp. Please drop me a note when you think your work might be able to build that beast.
* Package definitions can request non-default features to be built anyway. A difference from cargo-build-system: features are set in the package of the rust crate, not the package using the rust crate.
How is this intended to work?Package 1 has features AAA (= default) and BBB. So a .rlib is build for each feature (package1-AAA.rlib, package1-BBB.rlib) Or will one need to define two guix packages (package1+aaa and package1+bbb) and make the build-system build the respective feature?
I personally would prefer the former. Thus package2 would pick up the pre-compiled rlib for the respective feature.
Rational: If there are more features to be combined, the number of packages to be build can a order of square. So defining all these packages becomes a burden quickly. This is a computer's job :-) The build-system could easily build all combinations. suffixing each rlib with a short hash over the feature names,
-- Regards Hartmut Goebel | Hartmut Goebel | h.goebel@crazy-compilers.com | | www.crazy-compilers.com | compilers which you thought are impossible |
[Prev in Thread] | Current Thread | [Next in Thread] |