How to package python extensions that need a special preprocessor?

2015-09-03 Thread David Howells
Hi, I'm trying to package a python module that has a C extension that has a special preprocessor that turns protocol definition files into C. Currently, I have a makefile that calls the rxgen program[*]: ./rxgen/rxgen.pl rpc-api/* which produces four C files (afs_xg.[ch] and afs_py.[ch]

Re: How to package python extensions that need a special preprocessor?

2015-09-03 Thread Guy Streeter
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 09/03/2015 05:36 AM, David Howells wrote: > Hi, > > I'm trying to package a python module that has a C extension that has a > special preprocessor that turns protocol definition files into C. > > Currently, I have a makefile that calls the rxgen

Re: How to package python extensions that need a special preprocessor?

2015-09-03 Thread David Howells
Guy Streeter wrote: > > I'm trying to package a python module that has a C extension that has a > > special preprocessor that turns protocol definition files into C. > ... > See the setup.py in this package: > > https://git.fedorahosted.org/cgit/python-libnuma.git/ > > It runs msgfmt on the pr

Re: How to package python extensions that need a special preprocessor?

2015-09-03 Thread Guy Streeter
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 09/03/2015 10:36 AM, David Howells wrote: > Guy Streeter wrote: > >>> I'm trying to package a python module that has a C extension that has >>> a special preprocessor that turns protocol definition files into C. >> ... See the setup.py in this pac

Re: How to package python extensions that need a special preprocessor?

2015-09-03 Thread David Howells
Guy Streeter wrote: > Do you just need to control the build order, so your preprocessor runs > first? Yes. > You can over-ride "build" to make that happen. Okay. > Or use something like > > ./setup.py build_prep build_ext build I'd rather not do that - I'd rather 'build' built everything.