ProgrammingThis forum is for all programming questions.
The question does not have to be directly related to Linux and any language is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
I get the dreaded "No such file or directory" error, even *WITH* the files installed. Why? Are there any variables I have to set or something?
I don't know which system you're using and I don't know which version of GTK you're using, but you could try to include this one (or similar) into your compilation:
I don't know which system you're using and I don't know which version of GTK you're using, but you could try to include this one (or similar) into your compilation:
BUT, you should also find this in a _good_ GTK tutorial for Linux :-)
Andi
I'm using Ubuntu 10.10 Alpha 1 with GNOME 2.31, and that post really helped me. Thank you. So much for Sergei Stashenko's blunt comment telling me to go take a hike.
I'm using Ubuntu 10.10 Alpha 1 with GNOME 2.31, and that post really helped me. Thank you. So much for Sergei Stashenko's blunt comment telling me to go take a hike.
I.e. I suggested you to study the fundamental issues, and ForzaItalia2006 gave you a particular command line which, of course, in the end uses the fundamental features you are supposed to know. Unless you know/understand the fundamental issues, you are destined to face similar problems in the future.
By the way, read about 'pkg-config' - to know why/what for it was invented. Its existence is due to a bunch of similar fundamental issues involved is SW development.
I.e. I suggested you to study the fundamental issues, and ForzaItalia2006 gave you a particular command line which, of course, in the end uses the fundamental features you are supposed to know. Unless you know/understand the fundamental issues, you are destined to face similar problems in the future.
Yes, you're generally right and it is always beneficial to study the fundamental details, but sometimes the OPs aren't immediately interested in the details, but just want to get a simple program working.
And IF an OP is really interested in the details, he/she will research about pkg-config, the features which it provides and possibly finally what compiler options like -l<x> or -I<x> mean.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.