Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I'm not completely sure of what your "specific" case is.</p> <p>If your "media player" is intended for a well know unique client (or small set of clients) who will update all the media player at once or any given plugin at once under your complete supervision then I'll go for static libraries.</p> <p>If that's not the case I'll go for dynamic libraries. Optimizations are good but are not as good as customer/user satisfaction. There's nothing worse than updating your xxx library to the latest version and that all the sudden things just stop to work. If you haven't control over when and how updates are made be as flexible as you can.</p> <p><strong>Response to the comment:</strong></p> <p>Usually dynamic libraries are backwards compatible for minor release versions while static linking might be dependent on a concrete version and break if you try to link it to another release. With Dynamic Linking your program might even work as long as the calls you use doesn't change while static linking might depend on a change of the function offset in the library.</p> <p>For example, static libraries might be loaded in runtime into the address space of the process at an static offset. Of course, knowing this offset allows for certain optimizations but if you update the library then either you update ALL the plugins using that library or probably the unupdated plugins won't work (as function offset might very well have changed).</p> <p>I assume you load them in runtime, although if that can be named static linking is in the air, in any other case you will just have the library on each plugin and there will be no "sharing".</p>
    singulars
    1. This table or related slice is empty.
    1. POStatic vs. shared libraries for a media player
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USJorge Córdoba
    1. USJorge Córdoba
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POStatic vs. shared libraries for a media player
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    1. COIt's an open-source player. How can dynamic libraries help with updating? If using static libraries, how can updating your "pdating your xxx library to the latest version" break my application? I'd say the other way around.
      singulars
      1. PO
      1. USCMircea
    2. COStatic libraries are just as backwards compatible as shared ones, since they're generated from the same source. All you need to do to use newer versions is to recompile the libraries and relink against them - not an issue really. I don't see how the address space offset can affect me since the plug-ins will have a callback design (that is they depend on the application telling them to do stuff) and the only common dependency will be Qt. Maybe I'll export all the generic application code in a shared library so it can be used by plug-ins, but I don't find that really useful in this case.
      singulars
      1. PO
      1. USCMircea
 

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