RE: [Xen-cim] Compilation problems

["Kohn, Rodolfo" <rodolfo.kohn@xxxxxxxxx>]

Jim,

Now you mention openWBEM, I've noted other problem with cmpimacs.h in
openWBEM: it seems to be not updated for the last versions of CMPI.
Looking at sfcb, the broker I'm using, and OpenPegasus, their cmpimacs.h
seem to be more up-to-date.

I've noted that with Instance provider functions SetInstance and
ModifyInstance (which is newer as I understand but not sure).
ModifyInstance is not found in openWBEM's cmpimacs.h header.

Thanks,
Rodolfo

>-----Original Message-----
>From: Jim Fehlig [mailto:jfehlig@xxxxxxxxxx]
>Sent: Thursday, August 16, 2007 8:35 PM
>To: Kohn, Rodolfo
>Cc: xen-cim@xxxxxxxxxxxxxxxxxxx
>Subject: Re: [Xen-cim] Compilation problems
>
>Kohn, Rodolfo wrote:
>>
>> Hi,
>>
>>
>>
>> I downloaded the xenCIM code and compiled it.
>>
>>
>>
>> I got a compilation error in file cmpilify.h because constant
EXTERN_C
>> was not recognized.
>>
>>
>>
>> I changed it by CMPI_EXTERN_C which is the one that appears in
>> cmpimacs.h header file and it compiled. I suppose this is the one
that
>> was intended to be used. Is that correct?
>>
>
>Yes.  cmpimacs.h packaged with openwbem defines EXTERN_C and not
>CMPI_EXTERN_C.  I will submit a patch to OW.
>
>> If that is correct I think cmpilify.h should include cmpimacs.h or
>> should define EXTERN_C itself.
>>
>
>Given the issue with OW and the desire to support unpatched versions I
>will change cmpilify.h to include cmpimacs.h _and_ add
>
>#ifndef CMPI_EXTERN_C
>  #ifdef __cplusplus
>    #define CMPI_EXTERN_C extern "C"
>  #else
>    #define CMPI_EXTERN_C
>  #endif
>#endif
>
>FYI, I have not compiled/run the providers under pegasus in some time
>(several months).  Good luck and let us know if you have any issues.
>
>Thanks for the report.
>Jim

_______________________________________________
Xen-cim mailing list
Xen-cim@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-cim