Hi,

I'm trying to follow the instructions for vibe-d with:

    >dub init web vibe.d
    >cd web
    >dub

and then add the line "subConfigurations": {"vibe-d": "win32"}" to the dub.json file.

This however is producing errors during linking. Could I get a hand?

Pastebin of dub --vverbose: http://pastebin.com/4BcHJM74

Thanks,
Charles

On Friday, 20 February 2015 at 02:50:05 UTC, Charles wrote:
> Pastebin of dub --vverbose: http://pastebin.com/4BcHJM74

> Target vibe-d 0.7.22 is up to date. Use --force to rebuild.
Have you tried the --force switch to rebuild vibe.d?

Looks like the existing vibe.d lib was build against a different
build of druntime.

On Friday, 20 February 2015 at 02:55:32 UTC, MartinNowak wrote:
> On Friday, 20 February 2015 at 02:50:05 UTC, Charles wrote:
>> Pastebin of dub --vverbose: http://pastebin.com/4BcHJM74
>
>> Target vibe-d 0.7.22 is up to date. Use --force to rebuild.
> Have you tried the --force switch to rebuild vibe.d?
>
> Looks like the existing vibe.d lib was build against a different
> build of druntime.

Yes, I have. Here's a pastebin with --force --vverbose: http://pastebin.com/qZEKUN46

On Friday, 20 February 2015 at 04:00:21 UTC, Charles wrote:
> Yes, I have. Here's a pastebin with --force --vverbose: http://pastebin.com/qZEKUN46

Just tried the dub init web vibe.d && cd web && dub thing, works for me.
So the most interesting questions.

- What version of dub and dmd are you using?
- Are those installer versions or did you build anything yourself?

On Friday, 20 February 2015 at 04:13:08 UTC, MartinNowak wrote:
> On Friday, 20 February 2015 at 04:00:21 UTC, Charles wrote:
>> Yes, I have. Here's a pastebin with --force --vverbose: http://pastebin.com/qZEKUN46
>
> Just tried the dub init web vibe.d && cd web && dub thing, works for me.
> So the most interesting questions.
>
> - What version of dub and dmd are you using?
> - Are those installer versions or did you build anything yourself?


They're installer versions, dub is 0.9.22 Nov 22 I want to say,
and DMD is 2.066.1

On Friday, 20 February 2015 at 04:48:09 UTC, Charles wrote:
> They're installer versions, dub is 0.9.22 Nov 22 I want to say,
> and DMD is 2.066.1

Same ones I tried.

With --force dmd seems to fail but there is not output.
Can you run only the link command with a -v to get verbose dmd output?

> dmd -c -of.dub\build\application-debug-windows-x86-dmd_2066-7FF336D92D4F5796EA8623FC9A6A9B90\web.obj -debug -g -w -version=VibeDefaultMain -version=VibeWin32Driver -version=Have_web -version=Have_vibe_d -version=Have_openssl -Isource -IC:\Users\Charles\AppData\Roaming\dub\packages\vibe-d-0.7.22\source -IC:\Users\Charles\AppData\Roaming\dub\packages\openssl-1.1.3_1.0.1g -Jviews source\app.d C:\Users\Charles\AppData\Roaming\dub\packages\vibe-d-0.7.22\source\vibe\appmain.d

On Friday, 20 February 2015 at 14:36:47 UTC, MartinNowak wrote:
> On Friday, 20 February 2015 at 04:48:09 UTC, Charles wrote:
>> They're installer versions, dub is 0.9.22 Nov 22 I want to say,
>> and DMD is 2.066.1
>
> Same ones I tried.
>
> With --force dmd seems to fail but there is not output.
> Can you run only the link command with a -v to get verbose dmd output?
>
>> dmd -c -of.dub\build\application-debug-windows-x86-dmd_2066-7FF336D92D4F5796EA8623FC9A6A9B90\web.obj -debug -g -w -version=VibeDefaultMain -version=VibeWin32Driver -version=Have_web -version=Have_vibe_d -version=Have_openssl -Isource -IC:\Users\Charles\AppData\Roaming\dub\packages\vibe-d-0.7.22\source -IC:\Users\Charles\AppData\Roaming\dub\packages\openssl-1.1.3_1.0.1g -Jviews source\app.d C:\Users\Charles\AppData\Roaming\dub\packages\vibe-d-0.7.22\source\vibe\appmain.d

Thanks for the help with this. The link command ran without error, and it's output is here: http://pastebin.com/eqT4vst6

To be exact, the command I ran was this:  dmd -v -c -of.dub\build\application-debug-windows-x86-dmd_2066-7FF336D92D4F5796EA8623FC9A6A9B90\web.obj -debuenssl -Isource -IC:\Users\Charles\AppData\Roaming\dub\packages\vibe-d-0.7.22\source -IC:\Users\Charles\AppData\-d-0.7.22\source\vibe\appmain.d > %userprofile%\Desktop\output.txt

It didn't produce any errors as far as I can tell, but I'm not sure how to tell what the mangled function names are.

Sorry about the delay in getting back to you on this.

Charles