• =?ISO-8859-1?Q?Anders_F_Bj=F6rklund?= (11/13) Dec 19 2004 These GDC-installed directories:
• =?ISO-8859-1?Q?Anders_F_Bj=F6rklund?= (10/22) May 02 2005 I'll rephrase this one for GDC 0.11:
• David Friedman (6/34) May 04 2005 If one were writing C code to interact with the D runtime, it might be
• =?ISO-8859-1?Q?Anders_F_Bj=F6rklund?= (6/12) May 05 2005 I guess it's just me being old and grumpy and failing to see what

=?ISO-8859-1?Q?Anders_F_Bj=F6rklund?= <afb algonet.se> writes:

These GDC-installed directories:

- include/d/etc/c/recls

- include/d/etc/c/stlsoft

- include/d/etc/c/zlib

contain C/C++ code and headers...


Are they really needed for D ?

I thought that "include/d" would only hold
import modules for use with D itself (.d) ?

Especially these two, look useless enough:

 /opt/gdc/include/d/etc/c/zlib/zlib.lib: Microsoft Visual C library
 /opt/gdc/include/d/etc/c/recls/recls.lib: Microsoft Visual C library

Maybe "make install" needs some refinements ?

--anders

=?ISO-8859-1?Q?Anders_F_Bj=F6rklund?= <afb algonet.se> writes:

Anders F Björklund wrote:

 These GDC-installed directories:
 
 - include/d/etc/c/recls
 
 - include/d/etc/c/stlsoft
 
 - include/d/etc/c/zlib
 
 contain C/C++ code and headers...
 
 
 Are they really needed for D ?

I'll rephrase this one for GDC 0.11:

Why does GDC install the .h headers
for zlib and recls ? And not just the
.d modules (etc/c/zlib.d and std/recls.d)

--anders

PS.
Walter has already rejected moving
etc/c/zlib.d to std/c/zlib.d, so I
won't be discussing that - thank you.

David Friedman <d3rdclsmail_a_ _t_earthlink_d_._t_net> writes:

Anders F Björklund wrote:
 Anders F Björklund wrote:
 
 These GDC-installed directories:

 - include/d/etc/c/recls

 - include/d/etc/c/stlsoft

 - include/d/etc/c/zlib

 contain C/C++ code and headers...


 Are they really needed for D ?

 
 
 I'll rephrase this one for GDC 0.11:
 
 Why does GDC install the .h headers
 for zlib and recls ? And not just the
 .d modules (etc/c/zlib.d and std/recls.d)
 
 --anders
 
 PS.
 Walter has already rejected moving
 etc/c/zlib.d to std/c/zlib.d, so I
 won't be discussing that - thank you.

If one were writing C code to interact with the D runtime, it might be 
useful.  I don't think it will interfere with gdc.

OTOH, now that I have moved everything to a version-specific directory, 
it is difficult to use the headers.

David

=?ISO-8859-1?Q?Anders_F_Bj=F6rklund?= <afb algonet.se> writes:

David Friedman wrote:

 Why does GDC install the .h headers
 for zlib and recls ? And not just the
 .d modules (etc/c/zlib.d and std/recls.d)

 
 If one were writing C code to interact with the D runtime, it might be 
 useful.  I don't think it will interfere with gdc.

I guess it's just me being old and grumpy and failing to see what
the zlib and recls C/C++ libraries does in the standard D library...

At least just the headers is better than the full distributions.
It's not really a big deal (what's 800K) and it will not interfere.

--anders