I've finally developed what I think is a general solution to the problem of building existing Windows programs with clang: https://github.com/russellw/wic Using this, I've managed to run attempted builds of Python, Ruby and Perl. Python 2.7 works - it generates a python.exe that at least passes a preliminary smoke test. Perl generates an executable that crashes partway through the build. I'll try to narrow it down further. Ruby fails with an error message at the configuration step. I'm trying to find out why; it might be something easily fixable. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20150710/13be146a/attachment.html>
This seems more relevant to cfe-dev. On Thu, Jul 9, 2015 at 5:54 PM Russell Wallace <russell.wallace at gmail.com> wrote:> I've finally developed what I think is a general solution to the problem > of building existing Windows programs with clang: > > https://github.com/russellw/wic > <https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_russellw_wic&d=AwMFaQ&c=8hUWFZcy2Z-Za5rBPlktOQ&r=Mfk2qtn1LTDThVkh6-oGglNfMADXfJdty4_bhmuhMHA&m=YcMBbXwHtljUfWVgVj2K7c0HnM4QQ2Sd4WtVqHO3j44&s=22Z4NBDsx6r8TP5ejuUidL-0utuXnYJD8d50OjYxKRo&e=> >You seem to be struggling with the need to name the binary 'cl.exe'. Last time I checked, we installed clang-cl.exe under that name in a specialized director specifically so you can use build systems relying on that name. -Chandler> > > Using this, I've managed to run attempted builds of Python, Ruby and Perl. > > Python 2.7 works - it generates a python.exe that at least passes a > preliminary smoke test. > > Perl generates an executable that crashes partway through the build. I'll > try to narrow it down further. > > Ruby fails with an error message at the configuration step. I'm trying to > find out why; it might be something easily fixable. > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20150710/104026e6/attachment.html>
On Fri, Jul 10, 2015 at 2:00 AM, Chandler Carruth <chandlerc at google.com> wrote:> This seems more relevant to cfe-dev. >Okay.> > You seem to be struggling with the need to name the binary 'cl.exe'. Last > time I checked, we installed clang-cl.exe under that name in a specialized > director specifically so you can use build systems relying on that name. >Right, but: 1. The existence of a binary named cl.exe isn't enough; depending on the circumstances, the build system may look specifically in the visual studio directory. Of course, you could do the rename/copy by hand, but it's better to have it automated, particularly since in practice there is a need to switch back and forth. 2. Python at least needs to have it switchable specifically for 32-bit or 64-bit builds. 3. wic also supplies the option -Wno-invalid-token-paste which is necessary for compatibility with the Microsoft preprocessor. I intend adding other options as needed. 4. Hopefully can also substitute calls to the llvm linke when that's ready for prime time. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20150710/ccae4f66/attachment.html>