> Of course I meant Cargo.lock, not Cargo.toml ... so I know what I
> have to search for, and this makes it a bit easier than the
> previous search.
See cargo workspaces:
https://github.com/rust-lang/libc/blob/master/Cargo.toml
https://github.com/rust-lang/rfcs/blob/master/text/1525-cargo-workspac
ng0 writes:
> David Craven writes:
>
>>> We run (or this is the default) cargo with `--bin`, which is
>>> necessary for everything which needs to be compiled and features
>>> a Cargo.toml.
>>
>> All crates have a Cargo.toml file. The interesting crates are the ones with
>> a Cargo.lock file.
>>
David Craven writes:
>> We run (or this is the default) cargo with `--bin`, which is
>> necessary for everything which needs to be compiled and features
>> a Cargo.toml.
>
> All crates have a Cargo.toml file. The interesting crates are the ones with
> a Cargo.lock file.
>
>> To "build" libraries,
> We run (or this is the default) cargo with `--bin`, which is
> necessary for everything which needs to be compiled and features
> a Cargo.toml.
All crates have a Cargo.toml file. The interesting crates are the ones with
a Cargo.lock file.
> To "build" libraries, we have to explicitly tell cargo
Hi,
I've got about 94 rust packages on my todo list for our
(secushare) current prototype version.
Today I assembled the full list of them and started with the
crate `libc`. This crate comes with no Cargo.toml file, where I
already am aware of the limitation of our cargo build-system.
Before I c
