Can anyone tell me where should/must I put the Python.h file for waf
to find that file when compiling Phoenix?
I got the Python.h file from the source code of Python 3.3.1 since I'm
compiling Phoenix with Python 3.3.1. I just don't know where exactly
should I put that file now. Any ideas?
I don't know where to put it but putting it in $PATH or in the same
directory as the build script could work
···
Am 10.04.2013 10:41, schrieb Boštjan Mejak:
Can anyone tell me where should/must I put the Python.h file for waf
to find that file when compiling Phoenix?
I got the Python.h file from the source code of Python 3.3.1 since I'm
compiling Phoenix with Python 3.3.1. I just don't know where exactly
should I put that file now. Any ideas?
Robin, can you tell where does that Python.h file belong?
He probably can’t tell you where your Python.h for your Python install should be without doing some googling on it (which you could do yourself, BTW), because you never copy and paste Python.h by hand. You always install it from somewhere. If your Python.h isn’t being found, your machine is probably not set up correctly for Python extension compilation, or more in general for Python development. If you’re on a Linux distro, it probably means you’re missing some packages.
Kevin
···
On Wed, Apr 10, 2013 at 11:00 AM, David python@dav1d.de wrote:
Am 10.04.2013 10:41, schrieb Boštjan Mejak:
Can anyone tell me where should/must I put the Python.h file for waf
to find that file when compiling Phoenix?
I got the Python.h file from the source code of Python 3.3.1 since I’m
compiling Phoenix with Python 3.3.1. I just don’t know where exactly
should I put that file now. Any ideas?
I don’t know where to put it but putting it in $PATH or in the same
directory as the build script could work
–
You received this message because you are subscribed to the Google Groups “wxPython-users” group.
Can anyone tell me where should/must I put the Python.h file for waf
to find that file when compiling Phoenix?
Again, why? If the Phoenix build is able to be successfully complete (which it does according to your other messages) despite the issue of waf's first attempt to find Python.h failing, then obviously its additional attempts were successful and you shouldn't worry about it. If you didn't already have Python.h somewhere that could be found by the compiler then none of the compiles in the Phoenix part of the build would succeed.
I got the Python.h file from the source code of Python 3.3.1 since I'm
compiling Phoenix with Python 3.3.1. I just don't know where exactly
should I put that file now. Any ideas?
It depends on your platform and where you got your python. If you build it yourself then it will have been installed along with the other python headers when you did a "make install". If you used packages from a .deb or .rpm package repository then there is likely a python*-dev package or similar that will install the headers. If you used an installer on Windows or Mac then the headers are already installed in a place they can be found.
On Wed, Apr 10, 2013 at 6:36 PM, Robin Dunn robin@alldunn.com wrote:
Boštjan Mejak wrote:
Can anyone tell me where should/must I put the Python.h file for waf
to find that file when compiling Phoenix?
Again, why? If the Phoenix build is able to be successfully complete (which it does according to your other messages) despite the issue of waf’s first attempt to find Python.h failing, then obviously its additional attempts were successful and you shouldn’t worry about it. If you didn’t already have Python.h somewhere that could be found by the compiler then none of the compiles in the Phoenix part of the build would succeed.
I got the Python.h file from the source code of Python 3.3.1 since I’m
compiling Phoenix with Python 3.3.1. I just don’t know where exactly
should I put that file now. Any ideas?
It depends on your platform and where you got your python. If you build it yourself then it will have been installed along with the other python headers when you did a “make install”. If you used packages from a .deb or .rpm package repository then there is likely a python*-dev package or similar that will install the headers. If you used an installer on Windows or Mac then the headers are already installed in a place they can be found.
On Wed, Apr 10, 2013 at 09:32:22PM +0200, Boštjan Mejak wrote:
On Wed, Apr 10, 2013 at 6:36 PM, Robin Dunn <robin@alldunn.com> wrote:
> Boštjan Mejak wrote:
>
>> Can anyone tell me where should/must I put the Python.h file for waf
>> to find that file when compiling Phoenix?
>>
>
> Again, why? If the Phoenix build is able to be successfully complete
> (which it does according to your other messages) despite the issue of waf's
> first attempt to find Python.h failing, then obviously its additional
> attempts were successful and you shouldn't worry about it. If you didn't
> already have Python.h somewhere that could be found by the compiler then
> none of the compiles in the Phoenix part of the build would succeed.
>
>
>
>> I got the Python.h file from the source code of Python 3.3.1 since I'm
>> compiling Phoenix with Python 3.3.1. I just don't know where exactly
>> should I put that file now. Any ideas?
>>
>>
> It depends on your platform and where you got your python. If you build
> it yourself then it will have been installed along with the other python
> headers when you did a "make install". If you used packages from a .deb or
> .rpm package repository then there is likely a python*-dev package or
> similar that will install the headers. If you used an installer on Windows
> or Mac then the headers are already installed in a place they can be found.
>
> --
> Robin Dunn
> Software Craftsman
> http://wxPython.org
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "wxPython-users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to wxpython-users+unsubscribe@**googlegroups.com<wxpython-users%2Bunsubscribe@googlegroups.com>
> .
> For more options, visit https://groups.google.com/**groups/opt_out<https://groups.google.com/groups/opt_out>
> .
>
>
>
--
You received this message because you are subscribed to the Google Groups "wxPython-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to wxpython-users+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
I've been reading this list for nearly 10 years, and I have never seen a
post anywhere near as rude as this. It is particularly disturbing because
Kevin is obviously a very competent developer, and even more important, is
always willing to offer his unpaid help to users who ask. Shame on
you, Boštjan.
···
On Wed, Apr 10, 2013 at 3:32 PM, Boštjan Mejak <mejak.bost@gmail.com> wrote: