| Last change
 on this file since 404 was             2, checked in by Yuri Dario, 15 years ago | 
        
          | 
Initial import for vendor code.
 | 
        
          | 
              
Property                 svn:eol-style
 set to                 native | 
        
          | File size:
            822 bytes | 
      
      
| Line |  | 
|---|
| 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. | 
|---|
| 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 | 
|---|
| 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. | 
|---|
       
      
  Note:
 See   
TracBrowser
 for help on using the repository browser.