Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Remember that when you link against a static LIB, by default the linker is only pulling in the functions, classes, and data that the client (which in this case is your <strong>DLL</strong>) actually references.</p> <p>So what happens is this:</p> <ol> <li>You build your static LIB, and that's fine. This LIB is 100% valid.</li> <li>You now build your static DLL around the original binary LIB. It pulls in <em>only the stuff that it actually references</em>. It doesn't pull in the <em>entire class definition</em> which is what it needs to do. This DLL, though it builds, is invalid.</li> <li>A client then uses the DLL, and expects to see a complete binary definition for the exported class, because that's what the client sees in the accompanying header file.</li> <li>However the class has only been <em>partially</em> imported, and this is why you're getting those link errors.</li> </ol> <p>To fix:</p> <ul> <li>If you're able to, don't build your DLL off your static LIB. Build your DLL off the original source code. And build your static LIB off the original source code.</li> <li>Otherwise you can possibly fiddle with linker settings but I strongly recommend option 1 above. Note that OPT:NOREF won't work here as OPT:NOREF has no effect on static LIBs.</li> </ul> <p>What wont't fix it:</p> <ul> <li>High-level linker tweaks like OPT:NOREF, anything involving COMDATs, etc. If you want those functions present, you have to make sure they're referenced, either by referencing them, or by telling the linker explicitly, "hey, this Symbol X is referenced".</li> </ul> <p>As a side note:</p> <ul> <li>Anytime I build a DLL or LIB, I build <em>both</em> a DLL and a LIB, using exactly the technique you're using. Having a single code base that can generate either a DLL or a LIB by toggling a setting is ideal. But building a DLL off of a (binary) static LIB when you own the source code for both... I'm having a hard time imagining when such a scenario would be necessary.</li> </ul>
    singulars
    1. This table or related slice is empty.
    1. PONot all symbols of an DLL-exported class is exported (VS9)
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USSwingline Rage
    1. USSwingline Rage
    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. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COYou are right and I forgot to add that info to the question. I added a note about my linker settings that so that unreferenced symbols will not be removed. And the motivation why I don't build a DLL for each of the static libraries; I can't since they cross-reference each other.
      singulars
      1. PO
      1. USmandrake
    2. COJust a note (also added to my answer) that OPT:NOREF has no effect on static LIBs anyway. It defeats the entire purpose of having a static LIB. This makes sense. Just not very much.
      singulars
      1. PO
      1. USSwingline Rage
    3. COThe OPT:NOREF setting applied to the DLL linker setting not the static lib. But it should not matter. If a symbol is marked to export the linker would not optimize it away.
      singulars
      1. PO
      1. USmandrake
 

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