qbs | A Go ORM | SQL Database library

From qbs 1.19 on, this should work transparently by just setting "install: true" on the StaticLibrary item (as it already does for non-multiplexed products). See https://codereview.qt-project.org/c/qbs/qbs/+/339928 for how multiplexing is handled there. But if your workaround does the trick, you could just as well keep using it until then.

I assume this is for a custom command.

If you are only using Ninja try JOB_POOLS:

"Specify a pool for the Ninja generator. Incompatible with USES_TERMINAL, which implies the console pool. Using a pool that is not defined by JOB_POOLS causes an error by ninja at build time."

TL;DR: Use cmake. Forget about qbs and qmake.

Whenever I create a new project - doesn't matter whether its with qbs, qmake, or cmake - the project structure/ folder is lacking the '.pro' file.

A qmake project will have the .pro file, since that's the project file for qmake. Maybe you're looking in a wrong place? A qbs project will have a .qbs file, since that's what qbs uses. A cmake project will have CMakeLists.txt, since that's what cmake uses. It all works for me.

I'm just confused by all these guides stating that I have to add QT += widgets sql in the .pro file.

Those guides only apply when you use qmake, since .pro are qmake project files.

I suggest that you use cmake, as qbs is abandoned now, and there's no benefit to using Qt-specific qmake over the widely supported and continuously developed cmake.

Qt documentation covers the basics of how to use cmake to build Qt projects.

Qt support is provided natively by cmake, and it thus provides a comprehensive reference page.

This is my exact specialty! In general, if you want a constraint to depend on the choice for particular variables (e.x. which QB variable is picked), you'll need to set up a new constraint for each possible choice, in a somewhat clever way to ensure that that constraint only does anything when that variable was chosen.

1. Stack at least n players with your QB: You're going to have a new constraint for each QB in your player pool. The constraint will look like this:

Not sure if you just want the EPA column colored, if you want the entire row remove the subset argument from the last line.

Using uiOutput with rendering inputs in server, is the way to go.

I'm not testing the whole app, but you're assuming (incorrectly) that all of your inputs are numeric. Try the following:

My guess is that you are using an x86 compiler and an x64 Qt, which will not work. How did you set up your profile?

The object under construction does not have any association with QJSEngine yet. So you can only do one of the following alternatives:

1. Store the engine instance in a static variable if you can ensure that there is only ever one instance of QJSEngine in your whole application.
2. Store the engine instance in a thread-local variable (QThreadStorage) if you can ensure that there is only one engine per thread.
3. Set the current active engine in the current thread right before evaluating your JS code since. This might be the easiest and yet robust solution.
4. Retrieve the engine from a QJSValue parameter.
5. Implement a JS wrapper for the constructor

Solution 4.: Passing the engine implicitly via a QJSValue parameter.

I assume that your throwing constructor always has a parameter. QJSValue has a (deprecated) method engine() which you then could use. You can replace any parameter in a Q_INVOKABLE method with QJSValue instead of using QString and friends.