June 07, 2016
On Tuesday, 7 June 2016 at 05:46:51 UTC, Kai Nacke wrote:
> Outcome of the discussion was that the first version based on the frontend written in D should be version 1.0. (This is a major milestone.)

Congratulations! I'm happy about this.
June 07, 2016
On 2016-06-07 14:59, FreeSlave wrote:

> Yes. Look at https://issues.dlang.org/show_bug.cgi?id=16096
>
> I don't have such problem with ldc 1.0.0.

Thanks, I'll have a look.

-- 
/Jacob Carlborg
June 07, 2016
On Monday, 6 June 2016 at 10:45:39 UTC, Guillaume Piolat wrote:
>> very nice!
>> how about a howto for windows/VS users?
>

1) Download LDC unpack anywhere
2) Download VisualD install
https://github.com/dlang/visuald/releases
3) Setup VisualD to find LDC
Tools->Options->Projects and Solutions->Visual D Settings->LDC Directories
...
Profit!

June 07, 2016
On Tuesday, 7 June 2016 at 16:54:55 UTC, Daniel N wrote:
> On Monday, 6 June 2016 at 10:45:39 UTC, Guillaume Piolat wrote:
>>> very nice!
>>> how about a howto for windows/VS users?
>>
>
> 1) Download LDC unpack anywhere
> 2) Download VisualD install
> https://github.com/dlang/visuald/releases
> 3) Setup VisualD to find LDC
> Tools->Options->Projects and Solutions->Visual D Settings->LDC Directories
> ...
> Profit!

Excellent :-)
https://github.com/dlang/visuald/pull/61

(I am just "copy-pasting" there! Please create your own PR with better info! )
June 08, 2016
Was there anything changed regarding -od / -op / -oq behaviour? I am getting DCD build errors with new LDC because object files are emitted to a different place it expects.
June 09, 2016
On Monday, 6 June 2016 at 10:45:39 UTC, Guillaume Piolat wrote:
> On Monday, 6 June 2016 at 07:25:49 UTC, tester wrote:
>> On Monday, 6 June 2016 at 07:00:56 UTC, Kai Nacke wrote:
>>> Hi everyone,
>>>
>>> It is a great pleasure to announce that version 1.0.0 of LDC, the LLVM-based D compiler, is now available for download!
>>>
>>> The release is based on the 2.070.2 frontend and standard library and supports LLVM 3.5-3.8. We provide binaries for Linux, OX X, Win32 & Win64, Linux/ARM (armv7hf). :-)
>>>
>>> As usual, you can find links to the changelog and the binary packages over at digitalmars.D.ldc:
>>> http://forum.dlang.org/post/lwsnqbravjqbnnryvjkx@forum.dlang.org
>>>
>>> Regards,
>>> Kai
>>
>>
>> very nice!
>> how about a howto for windows/VS users?
>
> Hi,
>
> Here is what I've learned:
>
> - use VS 2015 preferably,
> - since a while the stock LDC package work as is, nothing to configure,
> - use PATH and --compiler=ldc2 or --compiler=path/to/compiler.exe to tell dub where LDC is (separate packages for 32-bit and 64-bit),
> - to avoid a dependency on the VS 2015 runtime, add the following linker flags:
>
> "lflags-windows-ldc": [
>         "libcmt.lib",
>         "/nodefaultlib:msvcrt.lib",
>         "/nodefaultlib:vcruntime.lib"
>     ],
>
> - executables made with LDC are not supported on XP and Vista, but seem to work regardless :)

Thanks!

See https://github.com/ldc-developers/ldc-scripts/pull/1

Regards,
Kai
June 13, 2016
Awesome news, just noticed a blurb on the Linux news site Phoronix about this as well:

http://www.phoronix.com/scan.php?page=news_item&px=LDC-1.0-Released
June 14, 2016
On Monday, 13 June 2016 at 12:35:57 UTC, Gerald wrote:
> Awesome news, just noticed a blurb on the Linux news site Phoronix about this as well:
>
> http://www.phoronix.com/scan.php?page=news_item&px=LDC-1.0-Released

Yes, we are in the press. :-)

http://llvmweekly.org/issue/128

Regards,
Kai
June 15, 2016
On 2016-06-07 14:59, FreeSlave wrote:

> Yes. Look at https://issues.dlang.org/show_bug.cgi?id=16096
>
> I don't have such problem with ldc 1.0.0.

Fixed, unless you already have noticed.

-- 
/Jacob Carlborg
Next ›   Last »
1 2 3