Re: [openssl.org #1684] bug: name collisionwith Windows SDK - Openssl

This is a discussion on Re: [openssl.org #1684] bug: name collisionwith Windows SDK - Openssl ; On Mon, Jun 02, 2008, Stefan.Neis@t-online.de wrote: > > - > > typedef struct ocsp_response_st OCSP_RESPONSE; > > > > > > > > within openssl/ossl_typ.h collides with > > > > > > > > #define OCSP_RESPONSE ((LPCSTR) 67) ...

+ Reply to Thread
Results 1 to 3 of 3

Thread: Re: [openssl.org #1684] bug: name collisionwith Windows SDK

  1. Re: [openssl.org #1684] bug: name collision with Windows SDK

    On Mon, Jun 02, 2008, Stefan.Neis@t-online.de wrote:

    >
    > -
    > > typedef struct ocsp_response_st OCSP_RESPONSE;
    > >
    > >
    > >
    > > within openssl/ossl_typ.h collides with
    > >
    > >
    > >
    > > #define OCSP_RESPONSE ((LPCSTR) 67)
    > >
    > >
    > >
    > > within WinCrypt.h, a windows header file (Microsoft Windows SDK 6.0A).
    > > There are work-arounds, but the compiler errors led to a few hours of
    > > tracking it down, which, I'm sure, no one else wishes to experience.

    >
    > Actually, I just had a very similar experience while trying to compile
    > Openssl
    > with mingw-w64. I had to add a couple of "#undef this" and "#undef that"
    > within
    > three openssl headers including "windows.h" (which in turn ended up
    > including
    > wincrypt.h). Anyway, this namespace polution by windows headers is a
    > real problem.
    >


    A few of these are include in crypto/ossl_typ.h what new one's did you have to
    use?

    Steve.
    --
    Dr Stephen N. Henson. Email, S/MIME and PGP keys: see homepage
    OpenSSL project core developer and freelance consultant.
    Homepage: http://www.drh-consultancy.demon.co.uk
    __________________________________________________ ____________________
    OpenSSL Project http://www.openssl.org
    Development Mailing List openssl-dev@openssl.org
    Automated List Manager majordomo@openssl.org


  2. Re: [openssl.org #1684] bug: name collisionwith Windows SDK


    -
    > typedef struct ocsp_response_st OCSP_RESPONSE;
    >
    >
    >
    > within openssl/ossl_typ.h collides with
    >
    >
    >
    > #define OCSP_RESPONSE ((LPCSTR) 67)
    >
    >
    >
    > within WinCrypt.h, a windows header file (Microsoft Windows SDK 6.0A).
    > There are work-arounds, but the compiler errors led to a few hours of
    > tracking it down, which, I'm sure, no one else wishes to experience.


    Actually, I just had a very similar experience while trying to compile
    Openssl
    with mingw-w64. I had to add a couple of "#undef this" and "#undef that"
    within
    three openssl headers including "windows.h" (which in turn ended up
    including
    wincrypt.h). Anyway, this namespace polution by windows headers is a
    real problem.

    Regards,
    Stefan


    __________________________________________________ ____________________
    OpenSSL Project http://www.openssl.org
    Development Mailing List openssl-dev@openssl.org
    Automated List Manager majordomo@openssl.org


  3. Re: [openssl.org #1684] bug: name collision with Windows SDK

    Stefan.Neis@t-online.de wrote:
    > -
    >> typedef struct ocsp_response_st OCSP_RESPONSE;
    >>
    >>
    >>
    >> within openssl/ossl_typ.h collides with
    >>
    >>
    >>
    >> #define OCSP_RESPONSE ((LPCSTR) 67)
    >>
    >>
    >>
    >> within WinCrypt.h, a windows header file (Microsoft Windows SDK 6.0A).
    >> There are work-arounds, but the compiler errors led to a few hours of
    >> tracking it down, which, I'm sure, no one else wishes to experience.

    >
    > Actually, I just had a very similar experience while trying to compile
    > Openssl
    > with mingw-w64. I had to add a couple of "#undef this" and "#undef that"
    > within
    > three openssl headers including "windows.h" (which in turn ended up
    > including
    > wincrypt.h). Anyway, this namespace polution by windows headers is a
    > real problem.


    You may contact mingw-w64 project and to inform them that in MSDN
    samples the code include first and after this
    explicitly.

    Roumen
    __________________________________________________ ____________________
    OpenSSL Project http://www.openssl.org
    Development Mailing List openssl-dev@openssl.org
    Automated List Manager majordomo@openssl.org


+ Reply to Thread