On 9/5/19 2:26 AM, Johnson, Andrew N. wrote:
> The callback.h header contains this:
>
>> /*
>> * WINDOWS also has a "CALLBACK" type def
>> */
>> #ifdef _WIN32
>> # ifdef CALLBACK
>> # undef CALLBACK
>> # endif /*CALLBACK*/
>> #endif /*_WIN32*/
>
> I think that was set up so that as long as you include the clashing windows header first (and don’t need to use their CALLBACK facilities) you should be able to include callback.h afterwards and it will hide the Windows definition.
>
> HTH, no promises though…
Sadly, not. I know this is an ordering issue. What I
don't know __where__ the issue comes from as the MSVC
error output doesn't mention any line numbers in pdbsingle.cpp.
I'm also unable to find where (all) the windows headers
define CALLBACK. A (case insensitive) google search
finds a lot of unrelated chatter about callback functions.
The mingw headers define CALLBACK in a half dozen different
headers.
I'm hoping that someone with in interest in building pva2pva
on Windows will step up to help straighten this out.
- Replies:
- Re: CALLBACK clash Benjamin Franksen via Core-talk
- References:
- CALLBACK clash Michael Davidsaver via Core-talk
- Re: CALLBACK clash Johnson, Andrew N. via Core-talk
- Navigate by Date:
- Prev:
Re: CALLBACK clash Michael Davidsaver via Core-talk
- Next:
Build failed in Jenkins: epics-example-vx68 #413 APS Jenkins via Core-talk
- Index:
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
<2019>
2020
2021
2022
2023
2024
- Navigate by Thread:
- Prev:
Re: CALLBACK clash Johnson, Andrew N. via Core-talk
- Next:
Re: CALLBACK clash Benjamin Franksen via Core-talk
- Index:
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
<2019>
2020
2021
2022
2023
2024
|