It is expected that one would know how to properly add dependencies — and if they did not, they should go read the documentation (from the 'Docs' link at the top of the page).
I hate to be dismissive, but did you rtfm?
Shouldn't there be some continuity between the examples provided on the webpage and tfm?
There doesn't need to be any further instructions on the landing page, though. Again, that's what the docs are for.
So, neither the example on the page nor the documentation work.
How desperate should one be to want to use GTK? Is this some kind of an initiation?
PS. I can't reply to this thread any further.
I'll concede that I may be making a mistake copying and pasting things, but I've checked a few times. If the job of the documentation is to help, then it should address situations where people get stuck.
At this stage, the new gtk webpage feels akin to putting lipstick on a pig.
PPS. Seems like I can reply again.
I'm not sure if you're implicitly wanting us to diagnose your issue for you without providing any actual information, but seeing as I have no idea if you have GTK properly installed, the headers in the right place, or anything else like that, I can't help but be sceptical that the documentation isn't up to snuff.
So, I went to part of the GTK Project page where it provides examples on how to install GTK for Mac (https://www.gtk.org/docs/installations/macos/) and clicked on the installation script link under Getting Started. The installation script link is broken.
How do I actually run the code examples that you've provided?
For example, I started a new Cargo project and pasted the Rust example provided into my main.rs. It failed compilation. Should I have added a few dependencies to my Cargo.toml first? Should I have upgraded Rust first?
I upgraded Rust, btw. And added lines to my Cargo.toml. No bueno. Now, I have to go hunting elsewhere for answers.
A few extra lines of instruction would definitely save the thousands of developers who're bound to get stuck.