Re: Any actively maintained qt bindings for D?
On Wednesday, 17 February 2016 at 21:20:09 UTC, Jeremy DeHaan wrote: On Wednesday, 17 February 2016 at 20:56:27 UTC, Rishub Nagpal wrote: Qtd hasn't been updated in 3 years Does anyone know of anactively maintained qt library? I think QML bindings exists, but as far as I know direct Qt bindings don't exist/aren't updated. I want to do a GSoC proposal for direct bindings to Qt, though. I have a lot of ideas for doing a binding to Qt proper, but the only way I can do it is if I have time. Time holds us all back :P
Any actively maintained qt bindings for D?
Qtd hasn't been updated in 3 years Does anyone know of anactively maintained qt library?
Re: Situation with D on iOS, Android, and WP8?
On Tuesday, 17 March 2015 at 07:12:07 UTC, Mitchell wrote: Hi Mitchell - For iOS, if you are willing to build the LLVM + LDC compiler chain, then please try: https://github.com/smolt/ldc-iphone-dev The readme lists the current state of things. You can build and run phobos hello world, and much more. I am trying to decide weather to cleanup and post more complicated app examples or push ios branch changes into ldc and D-Programming-Language git repos. Lately I've been doing the later. That looks awesome. I really hope iOS and Android support make it into LDC, that would make picking the language for my next cross platform app very easy indeed :) We had a discussion about it earlier this month http://forum.dlang.org/thread/qnxxwaezsrlhqlpwu...@forum.dlang.org I don't know much about LLVM specifics but if you know about LLVM/LDC internals, we can collaborate on the Android side.
Re: What is the state of D with Android/iOS
On Wednesday, 25 February 2015 at 08:04:02 UTC, Joakim wrote: On Tuesday, 24 February 2015 at 21:20:24 UTC, Rishub Nagpal wrote: On Tuesday, 24 February 2015 at 19:34:15 UTC, Joakim wrote: I need to patch llvm in a similar way to that dmd PR, so that Android/ARM can use the same scheme. It appears that Dan did something similar with his patched llvm for iOS. As for your linked Android patches, that might be possible but would be pointless unless you are only deploying to a device you patched the OS for. Better to patch llvm to support the same TLS scheme used for Android/x86. Interesting. A few others and I were talking about getting Android/ARM to function with LDC today. I'll be sure to keep up to date with your work! The remaining piece is to insert the correct function call to ___tls_get_addr when TLS variables are accessed, ie the equivalent to this patch for dmd's backend needs to be created for llvm: https://github.com/joakim-noah/dmd/commit/477f52cffb0d8bd1a698dd33ad7e2e66d9fa62ca#diff-d427199c5cd504da634c0c42fc2b3371 I've been putting off looking into llvm's internals enough to write that for a while now. If you or anybody else knows llvm better, feel free to take it. The remaining changes needed are in this small patch for llvm: https://gist.github.com/joakim-noah/1fb23fba1ba5b7e87e1a Why exactly do we need to insert that TLS function call? Shouldn't Android/ARM follow the normal ELF logic? I am not really sure what Dan Olsen did here: https://github.com/smolt/llvm/commit/42c2d7057b62454bb466abe8d146dd3c717e2cc5 Is he creating a iOS TLS ABI? I have spent the last week doing heavy research, and I am not sure if I really understand the problem Do you have any references or documented code I can read to better understand what exactly is going on?
Re: What is the state of D with Android/iOS
On Wednesday, 25 February 2015 at 08:04:02 UTC, Joakim wrote: On Tuesday, 24 February 2015 at 21:20:24 UTC, Rishub Nagpal wrote: On Tuesday, 24 February 2015 at 19:34:15 UTC, Joakim wrote: I need to patch llvm in a similar way to that dmd PR, so that Android/ARM can use the same scheme. It appears that Dan did something similar with his patched llvm for iOS. As for your linked Android patches, that might be possible but would be pointless unless you are only deploying to a device you patched the OS for. Better to patch llvm to support the same TLS scheme used for Android/x86. Interesting. A few others and I were talking about getting Android/ARM to function with LDC today. I'll be sure to keep up to date with your work! The remaining piece is to insert the correct function call to ___tls_get_addr when TLS variables are accessed, ie the equivalent to this patch for dmd's backend needs to be created for llvm: https://github.com/joakim-noah/dmd/commit/477f52cffb0d8bd1a698dd33ad7e2e66d9fa62ca#diff-d427199c5cd504da634c0c42fc2b3371 I've been putting off looking into llvm's internals enough to write that for a while now. If you or anybody else knows llvm better, feel free to take it. The remaining changes needed are in this small patch for llvm: https://gist.github.com/joakim-noah/1fb23fba1ba5b7e87e1a Cool. I will take a look
Re: What is the state of D with Android/iOS
On Tuesday, 24 February 2015 at 19:34:15 UTC, Joakim wrote: On Tuesday, 24 February 2015 at 17:55:59 UTC, Rishub Nagpal wrote: On Tuesday, 24 February 2015 at 17:15:28 UTC, Joakim wrote: If you simply want to call a D library within an Android/iOS app, that's possible, though there are still some rough edges. Specifically, there is still some work to be done with certain floating-point operations on iOS (http://forum.dlang.org/post/m2mw4tab0w@comcast.net) and while Android/x86 will work fine (http://wiki.dlang.org/Build_DMD_for_Android), Android/ARM doesn't currently support TLS. That lack of TLS support means you'd have to run a slightly patched druntime and I'm fairly certain phobos wouldn't work. Could any of these patches be used as a basis to remedy it? https://groups.google.com/forum/#!topic/0xlab-devel/aSOcm3c9PFk https://bugs.kde.org/show_bug.cgi?id=302709 Could you in theory recompile Android to support TLS and then try to compile an executable for Android/ARM ? Sorry, the way I wrote that may have been confusing: I meant that ldc doesn't currently support any form of TLS for Android/ARM. Native TLS is not supported on Android/bionic for any architecture, whether x86 or ARM. I worked around this on x86 by removing the SHF_TLS and STT_TLS flags from the ELF objects and using pthread_setspecific/pthread_getspecific instead (more details on the dmd PR: https://github.com/D-Programming-Language/dmd/pull/3643), which is basically how Walter implemented TLS on OS X/Mach-O years ago, as OS X didn't support native TLS till 10.7 and their TLV APIs are still undocumented. I need to patch llvm in a similar way to that dmd PR, so that Android/ARM can use the same scheme. It appears that Dan did something similar with his patched llvm for iOS. As for your linked Android patches, that might be possible but would be pointless unless you are only deploying to a device you patched the OS for. Better to patch llvm to support the same TLS scheme used for Android/x86. Interesting. A few others and I were talking about getting Android/ARM to function with LDC today. I'll be sure to keep up to date with your work!
Re: What is the state of D with Android/iOS
On Tuesday, 24 February 2015 at 17:15:28 UTC, Joakim wrote: On Tuesday, 24 February 2015 at 13:44:07 UTC, Rishub Nagpal wrote: Is D currently mature enough to create binaries for android/iOS? I've been researching this, but most posts predate 2013, and I wanted to know what was the current status. Mature enough? Sure, but that doesn't mean the support is there. D bindings for the JNI is certainly possible, so by extension it should be possible to call D libraries with Android's NDK, correct? If you simply want to call a D library within an Android/iOS app, that's possible, though there are still some rough edges. Specifically, there is still some work to be done with certain floating-point operations on iOS (http://forum.dlang.org/post/m2mw4tab0w@comcast.net) and while Android/x86 will work fine (http://wiki.dlang.org/Build_DMD_for_Android), Android/ARM doesn't currently support TLS. That lack of TLS support means you'd have to run a slightly patched druntime and I'm fairly certain phobos wouldn't work. Could any of these patches be used as a basis to remedy it? https://groups.google.com/forum/#!topic/0xlab-devel/aSOcm3c9PFk https://bugs.kde.org/show_bug.cgi?id=302709 Could you in theory recompile Android to support TLS and then try to compile an executable for Android/ARM ?
What is the state of D with Android/iOS
Is D currently mature enough to create binaries for android/iOS? I've been researching this, but most posts predate 2013, and I wanted to know what was the current status. D bindings for the JNI is certainly possible, so by extension it should be possible to call D libraries with Android's NDK, correct? Is is possible to write android apps purely in D similar to mono for android? http://developer.xamarin.com/guides/android/getting_started/hello,android/hello,android_quickstart/
