Databases
StackOverflow2013
Postsdbo
POUINT32 compiler version mismatch - Linking to legacy library
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POUINT32 compiler version mismatch - Linking to legacy library
    primarykey
    data
    text
    <p>I am trying to link a DLL but I am constantly running into issues with <code>UINT32</code>.</p> <p>The library is compiled against the 4.1 version of the Visual Studio compiler. The interface for my component (which was 4.1 and I am now porting to 2012) is defined with many <code>UINT32</code>s in it. In VC4.1 <code>UINT32</code> is not defined by the compiler and so it was typedefed to <code>unsigned long</code> by the programmer, but from VC6 onwards <code>UINT32</code> is defined as <code>unsigned int</code>. This makes my life hard.</p> <p>My initial reaction was to try replacing all <code>UINT32</code> in the interface with <code>unsigned long</code> and recompiling. This works as the function signatures are the same. However an <code>unsigned long</code> in 2012 is 64 bits wide... not 32 bits. This is not a problem in most cases but I foresee possible problems with flag parameters and return types.</p> <p>What I am wondering is if I have missed a more obvious solution for this. I thought of defining a different type</p> <pre><code>typedef OAM_UINT32 unsigned long //in the library typedef OAM_UINT32 unsigned int // in my component </code></pre> <p>But then the problem is going to be the same as what I have already with my two definitions of UINT32... right?</p> <p>Any help would be much appreciated.</p> <p><strong>The Problem</strong></p> <p>Client code</p> <pre><code>#include &lt;oam_if.h&gt; .... UINT32 uuid = getSomeLocalUserId(); UINT32 dwOamRetVal = dwOamGetUserDetails( uuid ); // LINK ERROR: Symbol not found </code></pre> <p>oam_if.h</p> <pre><code>UINT32 dwOamGetUserDetails( UINT32 idOfUser ); </code></pre> <p>When the library (OAM) is compiled the UINT32 value is evaluated as an <code>unsigned long</code>. When the client component is compiled, UINT32 is evaluated as <code>unsigned int</code>. The linker complains because it has a symbol defined in the OAM library for <code>dwOamGetuserDetails</code> which rakes and returns an <code>unsigned long</code>, but the client is calling a function which according to it should take an <code>unsigned int</code>. </p> <p>So while their respective inputs are unsigned numbers both 32 bits long, the signature of the function is different and the linker complains.</p> <p>The only way I can see to fix it is to define everything as <code>unsigned long</code> directly. However then OAM will be using a 32 bit long number but the client will be using a 64 bit number!</p> <p><strong>Sample of Linker Error</strong></p> <blockquote> <p>error LNK2001: unresolved external symbol "public: virtual unsigned long __thiscall Message::getCallId(void)const " (?getCallId@Message@@UBEKXZ) oam.lib(OAM_SsRequest.obj)</p> </blockquote> <p>This is actually a callback from the library to the component, so in this case it is looking for a signature that matches UINT32 as defined by the libary (unsigned long) but the component is defining an unsigned int for its callback.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USDennis
    1. USDennis
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. POUINT32 compiler version mismatch - Linking to legacy library
      1. This table or related slice is empty.
      1. VTUpMod
    1. COThe solution would be to use `uint32_t` from `<stdint>`, and finally kick Microsoft into supporting C99...
      singulars
      1. POUINT32 compiler version mismatch - Linking to legacy library
      1. USDevSolar
    2. COI assume that you would be making this change in the header for the library. My concern would be more of the CRT used in the .DLL. If it was dynamically linked to VC 4.1 you may run into serious problems with memory allocation / deallocation.
      singulars
      1. POUINT32 compiler version mismatch - Linking to legacy library
      1. USdrescherjm
    3. CODoing this "double" typedef, where one part uses unsigned long and the other unsigned int should work with no problems and decouples you from the Windows-based types. It's unclear to me why you need to continue compiling the library against such an old version of Visual Studio. Have you considered porting it forward to a more modern version of the compiler?
      singulars
      1. POUINT32 compiler version mismatch - Linking to legacy library
      1. USNik Bougalis
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload