| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
| |
- Build is warning free on Linux
- Still using qmake
- Custom fragmenShaders in the cluster are not ported yet
- Qt 3D models are rendered, but the Studio 3D integration is untested
Change-Id: I0e410a932d6461ba29e7c945cb5e9750d6df8964
Reviewed-by: Dominik Holland <dominik.holland@qt.io>
Reviewed-by: Bramastyo Harimukti Santoso <bram.harimukti@gmail.com>
|
| |
|
|
|
|
|
|
|
| |
- as discussed, it is better to keep "remotesettings" than having
an intermediate name for 5.13 release
Change-Id: I37fd3f21dc5faf8dbad98b38674f6ed711617069
Reviewed-by: Kavindra Palaraja <kpalaraja@luxoft.com>
Reviewed-by: Egor Nemtsev <enemtsev@luxoft.com>
|
| |
|
|
|
|
|
|
|
|
| |
- rename the general settings into dataprovider temporarily
- split cluster interfaces to drivedata
- rename the control app into companion app
Task-number: AUTOSUITE-948
Change-Id: Ie363c4b1c31cc9d047e83c41ec9b11f8f4658be3
Reviewed-by: Egor Nemtsev <enemtsev@luxoft.com>
|
| |
|
|
|
|
|
|
|
|
|
| |
Also make sure neptune3 doesn't build at all when the ivigenerator
is not available. Otherwise the user might run into a situation
where there is a neptune3 binary but only half of the plugins
are available.
Change-Id: If0819680a87ba9d5d343fb7414ebbb3da4b87d97
Reviewed-by: Kavindra Palaraja <kpalaraja@luxoft.com>
Reviewed-by: Dominik Holland <dominik.holland@pelagicore.com>
|
|
|
We make sure to always build both type of qtivi backends. The production
backend using qtro and the simulation backend. When building neptune3
for android the production backend is not build and running it will
automatically fall back to the simulation there.
With the companion app we build the production backend to be able to
connect to a running neptune3 on a target.
Change-Id: I0aebd34ba730956566db05da3c571a425e9f61b3
Reviewed-by: Bramastyo Harimukti Santoso <bramastyo.harimukti.santoso@pelagicore.com>
|
