| Guido van Rossum | 3caad8c | 1995-03-28 09:22:53 +0000 | [diff] [blame] | 1 | This directory show how to embed the Python interpreter in your own |
| 2 | application. The file demo.c shows you all that is needed in your C |
| 3 | code. |
| Guido van Rossum | 705d517 | 1994-10-08 19:30:50 +0000 | [diff] [blame] | 4 | |
| 5 | To build it, you may have to edit the Makefile: |
| 6 | |
| 7 | 1) set blddir to the directory where you built Python, if it isn't in |
| 8 | the source directory (../..) |
| 9 | |
| 10 | 2) change the variables that together define the list of libraries |
| 11 | (MODLIBS, LIBS, SYSLIBS) to link with, to match their definitions in |
| 12 | $(blddir)/Modules/Makefile |
| Guido van Rossum | 3559d1f | 2001-01-10 17:11:51 +0000 | [diff] [blame] | 13 | |
| 14 | An additional test program, loop.c, is used to experiment with memory |
| 15 | leakage caused by repeated initialization and finalization of the |
| 16 | interpreter. It can be build by saying "make loop" and tested with |
| 17 | "make looptest". Command line usage is "./loop <python-command>", |
| 18 | e.g. "./loop 'print 2+2'" should spit out an endless number of lines |
| 19 | containing the number 4. |