Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Qt Creator doesn't know how to expose different libraries to your projects. It's developer's duty. Dependency ensures only that mentioned projects are already built before building your main project.</p> <p>Your real concern was using Qxt without proper installation. Assuming that <code>configure</code> have been run and <code>libqxt</code> have been built (using Qt Creator or manually via <code>qmake</code>+<code>make</code>), my solution is adding following snippet (with obvious QXT_DIR customization) to .pro file:</p> <pre><code>QXT_DIR = $${IN_PWD}/../libqxt-0.5.1 LIBS += -L$${QXT_DIR}/deploy/libs INCLUDEPATH += $${QXT_DIR}/deploy/include for(module, QXT) { MODNAME = $$upper($$replace(module, "(.).*", "\1"))$$replace(module, "^.", "") INCLUDEPATH += $${QXT_DIR}/deploy/include/Qxt$${MODNAME} INCLUDEPATH += $${QXT_DIR}/src/$${module} win32:CONFIG(debug, debug|release):MODNAME = $$join(MODNAME,,,d) LIBS += -lQxt$${MODNAME} } </code></pre> <p>Unfortunately I'm not sure whether it works in complex projects.</p> <p>By default Qxt is built in release mode, but Qt Creator uses debug mode and it leads to broken binaries of projects depending on Qxt under Windows. You have to switch your project to release mode or build Qxt in debug mode (run <code>configure -debug</code> and rebuild Qxt).</p> <p>Last thing: In Windows you won't be able to run your project from Qt Creator even if you successfully build it. You must copy needed <code>Qwt*.dll</code> files (use the <code>d</code>-suffix versions if you're in debug mode) from <code>libqxt-0.5.1/deploy/libs</code> to <code>your_project/(release|debug)</code> directory .</p>
    singulars
    1. This table or related slice is empty.
    1. POLibqxt under Qt Creator
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USprzemoc
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POLibqxt under Qt Creator
      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
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COThanks for your answer, it worked.
      singulars
      1. PO
      1. USDario Castañé
    2. CO+1 thanks for the conf! May I ask you what this line does: MODNAME = $$upper($$replace(module, "(.).*", "\1"))$$replace(module, "^.", "") . Thanks again!
      singulars
      1. PO
      1. USViet
    3. CO@Viet: Qxt uses lowercase for module names provided in `QXT` variable , but CamelCase for library names and some included directories. This is analogous to Qt. Mentioned line sets `MODNAME` to CamelCase version of `module` using simple functions (`upper()` is undocumented one, self-evident though) and regular expressions.
      singulars
      1. PO
      1. USprzemoc
 

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