Changes between Version 1 and Version 2 of PyMill


Ignore:
Timestamp:
04/03/08 15:35:53 (6 years ago)
Author:
ArcRiley
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • PyMill

    v1 v2  
    1616  Extension( 
    1717    name         = 'bodies', 
    18     mill_sources = ( 
     18    sources = ( 
    1919      'src/bodies/Body.pxi', 
    2020      'src/bodies/Camera.pxi', 
     
    3131}}} 
    3232 
    33 In the above, the mill_sources dictates which files will be compiled, which are appended to the Extension's sources= regardless of whether they're regenerated.  Since .c generation is internal we can continue having one .c per extension right now and migrate to one .c per source file later (this will make debugging easier). 
     33In the above, the sources dictates which files will be compiled, which the processed .c's are appended to the Extension's sources= regardless of whether they're regenerated.  Since .c generation is internal we can continue having one .c per extension right now and migrate to one .c per source file later (this will make debugging easier). 
    3434 
    3535Note that this data obsoletes about 100 lines of setup.py which checks file last modified dates; a more robust checking (only regenerating what's needed when something changes) could even be implemented internally to PyMill. 
     
    3939 
    4040Source would continue to be laid out just as it is now, or really in any fashion a project using PyMill prefers, but without the need for all the .pyx files which do nothing but include .pxi files, and eventually without the need for .pxd files either. 
     41 
     42We'll migrate .pxi files (which Pyrex doesn't care about the extension of) to '''.pym''' (PyMill) during this process.