Skip to main content

Development Notes

Search This Blog

Qt 5.14 installer requires account setup...

on Tuesday, February 25, 2020

Get link
Facebook
Twitter
Pinterest
Email
Other Apps

The latest Qt installer requires an account setup.

To work around this turn off all internet access.

Installer licence license Qt

Get link
Facebook
Twitter
Pinterest
Email
Other Apps

Comments

Post a Comment

Popular Posts

ATMEL Flip installation on Windows 10 - problem with Java VM missing.

Well this was a bit of a waste of time, I already have Java SDK installed which completely messed up the Flip installer. I tried a VM with Windows 10 but was unable to attach the atmel USB driver to the VM. So I ended up opening up the installer using 7zip as shown below: Drag the two installers out. Run jre_setup.exe then run the Atmel_appli_Install.exe. Seems to fix the issue with Java VM. Next Problem: ' atlibusbdfu.dll not found ' Install the drivers found at: C:\Program Files (x86)\Atmel\Flip 3.4.7\usb References: http://www.microchip.com/developmenttools/productdetails.aspx?partno=flip

Integrating OpenGL and QtPainter

This post builds upon the following: Using fbos instead of pbuffers in qt-5-2 QtPainter currently uses old OpenGL, in addition it also assumes that you don't change the OpenGL state. The only sensible way to deal with this is to draw into your own FBO using your own OpenGL Context, not Qt's OpenGL context. QPainter therefore requires a compatibility profile as it is currently limited to OpenGL 2.0. Qt 5.9 has a number of fixes that allow CoreProfile to work see bug report: https://bugreports.qt.io/browse/QTBUG-33535 Basically the example code builds upon what was learnt from following the above original post. It is not a complete sample. // Qt calls this to draw OpenGL void MyWidget::paintGL() { makeCurrent(); QOpenGLPaintDevice device(rect().size()); // This device could be cached - only // updating when the size of Widget // changes. QPainter

LDRA: Automating TBRun

Most of the analysis and test runs for LDRA can be automated. I am using the following batch file to automate TBRun: REM Assumes the following Directory structure: REM REM c:\projects\TCF-Test REM c:\projects\TCF-Test\Environment REM c:\projects\TCF-Test\TCF REM REM The directory `c:\projects\TCF-Test` should contain the source code, headers REM and any linker files. REM REM The directory `c:\projects\TCF-Test\Environment` should contain the REM `sysearch.dat` and `sysappvar.dat` setup for the unit tests we are running. REM REM The directory `c:\projects\TCF-Test\TCF` should contain the stripped TCF files REM we require for the unit tests we are running. REM REM The results will be in: `C:\LDRA_Workarea\TCF_TEST_SET_tbwrkfls`. REM REM Directory where source files are. set ALIAS_DIR=C:\projects\TCF-Test REM Sub-directory where stripped TCF files are set TCF_DIR=TCF REM Set name set SET_NAME=TCF_TEST_SET REM Directory w

Powered by Blogger