Development

[todoooo]

Add castxml support

[bradking]

Cc: @dlrdave

[dlrdave]

I have been trying to get to reviewing this... I have a build of https://github.com/CastXML/CastXMLSuperbuild going on my Mac right now, and will get a Windows one going too. I need that to succeed first or to install a pre-built binary of castxml before I can get this one verified on Windows. I'll keep plugging away at it in my spare time, but it might still take me a couple more weeks before I can effectively review things here.

[todoooo]

Hi David If you're building on Windows with VS2017, you'll need to build clang 5.0. The super build uses clang 3.8. Also the latest binary of castxml is 6 months old (last time I checked). It's painful. I know! Todd On 3 Nov 2017 12:40 p.m., "David Cole" <[email protected]> wrote: I have been trying to get to reviewing this... I have a build of https://github.com/CastXML/CastXMLSuperbuild going on my Mac right now, and will get a Windows one going too. I need that to succeed first or to install a pre-built binary of castxml before I can get this one verified on Windows. I'll keep plugging away at it in my spare time, but it might still take me a couple more weeks before I can effectively review things here. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#1 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AObwKXQ234f3uB9_k-v5h6Q99fcXTP3Rks5sylLrgaJpZM4P2One> .

[dlrdave]

Thanks for the info. Any particular version of python I need for the underlying build of llvm to work? (It errored out with "needs python" but doesn't say anything about 2 or 3, or min version...)

[dlrdave]

I've got VS 2013 installed on most of my Windows machines. Was intending to start with that, and then work up to 2017 on one machine where I can experiment.

[todoooo]

I used python 2.7 I also had lots of problems building llvm in VS2017. If you use BUILD_ALL the compiler keeps starting exes until the system runs out of ram. Stupid. Todd On 3 Nov 2017 1:16 p.m., "David Cole" <[email protected]> wrote: Thanks for the info. Any particular version of python I need for the underlying build of llvm to work? (It errored out with "needs python" but doesn't say anything about 2 or 3, or min version...) — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#1 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AObwKR1eSUbLJ9OhnFthgKIxKYptHQG1ks5syltpgaJpZM4P2One> .

[todoooo]

In that case use the superbuild to compile llvm and then get the latest castxml from git and build it against those DLLs.

…

On 3 Nov 2017 1:17 p.m., "David Cole" ***@***.***> wrote: I've got VS 2013 installed on most of my Windows machines. Was intending to start with that, and then work up to 2017 on one machine where I can experiment. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#1 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AObwKTY4GWEFB9crhzPBT64KqReucldKks5syludgaJpZM4P2One> .

[dlrdave]

OK, one of my Windows machines had python 2.7 on it already, and I got the CastXMLSuperbuild to work. Then, I got this branch of mummy to build using that castxml.exe on my VS 2013 install. Then, after "sn -Vr *,995c7fb9db2c1b44" to bypass the strong name validation, all the mummy tests passed, too! So... making progress... on my way to VS 2017 next.

[todoooo]

You will need the latest castxml from git to build with VS2017. However building with VS2017 is not a necessity. The main aim was to eliminate gccxml in order to avoid needing VS2008 and MSVC10. If you've got it building on VS2013 without issues, that's great.

…

On 4 Nov 2017 12:50 a.m., "David Cole" ***@***.***> wrote: OK, one of my Windows machines had python 2.7 on it already, and I got the CastXMLSuperbuild to work. Then, I got this branch of mummy to build using that castxml.exe on my VS 2013 install. Then, after "sn -Vr *,995c7fb9db2c1b44" to bypass the strong name validation, all the mummy tests passed, too! So... making progress... on my way to VS 2017 next. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#1 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AObwKWOeXAsFwEz3FeVNs9GU1LEAeJNXks5syv33gaJpZM4P2One> .