
Thought I'd try packaging up an OpenDX wrapper using the new Distutils.
I need to get a -I path on the cc command line (and a -L/-rpath on the linker line). Is there a way to do this with the current version (portably or UNIX-specific; either one)?
I gather from the docs that the Setup Configuration File will eventually take care of this third-party software path configuration. I'm looking for a stopgap until then.
If not, is there a "!shell <command>" backdoor that can be used in the meantime?
Thanks,
Randall
-- Randall Hopper (mailto:aa8vb@yahoo.com) EPA Scientific Visualization Center US EPA MD/24 ERC-1A; RTP, NC 27711

On 02 June 2000, Randall Hopper said:
I need to get a -I path on the cc command line (and a -L/-rpath on the linker line). Is there a way to do this with the current version (portably or UNIX-specific; either one)?
Just put 'include_dirs' and 'library_dirs' elements in dictionaries at the bottom of the 'ext_modules' list-of-tuples-of-dictionaries. Eg. see examples/mxdatetime_setup.py:
ext_modules = [('DateTime.mxDateTime.mxDateTime', { 'sources': ['mxDateTime/mxDateTime.c'], 'include_dirs': ['mxDateTime'], } )]
'library_dirs' is similar.
Note that this is a lot less hairy in the current CVS code:
ext_modules = [Extension('DateTime.mxDateTime.mxDateTime', ['mxDateTime/mxDateTime.c'], include_dirs=['mxDateTime'] ) ] And if this is a setting that users have to override (eg. "specify the include directories for libfoo here"), the config file code in the current CVS will handly this nicely.
Right, enough screwing around -- definitely time to write some docs and tests and get 0.9 out the door.
Greg

Greg Ward: |On 02 June 2000, Randall Hopper said: |> I need to get a -I path on the cc command line (and a -L/-rpath on the |> linker line). Is there a way to do this with the current version (portably |> or UNIX-specific; either one)? | |Just put 'include_dirs' and 'library_dirs' elements in dictionaries at |the bottom of the 'ext_modules' list-of-tuples-of-dictionaries. Eg. see |examples/mxdatetime_setup.py: | | ext_modules = [('DateTime.mxDateTime.mxDateTime', | { 'sources': ['mxDateTime/mxDateTime.c'], | 'include_dirs': ['mxDateTime'], | } | )] | |'library_dirs' is similar.
Thanks. I've got it packaged and ready to ship with Distutils 15.3.
I'll try it on a few folks tonight and see how they do.

On 05 June 2000, Randall Hopper said:
Thanks. I've got it packaged and ready to ship with Distutils 15.3.
Wow, great! I think this is the first recorded *forward*-looking time machine in the Python community; I'm glad to hear the Distutils makes it as far as version 15.3. How many years into the future did you have to travel?
Greg
PS. the current Distutils release is 0.8.2; 0.9 will be the next release. ;-)

Greg Ward: |On 05 June 2000, Randall Hopper said: |> Thanks. I've got it packaged and ready to ship with Distutils 15.3. | |Wow, great! I think this is the first recorded *forward*-looking time |machine in the Python community; I'm glad to hear the Distutils makes it |as far as version 15.3. How many years into the future did you have to |travel?
Oops. Oh yeah, I meant to do that ;-)
That's Numeric's version number. Distutils 0.8.2 is what I used.
participants (2)
-
Greg Ward
-
Randall Hopper