How can I let other people to know what's in my libs?

Chad J gamerChad at _spamIsBad_gmail.com
Sun Dec 3 03:30:38 PST 2006


zhang wrote:
> Hi, everybody! I still understand how can I let other people to know
> what's in my libs? For example, I have organized a lib using D, and want
> other people to use it. What should I offer except for the LIB. Should I
> offer the sources which maybe include some modules. I know it is very
> easy in C/C++. I just offer some header files in C/C++, but what can I
> do in D. 
> 
> Somebody can give me some hints. Thanks for your any helps.
> 

If your library is opensource, then you might just give the .d files and 
nevermind the .lib.  D compiles fast, so it's doubtful anyone will mind 
the extra compilation.

Otherwise if you have some reason to keep the source under wraps and 
just offer the .lib, then dmd can make d interface files (.di files). 
The .di files contain all the info someone needs to link to your .lib, 
and little or no more.
http://www.digitalmars.com/d/dcompiler.html
At the bottom of the page, read "D Interface Files".



More information about the Digitalmars-d mailing list