Menu
Learn
Documentation
Language Reference
Library Reference
Command-line Reference
Feature Overview
Articles
Downloads
Packages
Community
Blog
Orgs using D
Twitter
Calendar
Forums
IRC
Wiki
GitHub
Issues
Get involved
Contributors
Foundation
Donate
Sponsors
Resources
Tour
Books
Tutorials
Tools
Editors
IDEs
Visual D
Acknowledgments
D Style
Glossary
Sitemap
Search
Entire Site
Language
Library
Forums
Learn group
This thread
go
Forums
Forum Index
New users
Learn
Community
General
Announce
Improvements
DIP Ideas
DIP Devel.
Ecosystem
GDC
LDC
Debuggers
IDEs
DWT
Development
Internals
Issues
Beta
DMD
Phobos
Druntime
Study
Turkish
Genel
Duyuru
Log in
Settings
Help
Index
»
Learn
»
Linking with/Debugging static C/C++ libraries
»
Post reply
Warning: the post you are replying to is from 14 years ago (May 30, 2011).
Posting to
Learn
in reply to
Jeff Slutter
Your name:
Your email address (
?
):
Subject:
Message:
On Monday, 30 May 2011 at 15:19:02 UTC, 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) > > >> 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!
Enable
Markdown
Copyright © 1999-2021 by the
D Language Foundation