version 2.062? 2.066.1?

arm-linux-gnueabi 	
arm-linux-gnueabihf

?

I remember a year ago when I tried D for the first time I downloaded both gdc and ldc and everything just worked and each install was just like dmd!  Now it seems like a step backwards and I'm not sure what is going on.  arm-linux-genuabi? arm-linux-gnueableihfqueridsofeyfh?  aifh-fkeif-fjjjjjjjj-fdsskjhfkjfafaaaaaa?

Is D dead?  If DMD is the reference compiler and can't be used for production code... and gdc is about 1000 versions out of date... and ldc requires building from sources(actually I didn't have too much trouble with installing it but it doesn't work with my libs because of the crappy coff issues that D has had since birth(it's like a tumor)).

`Windows users should replace arm-gdcproject-linux-gnueabi-gdc with arm-gdcproject-linux-gnueabi-gdc.exe.`

Why so many hoops to jump through? D is making me feel like a poodle!

On Friday, 10 June 2016 at 19:37:13 UTC, Joerg Joergonson wrote:
> 
>  arm-linux-genuabi? arm-linux-gnueableihfqueridsofeyfh?  aifh-fkeif-fjjjjjjjj-fdsskjhfkjfafaaaaaa?

Rofl!

> and ldc requires building from sources(actually I didn't have too much trouble with installing it but it doesn't work with my libs because of the crappy coff issues that D has had since birth(it's like a tumor)).

Why do you have to build from sources? Any details about the problems you see?

Thanks,
  Johan

On Friday, 10 June 2016 at 19:51:19 UTC, Johan Engelen wrote:
> On Friday, 10 June 2016 at 19:37:13 UTC, Joerg Joergonson wrote:
>> 
>>  arm-linux-genuabi? arm-linux-gnueableihfqueridsofeyfh?  aifh-fkeif-fjjjjjjjj-fdsskjhfkjfafaaaaaa?
>
> Rofl!
>
>> and ldc requires building from sources(actually I didn't have too much trouble with installing it but it doesn't work with my libs because of the crappy coff issues that D has had since birth(it's like a tumor)).
>
> Why do you have to build from sources? Any details about the problems you see?
>
> Thanks,
>   Johan

Well, the post was a bit incoherent because getting all this stuff working is. I was searching for ldc and ran across some web site that had only the sources(same for gdc).

The point of it all is that things seem to be a bit discombobulated and make D look bad.  Professions won't use D if it can't be used professionally(not that I'm a pro, just saying).

Why isn't there a proper binaries for ldc and gdc that work out of the box like dmd?  There used to be. What's up with all this arm-linux-genuabi crap? When one opens up the archive all the files are named that way too.  There is no explanation of what that means. Did some kid write this stuff in his basement or is this suppose to be serious? Do people think about the end user when creating this stuff or is it just a eureka moment "Lightbulb: Lets create some spaghetti!".

I would have thought things would have gotten easier and more logical but that doesn't seem to be the case.

On Friday, 10 June 2016 at 20:30:36 UTC, Joerg Joergonson wrote:
> On Friday, 10 June 2016 at 19:51:19 UTC, Johan Engelen wrote:
>>   [...]
>
> Well, the post was a bit incoherent because getting all this stuff working is. I was searching for ldc and ran across some web site that had only the sources(same for gdc).
>
> The point of it all is that things seem to be a bit discombobulated and make D look bad.  Professions won't use D if it can't be used professionally(not that I'm a pro, just saying).
>
> Why isn't there a proper binaries for ldc and gdc that work out of the box like dmd?  There used to be. What's up with all this arm-linux-genuabi crap? When one opens up the archive all the files are named that way too.  There is no explanation of what that means. Did some kid write this stuff in his basement or is this suppose to be serious? Do people think about the end user when creating this stuff or is it just a eureka moment "Lightbulb: Lets create some spaghetti!".
>
> I would have thought things would have gotten easier and more logical but that doesn't seem to be the case.

The official download page is http://dlang.org/download.html (ldc download can be found from there) - please let us know if you find other outdated pages.

You can even use the official install script for ldc and gdc too :)

On Friday, 10 June 2016 at 20:30:36 UTC, Joerg Joergonson wrote:
> Well, the post was a bit incoherent because getting all this stuff working is. I was searching for ldc and ran across some web site that had only the sources(same for gdc).
> […]
> Why isn't there a proper binaries for ldc and gdc that work out of the box like dmd?

LDC binaries exist and work out of the box – just extract them anywhere and you are set. Have a look at the official release list: https://github.com/ldc-developers/ldc/releases

I'm not sure what other website you came across; maybe there are some links that need fixing?

 — David

On Friday, 10 June 2016 at 20:30:36 UTC, Joerg Joergonson wrote:
> Why isn't there a proper binaries for ldc and gdc that work out of the box like dmd?  There used to be. What's up with all this arm-linux-genuabi crap?

Those are proper binaries that work out of the box on different platforms.

Alas Windows doesn't have prebuilt binaries for gdc targeting Windows. Weird, the Windows binaries there generate ARM binaries (for phones and stuff).

LDC has Win32 builds though:
https://github.com/ldc-developers/ldc/releases/download/v1.0.0/ldc2-1.0.0-win32-msvc.zip

On Friday, 10 June 2016 at 21:33:58 UTC, Adam D. Ruppe wrote:
> On Friday, 10 June 2016 at 20:30:36 UTC, Joerg Joergonson wrote:
>> Why isn't there a proper binaries for ldc and gdc that work out of the box like dmd?  There used to be. What's up with all this arm-linux-genuabi crap?
>
> Those are proper binaries that work out of the box on different platforms.
>
> Alas Windows doesn't have prebuilt binaries for gdc targeting Windows. Weird, the Windows binaries there generate ARM binaries (for phones and stuff).
>
> LDC has Win32 builds though:
> https://github.com/ldc-developers/ldc/releases/download/v1.0.0/ldc2-1.0.0-win32-msvc.zip

The problem I'm getting with ldc, using your simpledisplay, is that the libs aren't loading due to the wrong format. It's the omf vs coff thing or whatever, I guess... I didn't feel like messing with it right now(later I'll need both x86 and x64 libs that work with dmd, ldc, and gdc). But yea, ldc basically worked similar to dmd, but not gdc.

On Friday, 10 June 2016 at 22:01:15 UTC, Joerg Joergonson wrote:
> The problem I'm getting with ldc, using your simpledisplay, is that the libs aren't loading due to the wrong format. It's the omf vs coff thing or whatever, I guess...

How do you mean that? LDC/MSVC uses COFF, and there should be no issues with linking against any external libraries you might need. Knowing Adam, though, simpledisplay probably only depends on the Win32 API, so I'm not sure where the issue would be in the first place.

Unless, of course, you are referring to linking an LDC executable against a simpledisplay library built with DMD – the different D compilers are not ABI-compatible, and will not be for the foreseeable future.

 — David

On Saturday, 11 June 2016 at 01:04:28 UTC, David Nadlinger wrote:
> Knowing Adam, though, simpledisplay probably only depends on the Win32 API, so I'm not sure where the issue would be in the first place.

It also uses opengl32.lib that could be a problem. I offer the .omf file on my github for people to download... but with ldc you'd want to use whatever is packaged there (the Microsoft ones?).

Or compile with -version=without_opengl and that might work too (or the LDC translation of that). Grab the newest version btw because I just noticed a bug in that version.

On Friday, 10 June 2016 at 22:01:15 UTC, Joerg Joergonson wrote:
> The problem I'm getting with ldc, using your simpledisplay, is that the libs aren't loading due to the wrong format.


What's the exact message and what did you do? The opengl32.lib I have on my github is for dmd 32 bit, ldc uses the Microsoft one I think so you shouldn't need anything else.