Linking with/Debugging static C/C++ libraries

[Dmitry Olshansky]

On 30.05.2011 19:14, Jeff Slutter wrote:
> On 5/30/2011 10:57 AM, Dmitry Olshansky wrote:
>> It was me who brought it Unilink out of infernal abyss :)  See also:
>> http://www.digitalmars.com/d/archives/digitalmars/D/announce/Alternative_linker_win32_64_20086.html
>>
>>
>> Seriously I still suggest to try it out, and at any rate author showed
>> quite a motivation and provided full D support in no time.
>> (there is little problem that he won't use CV debug symbols... and
>> UniLink _converts_ them to Borland's TDS format)
>> Still it's now possible to use any linker with VisualD, using 'compile
>> only' option (in fact I just tried it out myself).
> I will give it a try.
>
> With the Borland TDS debug symbols, that means no debugging with
> VisualD/Visual Studio right? (No CodeView, No PDB)
>
Yup, Borland's tools only.
For the sake of expreiment I did tested it with latest trial of CodeGear 
C++ Builder-something long ago.
I even thought to tweak Mago debugger so that it reads TDS symbols. IIRC 
it has dedicated component for symbol loading.
But with GSOC I think my hands are full for the rest of summer :)

>> Right and I've seen this cool option 'use other compiler' in recent
>> VisualD with textbox for command line. So GDC&  LDC support is almost
>> there.
> I missed that, so that's exciting!


-- 
Dmitry Olshansky