Am 11.02.2011 19:56, schrieb Dmitry Olshansky:
> Ok, bumping this up with the latest news from UniLink developers: <quote>
> 
> Ok, we release it's as D extension in next release.
> 
> Best regards,
>  UniLink
> 
> </quote>
> 
> That's just plain awesome ;)
> 

Great :)

On 2/11/11 12:56 PM, Dmitry Olshansky wrote:
> Ok, bumping this up with the latest news from UniLink developers:
> <quote>
>
> Ok, we release it's as D extension in next release.
>
> Best regards,
> UniLink
>
> </quote>
>
> That's just plain awesome ;)
>

Is UniLink working with 64 bits?

Andrei

On 12.02.2011 3:13, Andrei Alexandrescu wrote:
> On 2/11/11 12:56 PM, Dmitry Olshansky wrote:
>> Ok, bumping this up with the latest news from UniLink developers:
>> <quote>
>>
>> Ok, we release it's as D extension in next release.
>>
>> Best regards,
>> UniLink
>>
>> </quote>
>>
>> That's just plain awesome ;)
>>
>
> Is UniLink working with 64 bits?
>
> Andrei

Yes, that's actually one of it's benefits, as I told somewhere along the thread.
To be 101% sure I just linked a simple 'hello x64' program.

-- 
Dmitry Olshansky

Hopefully that release will come soon ;)

Dmitry Olshansky wrote:
> Ok, bumping this up with the latest news from UniLink developers:
> <quote>
> 
> Ok, we release it's as D extension in next release.
> 
> Best regards,
>  UniLink
> 
> </quote>
> 
> That's just plain awesome ;)
> 

yeah, it would be great to be able to link against anything else in the windows world.

I just tried unilink on a small program compiled with dmd-2.051 and it worked alright. Surprisingly, the executable is less than half the size of the optlink generated file. Comparing the map files, it does not seem to reference less symbols (the corrupted map files written by optlink do not allow perfect comparison), so maybe there is a rather large alignment used by optlink?

Unfortunately, unilink does not support the debug information emitted by dmd:

UniLink v1.07 [beta] (build 1.19)
Warning: CV(1)-style debug-info not supported
Warning: Linked modules don't contain source-level debug information

BTW: The authors seem to plan to make unilink a commercial product. Here's a quote from the help file: "If current version of UniLink is beta (all other versions are commercial and can't be used w/o license), keep in mind, any beta will "yaff" after ~1.5 month of expired."

On 2/12/11, Rainer Schuetze <r.sagitario@gmx.de> wrote:
>
> BTW: The authors seem to plan to make unilink a commercial product. Here's a quote from the help file: "If current version of UniLink is beta (all other versions are commercial and can't be used w/o license), keep in mind, any beta will "yaff" after ~1.5 month of expired."
>

Great, from one closed-source linker to another.

What linker does GDC use on Windows? And has anyone had any success with using it on Windows?

On 2/12/11 3:30 PM, Andrej Mitrovic wrote:
> What linker does GDC use on Windows? And has anyone had any success
> with using it on Windows?

IIRC, it emits COFF and uses the ld from MinGW to link.

David

On 2/12/11, David Nadlinger <see@klickverbot.at> wrote:
> On 2/12/11 3:30 PM, Andrej Mitrovic wrote:
>> What linker does GDC use on Windows? And has anyone had any success with using it on Windows?
>
> IIRC, it emits COFF and uses the ld from MinGW to link.
>
> David
>

That's nice to know. I'll give GDC a spin and see how it's working out.

On 12.02.2011 16:32, Rainer Schuetze wrote:
>
> Dmitry Olshansky wrote:
>> Ok, bumping this up with the latest news from UniLink developers:
>> <quote>
>>
>> Ok, we release it's as D extension in next release.
>>
>> Best regards,
>>  UniLink
>>
>> </quote>
>>
>> That's just plain awesome ;)
>>
>
> yeah, it would be great to be able to link against anything else in the windows world.
>
> I just tried unilink on a small program compiled with dmd-2.051 and it worked alright. Surprisingly, the executable is less than half the size of the optlink generated file. Comparing the map files, it does not seem to reference less symbols (the corrupted map files written by optlink do not allow perfect comparison), so maybe there is a rather large alignment used by optlink?

Same things here, as to the executable size it might be some smart technology they plan to sell ;)
>
> Unfortunately, unilink does not support the debug information emitted by dmd:
>
> UniLink v1.07 [beta] (build 1.19)
> Warning: CV(1)-style debug-info not supported
> Warning: Linked modules don't contain source-level debug information

Yeah, that spoils the party...

>
> BTW: The authors seem to plan to make unilink a commercial product. Here's a quote from the help file: "If current version of UniLink is beta (all other versions are commercial and can't be used w/o license), keep in mind, any beta will "yaff" after ~1.5 month of expired."

I've seen that "yaff" :) Merely a message in console that states that your beta linker is out of date, functionality not crippled. More interestingly I haven't seen any commercial versions yet..

-- 
Dmitry Olshansky

Andrej Mitrovic wrote:
> Great, from one closed-source linker to another.

Making optlink open source won't make any difference. Few are skilled at asm anymore, and likely none of them would want to work on optlink for free.