November 08

On Thursday, 10 August 2023 at 22:38:06 UTC, Basile B. wrote:

>

On Thursday, 10 August 2023 at 10:29:13 UTC, Basile B. wrote:

>

On Saturday, 22 July 2023 at 16:50:17 UTC, Ruby The Roobster wrote:

>

Following all of the steps for building on windows, I get the following linker error:

dexed-d.obj : error LNK2019: unresolved external symbol __imp__D3std12experimental6logger12__ModuleInfoZ referenced in function ldc.dllimport_relocation

I'm using LDC 1.32.0.
Linker used is the Microsoft linker, not sure if that matters.

Since those changes that should work compile (I admit I have not tested to see if that even runs) now.

Actually I will tell you a little story. Trust it or dont.

So I was on IRC, in contact with Richard, trying to fix the problem. So it was like "if I do that that will be ok ?" which I did. But there was still many error messages...So I was a bit upset like "that still does not work..."

It turns out that this worked... but the linker output 3000 lines of warnings..

If there is a working executable, could it be placed on some location from which it can be grabed? Maybe from https://gitlab.com/basile.b/dexed?

November 08

On Wednesday, 8 November 2023 at 08:22:16 UTC, Bienlein wrote:

>

On Thursday, 10 August 2023 at 22:38:06 UTC, Basile B. wrote:

>

On Thursday, 10 August 2023 at 10:29:13 UTC, Basile B. wrote:

>

On Saturday, 22 July 2023 at 16:50:17 UTC, Ruby The Roobster wrote:

>

Following all of the steps for building on windows, I get the following linker error:

dexed-d.obj : error LNK2019: unresolved external symbol __imp__D3std12experimental6logger12__ModuleInfoZ referenced in function ldc.dllimport_relocation

I'm using LDC 1.32.0.
Linker used is the Microsoft linker, not sure if that matters.

Since those changes that should work compile (I admit I have not tested to see if that even runs) now.

Actually I will tell you a little story. Trust it or dont.

So I was on IRC, in contact with Richard, trying to fix the problem. So it was like "if I do that that will be ok ?" which I did. But there was still many error messages...So I was a bit upset like "that still does not work..."

It turns out that this worked... but the linker output 3000 lines of warnings..

If there is a working executable, could it be placed on some location from which it can be grabed? Maybe from https://gitlab.com/basile.b/dexed?

Sorry, I meant a working executable for Windows.

November 08

On Wednesday, 8 November 2023 at 08:23:02 UTC, Bienlein wrote:

>

On Wednesday, 8 November 2023 at 08:22:16 UTC, Bienlein wrote:

>

On Thursday, 10 August 2023 at 22:38:06 UTC, Basile B. wrote:

>

On Thursday, 10 August 2023 at 10:29:13 UTC, Basile B. wrote:

>

On Saturday, 22 July 2023 at 16:50:17 UTC, Ruby The Roobster wrote:

>

Following all of the steps for building on windows, I get the following linker error:

dexed-d.obj : error LNK2019: unresolved external symbol __imp__D3std12experimental6logger12__ModuleInfoZ referenced in function ldc.dllimport_relocation

I'm using LDC 1.32.0.
Linker used is the Microsoft linker, not sure if that matters.

Since those changes that should work compile (I admit I have not tested to see if that even runs) now.

Actually I will tell you a little story. Trust it or dont.

So I was on IRC, in contact with Richard, trying to fix the problem. So it was like "if I do that that will be ok ?" which I did. But there was still many error messages...So I was a bit upset like "that still does not work..."

It turns out that this worked... but the linker output 3000 lines of warnings..

If there is a working executable, could it be placed on some location from which it can be grabed? Maybe from https://gitlab.com/basile.b/dexed?

Sorry, I meant a working executable for Windows.

On AppYewyor it is no longer available. It says: "Artifacts older than 1 month are automatically deleted. For more details see Artifacts retention policy.".

December 02

On Wednesday, 8 November 2023 at 08:26:03 UTC, Bienlein wrote:

>

On AppYewyor it is no longer available. It says: "Artifacts older than 1 month are automatically deleted. For more details see Artifacts retention policy.".

I just have regenerated them : https://ci.appveyor.com/api/buildjobs/4k69nijm393122g7/artifacts/setup%2Foutput.zip

1 2
Next ›   Last »