jsradley
April 6th, 2005, 02:24 PM
Hi,
I have apt-get build-essentials, and have gcc working with the standard Helloworld.c program.
My problem is with #Includes for other packages.
For example, take Python. I have apt-get the Python Dev package, and can see the Python.h is located in /usr/include/python2.4/Python.h (from memory as I am in my lunch hr at work!)
If I add #include <Python.h> to hello.c, the compiler can't find it.
So what is done to tell the compiler where all the includes are?
Do I create my own Environment variable, or is their a built in solution that I haven't done or found yet.
Thanks
John
I have apt-get build-essentials, and have gcc working with the standard Helloworld.c program.
My problem is with #Includes for other packages.
For example, take Python. I have apt-get the Python Dev package, and can see the Python.h is located in /usr/include/python2.4/Python.h (from memory as I am in my lunch hr at work!)
If I add #include <Python.h> to hello.c, the compiler can't find it.
So what is done to tell the compiler where all the includes are?
Do I create my own Environment variable, or is their a built in solution that I haven't done or found yet.
Thanks
John