This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author steve.dower
Recipients Buraddin Ibn-Karlo, docs@python, paul.moore, steve.dower, tim.golden, zach.ware
Date 2016-03-25.17:33:55
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1458927236.14.0.715075869102.issue26629@psf.upfronthosting.co.za>
In-reply-to
Content
(Obligatory recommendation that you use Cython rather than ctypes, especially if you're going to require your users to have a compiler handy - in general this isn't recommended on Windows at all; make sure you distribute wheels if you want to make your users' lives easiest.)

I haven't tested this, but I believe you want to specify your libraries with the `libraries` parameter, not the `extensions` parameter:

LIBRARIES = [
    ('my_lib', {'sources': ['my_lib.c'], 'include_dirs': ['dirs', 'if', 'you', 'want'], 'macros': ['DEFINES', 'IF', 'YOU', 'WANT']})
]

setup(
    ...
    libraries=LIBRARIES,
    ...
)

Then you need to ensure build_clib is run to produce it. I'd imagine that will just happen, but I could be wrong.

Again, I haven't tried this myself, but it seems to be the right way to build a regular library.
History
Date User Action Args
2016-03-25 17:33:56steve.dowersetrecipients: + steve.dower, paul.moore, tim.golden, docs@python, zach.ware, Buraddin Ibn-Karlo
2016-03-25 17:33:56steve.dowersetmessageid: <1458927236.14.0.715075869102.issue26629@psf.upfronthosting.co.za>
2016-03-25 17:33:56steve.dowerlinkissue26629 messages
2016-03-25 17:33:55steve.dowercreate