Age | Commit message (Collapse) | Author |
|
Now that we have -fuse-cxa-atexit static dtors for modules are called as
they should be.
|
|
With -fvisibility=hidden it's hidden anyway.
|
|
|
|
|
|
It's automatic now.
|
|
|
|
Avoid macros when able to allow for scope control. Macros shove
everything inside the parent scope. The lone remaining macro needs to be
there since functions allow for a fixed amount of parameters.
Link against dinput automatically since LTO will remove it if it's not
needed anyway.
Rift trackers don't presently need access to ${project}-all etc. so
don't expose them through opentrack_rift_boilerplate yet.
|
|
|
|
|
|
To name position tracking "translation" per se is unusual outside of
geometry and hard sciences in general. Clear things up.
Reported-by: @MathijsG
Closes #359
|
|
|
|
In particular PT's calibration interval was 10 Hz which is too much by
far. Make both 4 Hz.
Issue: #344
|
|
All platforms work as expected after the shared library loading changes.
|
|
|
|
There's no need for the identifier to be exposed.
|
|
We don't have a virtual dtor and we don't want a vtable.
|
|
|
|
Given the symbol visibility rules as verified with nm(1), QLibrary is
sufficient. We don't need the RTLD_DEEPBIND "load hint" for Linux either
as per the same visibility rules.
This is untested on Apple but should be soon.
|
|
Remove linker script usage. I'm worried about the potential interaction
with shared libraries' _fini symbol for global destruction.
Further, add -fuse-cxa-atexit in order to run the global destructors to
begin with. This works on LLVM and GNU. MSVC doesn't export symbols by
default.
|
|
|
|
|
|
libaruco doesn't clamp the min/max sizes but throws an exception.
Reported-by: @duamutefmc
Data-by: @Emton
Issue: #329
Closes #329
|
|
This does the check before compiler tests, spewing less crapola into the
source directory.
|
|
|
|
By @drdanilov21. We'll likely need it in the future.
|
|
LoadStringFromFile result is always AnsiString.
I'm using the Unicode InoSetup version so paging @ph0b.
|
|
It's used in the win32 installer.
This reverts commit 3252beca3aa20fe5183a13029db831e4e121f6dc.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
We no longer have this recurring problem since I enabled
ignoring executable bit changes on the Windows workstation.
|
|
For my convenience.
|
|
Previous disallowed binding an already-bound key on Unix since Qxt
doesn't pass through bound keys unlike the Windows implementation.
Refactor some common code.
The Windows implementation isn't even compile-tested.
|
|
Issue: #349
Valgrind: yes
|
|
|
|
|
|
Committer shouldn't push so fast to get a chance to rebase.
Closes #356
|
|
Previous commit fixed only the case with one perpendicular axis of
rotation with the rest fixed at origin. This one works with all three
degrees of freedom enabled.
Reported-by: @MathijsG
Issue: #356
|
|
|
|
74d9f5e31428ef362033a63c10b781d943c5e5a5 skipped some of intermediate
computations.
|
|
We actually need to use a float intermediate type lest the value gets
truncated.
|
|
With a very small denominator in barycentric coords formula we get a
dissociated octopus that took PCP and LSD in one sitting.
A dead Octopus is just a bunch of blue spheres.
IOW, in division with too small a denominator operand the results are
numerically unstable.
This is done in the constructor in a convoluted way as to avoid
branching during calculating for each pixel.
Issue: #356
Reported-by: @MathijsG
|
|
This reverts commit 546cfb5ad52dcfe1421d1af5e7baeada588ac735.
@MathijsG points out that some users have red LEDs, not uniform white.
Issue: #355
|
|
The confusion stems from the max slider value. It's 255, not 100 as is
the default. Max pixel count change to 20 was confused as we'll counting
area and not radius here. Taking into account that the value was divided
by 100 previously, it's bit less than the previous one but not as
confused as then.
Reported-by: @MathijsG
Issue: #355
|
|
|
|
|
|
|