June 26, 2020
On Friday, 26 June 2020 at 18:28:48 UTC, kinke wrote:
> Wrt. automating the last mile (actually, the last few inches), setting up ldc2.conf, I've repeatedly stated that generalizing Adam's little Android tool would clearly be my choice. Sebastian Koppe promised to do that, but he's probably quite busy at the moment.

Yeah, it shouldn't be too hard to do. Maybe I'll look at doing it myself, imagine

dub run xc-setup

could do a setup wizard kind of thing that does the rest.

Then I think all we'd want from you is prolly just a backlink on the readme or whatever.
June 26, 2020
On Friday, 26 June 2020 at 19:18:44 UTC, Adam D. Ruppe wrote:
> On Friday, 26 June 2020 at 18:28:48 UTC, kinke wrote:
>> Wrt. automating the last mile (actually, the last few inches), setting up ldc2.conf, I've repeatedly stated that generalizing Adam's little Android tool would clearly be my choice. Sebastian Koppe promised to do that, but he's probably quite busy at the moment.
>
> Yeah, it shouldn't be too hard to do. Maybe I'll look at doing it myself

That'd be awesome. I have a pretty concrete idea of how this should look like, and would definitely prefer a little tool directly inside the LDC repo, analogous to ldc-build-runtime. The main reason being that it's tightly coupled to the prebuilt packages, and they are controlled by the CI scripts in the LDC repo.

See https://forum.dlang.org/post/pujpcnubepoknwbircob@forum.dlang.org for how I imagine this to be used.
June 26, 2020
On Friday, 26 June 2020 at 19:33:03 UTC, kinke wrote:
>
> That'd be awesome. I have a pretty concrete idea of how this should look like, and would definitely prefer a little tool directly inside the LDC repo, analogous to ldc-build-runtime. The main reason being that it's tightly coupled to the prebuilt packages, and they are controlled by the CI scripts in the LDC repo.
>
> See https://forum.dlang.org/post/pujpcnubepoknwbircob@forum.dlang.org for how I imagine this to be used.

That would be very useful. Keep in mind that many would like to have several targets installed at the same time so that you don't have to have a separate ldc directory for each target. As mentioned using ldc -mtriple=x-y-z will just take another target than the default one and automatically choose the right libraries and import paths.

BTW, why is LDC using -mtriple when clang is using --target?
June 26, 2020
On 6/26/2020 2:18 AM, aberba wrote:
> On Friday, 26 June 2020 at 01:25:36 UTC, Walter Bright wrote:
>> On 6/24/2020 4:21 AM, aberba wrote:
>>> PC was the only compelling target for Intel/Amd targets but now its changing.
>>
>> Search for "arm computer" on newegg.com:
>>
>> https://www.newegg.com/p/pl?d=arm+computer
>>
>> :-)
> 
> Just did. Don't get your point.

Not a single computer powered by an ARM CPU shows up.

Amazon doesn't have any, either.

Neither even have ARM in their CPU category.
June 26, 2020
On Friday, 26 June 2020 at 20:43:06 UTC, Walter Bright wrote:
> Not a single computer powered by an ARM CPU shows up.

Maybe that's just a bad search term cuz there's plenty of arm devices on the market, they are just often called other things like "ipads" and "chromebooks" and other brand names instead of being generically called "computers".
June 27, 2020
I think NVIDIA Jetson series might be the only big name boards you can get. But they are dev kits meant for machine learning (high end boards are quad core, 8gb ram).
June 26, 2020
On 6/26/2020 1:48 PM, Adam D. Ruppe wrote:
> On Friday, 26 June 2020 at 20:43:06 UTC, Walter Bright wrote:
>> Not a single computer powered by an ARM CPU shows up.
> 
> Maybe that's just a bad search term cuz there's plenty of arm devices on the market, they are just often called other things like "ipads" and "chromebooks" and other brand names instead of being generically called "computers".

Search on "desktop computer". On the left, you'll find a CPU menu. No ARM processors in it. Neither for Amazon.

I find it curious that nobody makes one.
June 26, 2020
On Friday, 26 June 2020 at 20:50:13 UTC, rikki cattermole wrote:
> I think NVIDIA Jetson series might be the only big name boards you can get. But they are dev kits meant for machine learning (high end boards are quad core, 8gb ram).

D code is alive and kicking inside a Jetson TX2 for quite a long time now, built by us for a really big medical customer...

Next step, Nvidia Xavier NX ...


June 27, 2020
On 27/06/2020 8:58 AM, Paolo Invernizzi wrote:
> On Friday, 26 June 2020 at 20:50:13 UTC, rikki cattermole wrote:
>> I think NVIDIA Jetson series might be the only big name boards you can get. But they are dev kits meant for machine learning (high end boards are quad core, 8gb ram).
> 
> D code is alive and kicking inside a Jetson TX2 for quite a long time now, built by us for a really big medical customer...
> 
> Next step, Nvidia Xavier NX ...

Neat!

Could you do a D blog article on what you do with it?

It would be a good show of application of D.
June 26, 2020
On Friday, 26 June 2020 at 21:00:53 UTC, rikki cattermole wrote:
> On 27/06/2020 8:58 AM, Paolo Invernizzi wrote:
>> On Friday, 26 June 2020 at 20:50:13 UTC, rikki cattermole wrote:
>>> I think NVIDIA Jetson series might be the only big name boards you can get. But they are dev kits meant for machine learning (high end boards are quad core, 8gb ram).
>> 
>> D code is alive and kicking inside a Jetson TX2 for quite a long time now, built by us for a really big medical customer...
>> 
>> Next step, Nvidia Xavier NX ...
>
> Neat!
>
> Could you do a D blog article on what you do with it?
>
> It would be a good show of application of D.

The bad things around big medical companies is that they tend to tie your hands with a pletora of NDA agreements ... I've literally lost the count around how many I've signed!

What I can tell is that it's driving a depth camera, and mixing data in realtime received by an eye-tracker device.