The package in that repo is a workspace with a virtual manifest.
In the root Cargo.toml file, members is set to crates/ and that directory in the repo is where you'll find the crates that are part of the workspace (excluding the ones listed under exclude in the root Cargo.toml)
Luckily, cargo just needs the git URL and will search for the package within the repo (docs).
In particular, different packages can come from the same git repo
have you spotted a direct way to connect to a rdp server in a lightweight way, i will implement something more featured after, but i just need a function that returns a result for a given username, password, ip and optionally a domain. i mean ill find out, but your opinion will help out alot
It's a complicated protocol, but I do sympathise with your struggle.
It looks like you've found a really good rust implementation! They seem to be actively working on it and documentation for end users is still lacking. I don't blame them here, good documentation takes time.
It's huge, but focus on the connect function. They've had to write it using lower level building blocks, but you can copy it. They use a similar function, but async, in the client crate. So I really do think this is just the boilerplate needed to connect using ironrdp at this current time.
I don't think there exists the high level of abstraction that you're after in ironrdp yet, but I wouldn't disregard the whole thing because of that.