Re: ImportC GUID compilation problem with some Windows headers

2024-03-21 Thread Carl Sturtivant via Digitalmars-d-learn
On Thursday, 21 March 2024 at 22:33:17 UTC, Dave P. wrote: I filed a bug for this: https://issues.dlang.org/show_bug.cgi?id=24447 I haven’t tried on a windows box and this is just from me grepping through header files, but maybe try to `#define EXTERN_C` as nothing in the meantime? I'll

Re: ImportC GUID compilation problem with some Windows headers

2024-03-21 Thread Dave P. via Digitalmars-d-learn
On Thursday, 21 March 2024 at 18:19:58 UTC, Carl Sturtivant wrote: On Thursday, 21 March 2024 at 00:06:56 UTC, Carl Sturtivant wrote: ```C EXTERN_GUID(IID_IBlahBlahBlah, 0xabcdef12, 0x11d2, 0xab3a, 0xc0, 0x4f, [...] ); ``` Has anyone successfully compiled an EXTERN_GUID declaration like

Re: ImportC GUID compilation problem with some Windows headers

2024-03-21 Thread Carl Sturtivant via Digitalmars-d-learn
On Thursday, 21 March 2024 at 00:06:56 UTC, Carl Sturtivant wrote: ```C EXTERN_GUID(IID_IBlahBlahBlah, 0xabcdef12, 0x11d2, 0xab3a, 0xc0, 0x4f, [...] ); ``` Has anyone successfully compiled an EXTERN_GUID declaration like this in a Windows header with ImportC using some C macro trickery for

ImportC GUID compilation problem with some Windows headers

2024-03-20 Thread Carl Sturtivant via Digitalmars-d-learn
I'm running into this COM related issue with some Windows headers, in the case when each GUID is declared in such a file as follows. ```C EXTERN_GUID(IID_IBlahBlahBlah, 0xabcdef12, 0x11d2, 0xab3a, 0xc0, 0x4f, [...] ); ``` and ImportC which is compiling `blah.c` containing only a few macro