Re: Building hexyl (a rust app) without cargo, with antioxidant-build-system

Efraim Flashner schreef op ma 30-05-2022 om 11:23 [+0300]: > Something that might help with that would be to also include the > source of the crate somewhere in the output. Then at the worst we > could just put the rust inputs of librsvg as regular inputs and let > librsvg do its own special build

Re: Building hexyl (a rust app) without cargo, with antioxidant-build-system

On Mon, 30 May 2022 11:23:21 +0300 Efraim Flashner wrote: > On Sat, Apr 02, 2022 at 05:18:55PM +0200, Maxime Devos wrote: > > Hi, > > > > antioxidant-build-system can now be used for some ‘real’ software > > -- it compiles 'hexyl'. To test, download > >

Re: Building hexyl (a rust app) without cargo, with antioxidant-build-system

On Sat, Apr 02, 2022 at 05:18:55PM +0200, Maxime Devos wrote: > Hi, > > antioxidant-build-system can now be used for some ‘real’ software -- it > compiles 'hexyl'. To test, download > (commit: > d09fd93750ac6d77e0c85623286b45cf5c3b055b) and

Re: Building hexyl (a rust app) without cargo, with antioxidant-build-system

Hartmut Goebel schreef op wo 06-04-2022 om 17:49 [+0200]: > [...] > >     * 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

Re: Building hexyl (a rust app) without cargo, with antioxidant-build-system

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-def

Re: Building hexyl (a rust app) without cargo, with antioxidant-build-system

raingloom schreef op wo 06-04-2022 om 00:28 [+0200]: > I'm also a bit worried with the trend of Guix trying to duplicate > functionality already present in language package managers and config > file formats. It creates a two-sources-of-truth situation. For service configurations, there is only on

Re: Building hexyl (a rust app) without cargo, with antioxidant-build-system

On Mon, 04 Apr 2022 11:26:45 +0200 Maxime Devos wrote: > Brendan Tildesley schreef op ma 04-04-2022 om 15:10 [+1000]: > >  I would have called it cargone. > >   > >  Do you believe sidestepping cargo all together like this is a good > > long term strategy?  In particular that importing packages w

Re: Building hexyl (a rust app) without cargo, with antioxidant-build-system

Maxime Devos schreef op za 02-04-2022 om 17:18 [+0200]: >   * makes a few assumptions on the source layout (can be fixed >     by using more info from Cargo.toml) This has now been partially resolved. It now looks in Cargo.toml to determine where Rusts's equivalent of 'configure' (build.rs) is lo

Re: Building hexyl (a rust app) without cargo, with antioxidant-build-system

Brendan Tildesley schreef op ma 04-04-2022 om 15:10 [+1000]: >  I would have called it cargone. >   >  Do you believe sidestepping cargo all together like this is a good > long term strategy?  In particular that importing packages will still > be easy.  The package definitions look almost the same

Building hexyl (a rust app) without cargo, with antioxidant-build-system

I would have called it car/gone./ Do you believe sidestepping cargo all together like this is a good long term strategy? In particular that importing packages will still be easy.

Building hexyl (a rust app) without cargo, with antioxidant-build-system

Hi, antioxidant-build-system can now be used for some ‘real’ software -- it compiles 'hexyl'. To test, download (commit: d09fd93750ac6d77e0c85623286b45cf5c3b055b) and run "guix build -L . -f guix.scm" and then $ cat guix.scm | /gnu/store/[