Message131303
| Author | pitrou |
|---|---|
| Recipients | amaury.forgeotdarc, benjamin.peterson, christian.heimes, eric.araujo, grahamd, loewis, ncoghlan, pitrou, python-dev, tarek, vstinner |
| Date | 2011-03-17.23:53:46 |
| SpamBayes Score | 3.835037e-07 |
| Marked as misclassified | No |
| Message-id | <1300406023.3710.18.camel@localhost.localdomain> |
| In-reply-to | <1300405001.13.0.817890664148.issue10914@psf.upfronthosting.co.za> |
| Content | |
|---|---|
> distutils sure knows how to build .o or .so files, but I don’t know > about standalone executables (because I don’t know how the .o end up > making an executable). If you want to try to do it, I would advise > you not to use the config command but rather a compiler object > directly. distutils.ccompiler.new_compiler() should give you an > instance of a subclass of distutils.ccompiler.CCompiler suitable for > your system, and then you can use help or the source to find what > methods to call. Well, config._link() seems to do what is needed here. If you think it is bad to rely on it, perhaps we should "inline" its code somehow in the test module. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2011-03-17 23:53:47 | pitrou | set | recipients: + pitrou, loewis, amaury.forgeotdarc, ncoghlan, vstinner, christian.heimes, benjamin.peterson, tarek, eric.araujo, grahamd, python-dev |
| 2011-03-17 23:53:46 | pitrou | link | issue10914 messages |
| 2011-03-17 23:53:46 | pitrou | create | |