Add MANIFEST. In file besides setup. Py with following contents.
Add MANIFEST. In file besides setup. Py with following contents: graft relative/path/to/directory/of/your/headers.
I don't want to install the headers; they should only be used as input for the compiler. Only the pyd file produced by the compiler should be installed. – user763305 Jul 14 at 7:28 No, whey won't be installed.
MANIFEST is not for installation, but for source distribution (setup. Py sdist). – Jacek Konieczny Jul 18 at 11:38 Great!
But I'm surprised that you need a MANIFEST at all to do something this simple. – user763305 Jul 18 at 12:17 Gah, I can't believe I forgot about MANIFEST.in. >.
In – Éric Araujo Oct 7 at 17:19.
If I remember right you should only need to specify the source files and it's supposed to find/use the headers. In the setup-tools manual, I see something about this I believe. "For example, if your extension requires header files in the include directory under your distribution root, use the include_dirs option" Extension('foo', 'foo.
C', include_dirs='include') docs.python.org/distutils/setupscript.ht....
I tried that. It did not find the headers. – user763305 Jul 9 at 8:25 I edited my question, see if it works.
:) – John Doe Jul 9 at 8:29 Tried ext_modules = Extension('Foo', glob('Foo/*. Cpp'), include_dirs='Foo'). Does not work; the header files are not added to the package.
– user763305 Jul 9 at 8:34 Have you tried the code in your questions example? It might work, at least I hope it will. :) I couldn't find anything else related to your problem in the manual; sorry.
:( – John Doe Jul 9 at 8:40.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.