Bitpie钱包官方版|aqt

作者: Bitpie钱包官方版
2024-03-07 17:04:10

「知乎·应用工程」aqtinstall使用手册——开始入门(Windows) - 知乎

「知乎·应用工程」aqtinstall使用手册——开始入门(Windows) - 知乎首发于拉克伍德大学超临界地热研究切换模式写文章登录/注册「知乎·应用工程」aqtinstall使用手册——开始入门(Windows)石中居士​​吉林大学 地质资源与地质工程博士后参考拉克伍德大学 地球探测科学与技术学院(原朗斯普林地质学院)资助

地球物理局 超临界地热资源研究中心

地球物理局 地震波动力学研究所

地球物理局 多物理场耦合仿真中心

aqtinstall临时工作组

说明:

# 青色背景公式表示本章节未引用但在之前章节引用过、或者本章节已经引用过一次但是行文相隔比较长的公式

# 黄色背景公式表示本章节的重要公式

# 写作基于最新的“一撸到底”的原则,适应信息流阅读习惯,确保思路连贯性,尽量减少读者上下滑动阅读的成本

# 引文采用美国心理学会(APA)格式。文中参考文献第一次出现时,列出引用数量“,XX+”,以及顶级期刊名称开始入门aqt是一个可用于安装Qt、模块、与Qt相关的工具、源代码、文档和示例的工具,可从Index of / 获取。在运行aqt之前,您需要告诉aqt您希望它安装的具体内容。本节文档旨在引导您了解aqt可用的软件包,以便告诉aqt您想安装什么。  请注意,每个aqt子命令都有一个--help选项;如果你遇到困难,请使用它!安装Qtaqt的一般用法如下:aqt install-qt ( | ) []如果您使用pip安装了aqt,则可以使用命令脚本aqt运行它,但在某些情况下,您可能需要以python -m aqt的方式运行它。某些较旧的操作系统可能需要指定Python版本3,例如:python3 -m aqt。  要使用aqt安装Qt,您需要告诉aqt四件事:主机操作系统(windows、mac或linux)目标SDK(桌面、安卓、iOS或Winrt)要安装的Qt版本目标架构  请记住,Qt for IOS仅适用于Mac OS,而Qt for WinRT仅适用于Windows。  要查找可用的Qt版本,可以使用aqt list-qt命令。该命令将打印Windows桌面可用的所有Qt版本:$ aqt list-qt windows desktop

5.9.0 5.9.1 5.9.2 5.9.3 5.9.4 5.9.5 5.9.6 5.9.7 5.9.8 5.9.9

5.10.0 5.10.1

5.11.0 5.11.1 5.11.2 5.11.3

5.12.0 5.12.1 5.12.2 5.12.3 5.12.4 5.12.5 5.12.6 5.12.7 5.12.8 5.12.9 5.12.10 5.12.11

5.13.0 5.13.1 5.13.2

5.14.0 5.14.1 5.14.2

5.15.0 5.15.1 5.15.2

6.0.0 6.0.1 6.0.2 6.0.3 6.0.4

6.1.0 6.1.1 6.1.2

6.2.02023-07-19 命令行(Git Bash)请注意,版本号是排序的,按次要版本号分组,并以单个空格字符分隔。所有aqt list-qt命令的输出都是为了方便你编写使用aqt list-qt输出的程序。  由于aqt list-qt命令直接查询 Index of / 上的 Qt 下载资源库,因此该命令的结果总是准确的。“可用Qt版本”wiki页面最后一次修改是在过去的某个时间点,因此可能是最新的,也可能不是。  既然我们已经知道Qt有哪些版本,那就选择6.2.0版吧。  接下来,我们需要找出Windows桌面版Qt 6.2.0的可用架构。为此,我们可以使用带有--arch标志的aqt list-qt:$ aqt list-qt windows desktop --arch 6.2.0

win64_mingw81 win64_msvc2019_64 win64_msvc2019_arm64 wasm_322023-07-19 命令行(Git Bash)请注意,这只是“可用Qt版本”wiki页面所列架构的一小部分。如果我们需要使用的架构不在此列表中,我们可以使用“可用Qt版本”wiki页面来大致了解哪些版本支持我们想要的架构,然后使用aqt list-qt来确认该架构是否可用。  假设我们想安装架构为win64_mingw81的Qt 6.2.0。 我们需要的安装命令是:$ aqt install-qt windows desktop 6.2.0 win64_mingw81  mk比方说,我们想在Qt 6.2的下一个版本推出后立即安装它。我们可以使用SimpleSpec来代替显式版本:$ aqt install-qt windows desktop 6.2 win64_mingw81外部7-zip解压缩器  默认情况下,aqt会使用与aqt同时安装的py7zr来解压存储在Qt代码库中的7zip压缩包。 你可以使用-E 或--external标志指定另一个7zip命令路径。例如,你可以利用以下命令,在Windows桌面上使用7-zip: $ aqt install-qt windows desktop 6.2.0 gcc_64 --external 7za.exe  在Linux上,可以使用此命令指定p7zip,它是7-zip的Linux端口,通常利用以下命令默认安装:$ aqt install-qt linux desktop 6.2.0 gcc_64 --external 7z更改输出目录  默认情况下,aqt会将所有Qt软件包安装到当前工作目录下的.///子目录中。例如,如果我们用arch win64_mingw81为Windows桌面安装Qt 6.2.0,它将被安装在./6.2.0/win64_mingw81目录中。  如果希望将其安装到其他位置,则需要使用-O或--outputdir标志。该选项也适用于所有其他以aqt install-开头的子命令。  要安装到C:\Qt(标准gui安装程序使用的默认目录),可以使用此命令: $ mkdir Qt

$ aqt install-qt --outputdir c:\Qt windows desktop 6.2.0 win64_mingw812023-07-19 命令行(Git Bash)安装模块  假设我们需要在Windows桌面上为Qt 5.15.2安装一些模块。首先,我们需要找出这些模块的名称,这可以使用带有--modules标志的aqt list-qt来完成。每个版本的Qt都有不同的模块列表,适用于不同的主机操作系统/目标 SDK/架构组合,因此我们需要向aqt list-qt提供这些信息:$ aqt list-qt windows desktop --modules 5.15.2 win64_mingw81

qtcharts qtdatavis3d qtlottie qtnetworkauth qtpurchasing qtquick3d

qtquicktimeline qtscript qtvirtualkeyboard qtwebengine qtwebglplugin2023-07-19 命令行(Git Bash)  比方说,我们想在安装之前了解更多关于这些模块的信息。为此,我们可以使用--long-modules标志:$ aqt list-qt windows desktop --long-modules 5.15.2 win64_mingw81

Module Name Display Name

======================================================================

debug_info Desktop MinGW 8.1.0 64-bit Debug Information Files

qtcharts Qt Charts for MinGW 8.1.0 64-bit

qtdatavis3d Qt Data Visualization for MinGW 8.1.0 64-bit

qtlottie Qt Lottie Animation for MinGW 8.1.0 64-bit

qtnetworkauth Qt Network Authorization for MinGW 8.1.0 64-bit

qtpurchasing Qt Purchasing for MinGW 8.1.0 64-bit

qtquick3d Qt Quick 3D for MinGW 8.1.0 64-bit

qtquicktimeline Qt Quick Timeline for MinGW 8.1.0 64-bit

qtscript Qt Script for MinGW 8.1.0 64-bit

qtvirtualkeyboard Qt Virtual Keyboard for MinGW 8.1.0 64-bit

qtwebglplugin Qt WebGL Streaming Plugin for MinGW 8.1.0 64-bit2023-07-19 命令行(Git Bash)2023-07-19 命令行(Git Bash)请注意,如果您的终端宽于95个字符,该命令将在右侧额外列中显示发布日期和大小。如果您尝试执行此命令,会发现debug_info的安装量为5.9千兆字节。  此外,请注意“显示名称”(Display Name)表明了模块的编译器。在本例中,对于win64_mingw81架构,您很可能希望使用MinGW 8.1.0 64-bit编译器。下面是该命令在使用名称含糊的win64_mingw架构时的打印结果:$ python -m aqt list-qt windows desktop --long-modules 6.2.4 win64_mingw

Module Name Display Name

=======================================================================

debug_info Desktop MinGW 11.2.0 64-bit debug information files

qt3d Qt 3D for MinGW 11.2.0 64-bit

qt5compat Qt 5 Compatibility Module for MinGW 11.2.0 64-bit

qtactiveqt Qt 3D for MinGW 11.2.0 64-bit

qtcharts Qt Charts for MinGW 11.2.0 64-bit

...  您可以在安装工具部分了解如何安装MinGW 8.1.0 和11.2.0。  假设我们要安装qtcharts和qtnetworkauth。我们可以在aqt install-qt命令中使用-m标志。该标志接收至少一个模块的名称作为参数:$ aqt install-qt windows desktop 5.15.2 win64_mingw81 -m qtcharts qtnetworkauth2023-07-19 命令行(Git Bash)  如果我们想安装所有可用的模块,可以使用all关键字:$ aqt install-qt windows desktop 5.15.2 win64_mingw81 -m all  还记得aqt list-qt命令是用来编写脚本的吗?安装Qt 5.15.2可用的所有模块的一种方法是将aqt list-qt的输出发送到aqt install-qt,就像这样:$ aqt install-qt windows desktop 5.15.2 win64_mingw81 \

-m $(aqt list-qt windows desktop --modules 5.15.2 win64_mingw81)  运行该命令需要Unix风格的shell,或至少需要Windows上的git-bash。xargs与此命令的对应关系留待读者自行解决。  如果想安装所有可用模块,最好使用all关键字,如上文所述。本脚本示例旨在让您了解如何完成更复杂的任务。也许你想安装除qtnetworkauth之外的所有模块;您可以写一个脚本,从aqt list-qt的输出中移除 qtnetworkauth,然后将其导入aqt install-qt。 这个练习留给读者自己完成。安装工具  让我们使用aqt list-tool命令来了解Windows桌面有哪些可用工具:$ aqt list-tool windows desktop

tools_vcredist

...

tools_qtcreator

tools_qt3dstudio

tools_openssl_x86

tools_openssl_x64

tools_openssl_src

tools_ninja

tools_mingw

tools_mingw90

tools_ifw

tools_conan

tools_cmake2023-07-19 命令行(Git Bash)  让我们看看tools_mingw中有哪些工具变体:$ aqt list-tool windows desktop tools_mingw

qt.tools.mingw47

qt.tools.win32_mingw48

qt.tools.win32_mingw482

qt.tools.win32_mingw491

qt.tools.win32_mingw492

qt.tools.win32_mingw530

qt.tools.win32_mingw730

qt.tools.win32_mingw810

qt.tools.win64_mingw730

qt.tools.win64_mingw8102023-07-19 命令行(Git Bash)  这就为我们提供了一个可以使用aqt install-tool安装的列表。让我们使用-l或--long标志查看更多细节:$ aqt list-tool windows desktop tools_mingw -l

Tool Variant Name Version Release Date

=============================================================

qt.tools.mingw47 4.7.2-1-1 2013-07-01

qt.tools.win32_mingw48 4.8.0-1-1 2013-07-01

qt.tools.win32_mingw482 4.8.2 2014-05-08

qt.tools.win32_mingw491 4.9.1-3 2016-05-31

qt.tools.win32_mingw492 4.9.2-1 2016-05-31

qt.tools.win32_mingw530 5.3.0-2 2017-04-27

qt.tools.win32_mingw730 7.3.0-1-202004170606 2020-04-17

qt.tools.win32_mingw810 8.1.0-1-202004170606 2020-04-17

qt.tools.win64_mingw730 7.3.0-1-202004170606 2020-04-17

qt.tools.win64_mingw810 8.1.0-1-202004170606 2020-04-172023-07-19 命令行(Git Bash)  如果您的终端宽于95个字符,则aqt list-tool还会打印每个工具的“显示名称”和“说明”;如果终端窄于95个字符,则无法以可读方式显示此表。  请注意,tools_mingw90工具似乎标错了:$ aqt list-tool windows desktop tools_mingw90 -l

Tool Variant Name Version Release Date

=============================================================

qt.tools.win64_mingw900 9.0.0-1-202203221220 2022-03-22

$ aqt list-tool windows desktop tools_mingw90 -l

Tool Variant Name Version Release Date Display Name Description

============================================================================================================

qt.tools.win64_mingw900 9.0.0-1-202203221220 2022-03-22 MinGW 11.2.0 64-bit MinGW-builds 11.2.0

64-bit toolchain with

gcc 11.2.02023-07-19 命令行(Git Bash)tools_mingw90的“缩小显示范围”截去了表格中显示软件包内容的两列:MinGW 11.2.0 64-bit。如果您使用的是Qt 6.2.2+的win64_mingw架构,那么这可能就是您要安装的编译器(参见long_modules解释)。  现在让我们使用aqt install-tool命令来安装mingw。该命令接收四个参数:主机操作系统(windows、mac或linux)目标 SDK(桌面、安卓、ios或Winrt)工具名称(本例中为tools_mingw)(可选)工具变体名称。当我们运行aqt list-tool并填入tool name参数时,就会看到这些名称的列表。  要安装mingw,可以使用此命令(请勿使用):aqt install-tool windows desktop tools_mingw # please don't run this!  使用该命令将安装tools_mingw中的所有工具变体;在这种情况下,你将安装同一工具的10个不同版本。对于某些工具,如qtcreator或ifw,这样做是合适的,因为每个工具变体都是不同的程序。不过,对于mingw和vcredist这样的工具,使用aqt list-tool查看有哪些可用的工具变体,然后只安装感兴趣的工具变体会更合理,就像这样:$ aqt install-tool windows desktop tools_mingw qt.tools.win64_mingw7302023-07-19 命令行(Git Bash)  请注意,aqt install-tool无法识别与每个工具相关的installscript.qs。当您使用标准 gui 安装程序安装这些工具时,安装程序可能会使用installscript.qs脚本对您的系统进行额外更改。如果您需要进行这些更改,则应自行负责,因为aqt无法运行此脚本。安装Qt压缩包子集【高级】引 言  您可能已经注意到,默认情况下,aqt install-qt会安装大量您可能需要也可能不需要的压缩包(archives),而且典型的安装可能会占用超过必要的磁盘空间。如果你安装了debug_info模块,它可能已经安装了超过1 gigabyte的数据。本节将帮助您减少Qt安装的占用空间。注意:小心使用--archives标记;标记为高级是有原因的!很容易误用该命令,导致Qt安装缺少所需的组件。除非你知道自己在做什么,否则不要使用它!最小Qt安装  通常,当你运行aqt install-qt时,程序会打印一长串正在下载、解压缩和安装的压缩包,包括qtbase、qtmultimedia、qt3d和~25个其他项目。我们可以使用--archives标记来选择实际安装哪些压缩包。--archives标记只能影响两个模块:基本Qt安装和debug_info模块。注意:在本文档中,“模块”、“压缩包”和“基本Qt安装”指的是不同的东西,在此进行定义:压缩包(archives):在这里,压缩包是用7zip算法压缩的文件包。它以扩展名为.7z的文件形式存在于磁盘驱动器上。模块(modules):Qt库将档案组织成模块。一个模块包含一个或多个存档。基本Qt安装:顾名思义,这只是另一个包含20-30个压缩包的模块。本文档将其称为基本Qt安装而非模块有几个原因:(1)aqt install-qt默认安装此模块。(2)不能使用aqt install-qt --modules指定此模块。(3)aqt list-qt --modules命令无法打印此模块。(4)aqt会转换Qt库中的模块名称,使其更易于读写。如果使用相同的规则转换基本Qt安装的名称,该名称将是空的。  基本Qt安装模块的全称通常是qt.qt6.620.gcc_64。qtcharts模块的全称可以是 qt.qt6.620.qtcharts.gcc_64。要读写一个包含20个前缀为qt.qt6.620.、后缀为.gcc_64的模块列表是很困难的,因为这些部分都是重复的,没有意义。只有qtcharts部分有用。  假设我们要使用gcc_64架构为Linux桌面安装Qt 5.15.2。qtbase压缩包包含了可正常工作的Qt安装所需的最基本信息,我们可以使用--archives标记单独安装它:$ aqt install-qt linux desktop 5.15.2 --archives qtbase2023-07-19 命令行(Git Bash)这次,aqt install-qt将只安装一个存档,即qtbase,而不是默认安装的~27个压缩包。编辑于 2023-07-19 10:34・IP 属地吉林aqtinstall​赞同 3​​添加评论​分享​喜欢​收藏​申请转载​文章被以下专栏收录拉克伍德大学超临界地

Technology - AQT | ALPINE QUANTUM TECHNOLOGIES

Technology - AQT | ALPINE QUANTUM TECHNOLOGIES

Skip to content

HOMEABOUTTECHNOLOGYQC SYSTEMSPINE System – memory lifetimePINE System – Quantum VolumePINE System – fault-tolerantPINE System – 20 qubit controlPINE System – 19-inch rackQC MODULESBEECH – Laser stabilizationPINE TRAP – High-performancePINE SET-UP – for quantumROWAN – Full control of laser lightRESOURCESNews & EventsMedia & PressCAREERCONTACT

Technologyadmin2020-03-23T17:08:58+01:00

::: Technology

The founders of AQT have been the first persons to realize a controlled-NOT gate operation – the building block for general-purpose quantum computers. Since then, ion-trap quantum computers are at the forefront of quantum technology development: from atomic clocks to quantum simulators, to universal quantum computers.

Using electric fields, single charged atoms are trapped inside vacuum chambers.Each ion represents a quantum bit, or qubit.Each qubit is manipulated and measured by precisely timed laser pulses.Achievements:

Realization of a scalable Shor algorithm [see here]

Topologically encoded quantum error correction [see here]

Quantum chemistry calculations [see here]

World record on 14-particle entanglement [see here]

and many more …

Beyond state-of-the-art applications such as factoring, simulations on high-energy physics or quantum-chemistry, AQT ion-trap technologies offer a clear roadmap to large-scale quantum computers: from scalable ion-trap processors to photonic networks connecting quantum computers.

Alpine Quantum Technologies GmbHImprintPrivacy & GDPRFollow us

Alpine Quantum Technologies GmbH

Imprint

Privacy & GDPR

Page load link

We use cookies and analysis software in order to design our website as user-friendly as possible. By proceeding, you accept using this service. More information

Ok

Go to Top

AQT - Advanced query tool - database query tool for DB2, Oracle, SQL Server, MySQL

AQT - Advanced query tool - database query tool for DB2, Oracle, SQL Server, MySQL

Home

Features

Get AQT

Pricing

Support

Download AQT

Advanced Query Tool is a fast and powerful multi-database query tool

Try it for free

AQT talks to all your databases, fast

AQT uses a native ODBC interface which runs reliably and efficiently against databases of all sizes.

AQT is mature and feature rich

AQT ships with an extensive query environment and a wide range of DBA and developer tools.

AQT is easy to use

AQT provides a simple, clean and responsive interface which helps you get your job done fast and efficiently.

One app for all your databases

No other product has AQT's degree of multi-database support. Configured individually for over 30 different database types, AQT is a specialized product for every database. One tool, one price, for all your databases. In addition, AQT has excellent cross-database features. Load data from Oracle into DB2 z/OS! Compare tables between Sybase and MySQL!

Simple and easy to use

AQT has a simple clean and intuitive interface. Novices find AQT easy to learn; experts enjoy the unprecedented visibility of their databases. Sites with multiple databases appreciate having a single interface for all their databases.

Feature Rich

AQT is packed full of features. AQT will make your life easier no matter whether you are developing reports, managing your database farm, writing stored procedures, loading test data or migrating data between systems. Why have multiple tools, when one can do it all?

Mature, stable and real-world tested

In use since 1999 and with tens of thousands of licenses sold in over 70 countries, AQT is a solidly proven product. Our customers vary from individuals with a handful of tables to large enterprises with hundreds of thousands of tables. AQT works.

See the full feature list

I've used AQT since I first found it at version 6 and could not live without it. It's the best universal query tool in the industry. Customer support is beyond the scale. Some think both the product and support are a 10 well they are wrong - it's easily a 15!!!

Nick ClavijoSolutions Architect, Charlotte, NC

As a developer, I have used AQT since 2004, and can say, hands down one of the best tools I have ever used. I use it just about every day, as do a number of developers here. Phil has solved some pretty difficult problems, above and beyond support you will find anywhere. Just for fun, I have history files going back 10 yrs. since I started using AQT and have run 140,720 queries (as of today!)! Yes, some came from batch, but most were entered manually. Used primarily with Oracle, some RDB, and once-in-a-blue-moon - Teradata, Informix and DB2.

Mike KnuevenSr Business/Application Analyst, Glen Ellyn, Illinois

Read more testimonials

Cardett Associates LtdPO Box 153, TakakaNew Zealand

aqt@dbquerytool.com

Privacy policy

Copyright 2002-2023 Cardett Associates Ltd. All rights reserved. AQT is a registered trademark of Cardett Associates Ltd.

Last reviewed on 29 March 2023

GitHub - miurahr/aqtinstall: aqt: Another (unofficial) Qt CLI Installer on multi-platforms

GitHub - miurahr/aqtinstall: aqt: Another (unofficial) Qt CLI Installer on multi-platforms

Skip to content

Toggle navigation

Sign in

Product

Actions

Automate any workflow

Packages

Host and manage packages

Security

Find and fix vulnerabilities

Codespaces

Instant dev environments

Copilot

Write better code with AI

Code review

Manage code changes

Issues

Plan and track work

Discussions

Collaborate outside of code

Explore

All features

Documentation

GitHub Skills

Blog

Solutions

For

Enterprise

Teams

Startups

Education

By Solution

CI/CD & Automation

DevOps

DevSecOps

Resources

Learning Pathways

White papers, Ebooks, Webinars

Customer Stories

Partners

Open Source

GitHub Sponsors

Fund open source developers

The ReadME Project

GitHub community articles

Repositories

Topics

Trending

Collections

Pricing

Search or jump to...

Search code, repositories, users, issues, pull requests...

Search

Clear

Search syntax tips

Provide feedback

We read every piece of feedback, and take your input very seriously.

Include my email address so I can be contacted

Cancel

Submit feedback

Saved searches

Use saved searches to filter your results more quickly

Name

Query

To see all available qualifiers, see our documentation.

Cancel

Create saved search

Sign in

Sign up

You signed in with another tab or window. Reload to refresh your session.

You signed out in another tab or window. Reload to refresh your session.

You switched accounts on another tab or window. Reload to refresh your session.

Dismiss alert

miurahr

/

aqtinstall

Public

Notifications

Fork

81

Star

819

aqt: Another (unofficial) Qt CLI Installer on multi-platforms

aqtinstall.readthedocs.io/en/latest/

License

MIT license

819

stars

81

forks

Branches

Tags

Activity

Star

Notifications

Code

Issues

24

Pull requests

6

Discussions

Actions

Projects

0

Wiki

Security

Insights

Additional navigation options

Code

Issues

Pull requests

Discussions

Actions

Projects

Wiki

Security

Insights

miurahr/aqtinstall

This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.

 masterBranchesTagsGo to fileCodeFolders and filesNameNameLast commit messageLast commit dateLatest commit History1,726 Commits.github.github  aqtaqt  cici  docsdocs  teststests  toolstools  .flake8.flake8  .git_archival.txt.git_archival.txt  .gitattributes.gitattributes  .gitignore.gitignore  .readthedocs.yml.readthedocs.yml  LICENSELICENSE  MANIFEST.inMANIFEST.in  README.rstREADME.rst  azure-pipelines.ymlazure-pipelines.yml  pyproject.tomlpyproject.toml  View all filesRepository files navigationREADMEMIT licenseAnother Qt installer(aqt)

Release:

Documentation:

Test status:

and Coverage:

Project maturity

This is a utility alternative to the official graphical Qt installer, for using in CI environment

where an interactive UI is not usable, or just on command line.

It can automatically download prebuilt Qt binaries, documents and sources for target specified,

when the versions are on Qt download mirror sites.

Note

Because it is an installer utility, it can download from Qt distribution site and its mirror.

The site is operated by The Qt Company who may remove versions you may want to use that become end of support.

Please don't blame us.

Warning

This is NOT franchised with The Qt Company and The Qt Project. Please don't ask them about aqtinstall.

License and copyright

This program is distributed under MIT license.

Qt SDK and its related files are under its licenses. When using aqtinstall, you are considered

to agree upon Qt licenses. aqtinstall installs Qt SDK as of a (L)GPL Free Software.

For details see Qt licensing and Licenses used in Qt5

Requirements

Minimum Python version:

3.7

Recommended Python version:

3.9 (frequently tested on)

Dependencies:

requests

semantic_version

patch

py7zr

texttable

bs4

defusedxml

Operating Systems:

Linux, macOS, MS Windows

Documentation

There is precise documentation with many examples.

You are recommended to read the Getting started section.

Getting started: https://aqtinstall.readthedocs.io/en/latest/getting_started.html

Stable (v3.0.x): https://aqtinstall.readthedocs.io/en/stable

Latest: https://aqtinstall.readthedocs.io/en/latest

Old (v2.2.3) : https://aqtinstall.readthedocs.io/en/v2.2.3/

Install

Same as usual, it can be installed with pip:

pip install -U pip

pip install aqtinstall

You are recommended to update pip before installing aqtinstall.

Note

aqtinstall depends several packages, that is required to download files from internet, and extract 7zip archives,

some of which are precompiled in several platforms.

Older pip does not handle it expectedly(see #230).

Note

When you want to use it on MSYS2/Mingw64 environment, you need to set environmental variable

export SETUPTOOLS_USE_DISTUTILS=stdlib, because of setuptools package on mingw wrongly

raise error VC6.0 is not supported

Warning

There is an unrelated package aqt in pypi. Please don't confuse with it.

It may be difficult to set up some Windows systems with the correct version of Python and all of aqt's dependencies.

To get around this problem, aqtinstall offers aqt.exe, a Windows executable that contains Python and all required dependencies.

You may access aqt.exe from the Releases section, under "assets", or via the persistent link to the continuous build of aqt.exe.

Example

When installing Qt SDK 6.2.0 for Windows.

Check the options that can be used with the list-qt subcommand, and query available architectures:

aqt list-qt windows desktop --arch 6.2.0

Then you may get candidates: win64_mingw81 win64_msvc2019_64 win64_msvc2019_arm64. You can also query the available modules:

aqt list-qt windows desktop --modules 6.2.0 win64_mingw81

When you decide to install Qt SDK version 6.2.0 for mingw v8.1:

aqt install-qt windows desktop 6.2.0 win64_mingw81 -m all

The optional -m all argument installs all the modules available for Qt 6.2.0; you can leave it off if you don't want those modules.

To install Qt 6.2.0 with the modules 'qtcharts' and 'qtnetworking', you can use this command (note that the module names are lowercase):

aqt install-qt windows desktop 6.2.0 win64_mingw81 -m qtcharts qtnetworking

When you want to install Qt for android with required desktop toolsets

aqt install-qt linux android 5.13.2 android_armv7 --autodesktop

When aqtinstall downloads and installs packages, it updates package configurations

such as prefix directory in bin/qt.conf, and bin/qconfig.pri

to make it working well with installed directory.

Note

It is your own task to set some environment variables to fit your platform, such as PATH, QT_PLUGIN_PATH, QML_IMPORT_PATH, and QML2_IMPORT_PATH. aqtinstall will never do it for you, in order not to break the installation of multiple versions.

Warning

If you are using aqtinstall to install the ios version of Qt, please be aware that

there are compatibility issues between XCode 13+ and versions of Qt less than 6.2.4.

You may use aqtinstall to install older versions of Qt for ios, but the developers of

aqtinstall cannot guarantee that older versions will work on the most recent versions of MacOS.

Aqtinstall is tested for ios on MacOS 12 with Qt 6.2.4 and greater.

All earlier versions of Qt are expected not to function.

Testimonies

Some projects utilize aqtinstall, and there are several articles and discussions

GitHub Actions: install_qt

Docker image: docker aqtinstall

Yet another comic reader: YACReader utilize on Azure-Pipelines

Contributor Nelson's blog article: Fast and lightweight headless Qt Installer from Qt Mirrors - aqtinstall

Lostdomain.org blog: Using Azure DevOps Pipelines with Qt

Wincak's Weblog: Using Azure CI for cross-platform Linux and Windows Qt application builds

Qt Forum: Automatic installation for Travis CI (or any other CI)

Qt Forum: Qt silent, unattended install

Reddit: Qt Maintenance tool now requires you to enter your company name

Qt Study group presentation: Another Qt CLI installer

History

This program is originally shown in Kaidan project as a name qli-installer.

The aqtinstall project extend and improve it.

About

aqt: Another (unofficial) Qt CLI Installer on multi-platforms

aqtinstall.readthedocs.io/en/latest/

Topics

python

windows

linux

qt

osx

installer

mingw

msvc

andorid-sdk

Resources

Readme

License

MIT license

Activity

Stars

819

stars

Watchers

17

watching

Forks

81

forks

Report repository

Releases

109

Release v3.1.12

Latest

Mar 2, 2024

+ 108 releases

Sponsor this project

liberapay.com/miurahr

Packages

0

No packages published

Contributors

38

+ 24 contributors

Languages

Python

56.1%

HTML

43.9%

Footer

© 2024 GitHub, Inc.

Footer navigation

Terms

Privacy

Security

Status

Docs

Contact

Manage cookies

Do not share my personal information

You can’t perform that action at this time.

Just a moment...

a moment...Enable JavaScript and cookies to continue

Getting Started — aqtinstall 3.1.12 documentation

Getting Started — aqtinstall 3.1.12 documentation

aqtinstall

latest

Installation

Command changes

Getting Started

Installing Qt

External 7-zip extractor

Changing the output directory

Installing Modules

Installing Qt for Android

Installing Qt for WASM

Installing Docs

Installing Tools

Installing a subset of Qt archives [Advanced]

Introduction

Minimum Qt Installation

Installing More Than The Bare Minimum

Installing Modules With Archives Specified

Installing the debug_info module

Command Line Options

Command examples

Configuration

Contribution guide

Contributor Covenant Code of Conduct

Security Policy

Authors

ChangeLog

Changes until v2.0.6

aqtinstall

Getting Started

Edit on GitHub

Getting Started

aqt is a tool that can be used to install Qt, modules, tools related to Qt,

source, docs, and examples, available at https://download.qt.io/.

Before running aqt, you will need to tell aqt exactly what you want it

to install. This section of the documentation is meant to walk you through the

process of finding out what packages are available to aqt, so you can tell

aqt what you want to install.

Please note that every aqt subcommand has a --help option; please use

it if you are having trouble!

Installing Qt

General usage of aqt looks like this:

aqt install-qt ( | ) []

If you have installed aqt with pip, you can run it with the command script aqt,

but in some cases you may need to run it as python -m aqt.

Some older operating systems may require you to specify Python version 3, like this: python3 -m aqt.

To use aqt to install Qt, you will need to tell aqt four things:

The host operating system (windows, mac, or linux)

The target SDK (desktop, android, ios, or winrt)

The version of Qt you would like to install

The target architecture

Keep in mind that Qt for IOS is only available on Mac OS, and Qt for WinRT is

only available on Windows.

To find out what versions of Qt are available, you can use the aqt list-qt command.

This command will print all versions of Qt available for Windows Desktop:

$ aqt list-qt windows desktop

5.9.0 5.9.1 5.9.2 5.9.3 5.9.4 5.9.5 5.9.6 5.9.7 5.9.8 5.9.9

5.10.0 5.10.1

5.11.0 5.11.1 5.11.2 5.11.3

5.12.0 5.12.1 5.12.2 5.12.3 5.12.4 5.12.5 5.12.6 5.12.7 5.12.8 5.12.9 5.12.10 5.12.11

5.13.0 5.13.1 5.13.2

5.14.0 5.14.1 5.14.2

5.15.0 5.15.1 5.15.2

6.0.0 6.0.1 6.0.2 6.0.3 6.0.4

6.1.0 6.1.1 6.1.2

6.2.0

Notice that the version numbers are sorted, grouped by minor version number,

and separated by a single space-character. The output of all of the

aqt list-qt commands is intended to make it easier for you to write programs

that consume the output of aqt list-qt.

Because the aqt list-qt command directly queries the Qt downloads repository

at https://download.qt.io/, the results of this command will always be accurate.

The Available Qt versions wiki page was last modified at some point in the past,

so it may or may not be up to date.

Now that we know what versions of Qt are available, let’s choose version 6.2.0.

The next thing we need to do is find out what architectures are available for

Qt 6.2.0 for Windows Desktop. To do this, we can use aqt list-qt with the

--arch flag:

$ aqt list-qt windows desktop --arch 6.2.0

win64_mingw81 win64_msvc2019_64 win64_msvc2019_arm64 wasm_32

Notice that this is a very small subset of the architectures listed in the

Available Qt versions wiki page. If we need to use some architecture that

is not on this list, we can use the Available Qt versions wiki page to get

a rough idea of what versions support the architecture we want, and then use

aqt list-qt to confirm that the architecture is available.

Let’s say that we want to install Qt 6.2.0 with architecture win64_mingw81.

The installation command we need is:

$ aqt install-qt windows desktop 6.2.0 win64_mingw81

Let’s say that we want to install the next version of Qt 6.2 as soon as it is available.

We can do this by using a

SimpleSpec

instead of an explicit version:

$ aqt install-qt windows desktop 6.2 win64_mingw81

External 7-zip extractor

By default, aqt extracts the 7zip archives stored in the Qt repository using

py7zr, which is installed alongside aqt. You can specify an alternate 7zip

command path instead by using the -E or --external flag. For example,

you could use 7-zip on a Windows desktop, using this command:

C:\> aqt install-qt windows desktop 6.2.0 gcc_64 --external 7za.exe

On Linux, you can specify p7zip, a Linux port of 7-zip, which is often

installed by default, using this command:

$ aqt install-qt linux desktop 6.2.0 gcc_64 --external 7z

Changing the output directory

By default, aqt will install all of the Qt packages into the current

working directory, in the subdirectory .///.

For example, if we install Qt 6.2.0 for Windows desktop with arch win64_mingw81,

it would end up in ./6.2.0/win64_mingw81.

If you would prefer to install it to another location, you

will need to use the -O or --outputdir flag.

This option also works for all of the other subcommands that begin with

aqt install-.

To install to C:\Qt, the default directory used by the standard gui installer,

you may use this command:

C:\> mkdir Qt

C:\> aqt install-qt --outputdir c:\Qt windows desktop 6.2.0 win64_mingw81

Installing Modules

Let’s say we need to install some modules for Qt 5.15.2 on Windows Desktop.

First we need to find out what the modules are called, and we can do that

with aqt list-qt with the --modules flag.

Each version of Qt has a different list of modules for each host OS/ target SDK/ architecture

combination, so we will need to supply aqt list-qt with that information:

$ aqt list-qt windows desktop --modules 5.15.2 win64_mingw81

qtcharts qtdatavis3d qtlottie qtnetworkauth qtpurchasing qtquick3d

qtquicktimeline qtscript qtvirtualkeyboard qtwebengine qtwebglplugin

Let’s say that we want to know more about these modules before we install them.

We can use the --long-modules flag for that:

$ aqt list-qt windows desktop --long-modules 5.15.2 win64_mingw81

Module Name Display Name

======================================================================

debug_info Desktop MinGW 8.1.0 64-bit Debug Information Files

qtcharts Qt Charts for MinGW 8.1.0 64-bit

qtdatavis3d Qt Data Visualization for MinGW 8.1.0 64-bit

qtlottie Qt Lottie Animation for MinGW 8.1.0 64-bit

qtnetworkauth Qt Network Authorization for MinGW 8.1.0 64-bit

qtpurchasing Qt Purchasing for MinGW 8.1.0 64-bit

qtquick3d Qt Quick 3D for MinGW 8.1.0 64-bit

qtquicktimeline Qt Quick Timeline for MinGW 8.1.0 64-bit

qtscript Qt Script for MinGW 8.1.0 64-bit

qtvirtualkeyboard Qt Virtual Keyboard for MinGW 8.1.0 64-bit

qtwebglplugin Qt WebGL Streaming Plugin for MinGW 8.1.0 64-bit

Note that if your terminal is wider than 95 characters, this command will show

release dates and sizes in extra columns to the right.

If you try this, you will notice that debug_info is 5.9 gigabytes installed.

Also, notice that the ‘Display Name’ indicates which compiler the module is

intended to be used with. In this case, for the architecture win64_mingw81,

you will most likely want to use the “MinGW 8.1.0 64-bit” compiler.

Here’s what the command prints when you use it with the ambiguously-named

win64_mingw architecture:

$ python -m aqt list-qt windows desktop --long-modules 6.2.4 win64_mingw

Module Name Display Name

=======================================================================

debug_info Desktop MinGW 11.2.0 64-bit debug information files

qt3d Qt 3D for MinGW 11.2.0 64-bit

qt5compat Qt 5 Compatibility Module for MinGW 11.2.0 64-bit

qtactiveqt Qt 3D for MinGW 11.2.0 64-bit

qtcharts Qt Charts for MinGW 11.2.0 64-bit

...

You can find out how to install MinGW 8.1.0 and 11.2.0 in the Installing Tools section.

Let’s say that we want to install qtcharts and qtnetworkauth.

We can do that by using the -m flag with the aqt install-qt command.

This flag receives the name of at least one module as an argument:

$ aqt install-qt windows desktop 5.15.2 win64_mingw81 -m qtcharts qtnetworkauth

If we wish to install all the modules that are available, we can do that with the all keyword:

$ aqt install-qt windows desktop 5.15.2 win64_mingw81 -m all

Remember that the aqt list-qt command is meant to be scriptable?

One way to install all modules available for Qt 5.15.2 is to send the output of

aqt list-qt into aqt install-qt, like this:

$ aqt install-qt windows desktop 5.15.2 win64_mingw81 \

-m $(aqt list-qt windows desktop --modules 5.15.2 win64_mingw81)

You will need a Unix-style shell to run this command, or at least git-bash on Windows.

The xargs equivalent to this command is an exercise left to the reader.

If you want to install all available modules, you are probably better off using

the all keyword, as discussed above. This scripting example is presented to

give you a sense of how to accomplish something more complicated.

Perhaps you want to install all modules except qtnetworkauth; you could write a script

that removes qtnetworkauth from the output of aqt list-qt,

and pipe that into aqt install-qt.

This exercise is left to the reader.

Installing Qt for Android

Let’s install Qt for Android. This will be similar to installing Qt for Desktop on Windows.

Note

Versions of aqtinstall older than 3.1.0 required the use of the --extensions and

--extension flag to list any architectures, modules, or archives for Qt 6 and above.

These flags are no longer necessary, so please do not use them.

$ aqt list-qt windows android # Print Qt versions available

5.9.0 5.9.1 ...

...

6.4.0

$ aqt list-qt windows android --arch 6.2.4 # Print architectures available

android_x86_64 android_armv7 android_x86 android_arm64_v8a

$ aqt list-qt windows android --modules 6.2.4 android_armv7 # Print modules available

qt3d qt5compat qtcharts qtconnectivity qtdatavis3d ...

$ aqt install-qt windows android 6.2.4 android_armv7 -m qtcharts qtnetworkauth # Install

Please note that when you install Qt6 for android or ios, the installation will not

be functional unless you install the corresponding desktop version of Qt alongside it.

You can do this automatically with the --autodesktop flag:

$ aqt install-qt linux android 6.2.4 android_armv7 -m qtcharts qtnetworkauth --autodesktop

Installing Qt for WASM

To find out how to install Qt for WASM, we will need to use the wasm_32 architecture.

We can find out whether or not that architecture is available for our version of Qt with the

--arch flag.

$ python -m aqt list-qt windows desktop --arch 6.1.3

win64_mingw81 win64_msvc2019_64

$ python -m aqt list-qt windows desktop --arch 6.2.0

win64_mingw81 win64_msvc2019_64 win64_msvc2019_arm64 wasm_32

Not every version of Qt supports WASM. This command shows us that we cannot use WASM with Qt 6.1.3.

Please note that the WASM architecture for Qt 6.5.0+ changed from wasm_32 to wasm_singlethread and

wasm_multithread. Always use aqt list-qt to check what architectures are available for the desired version of Qt.

We can check the modules available as before:

$ aqt list-qt windows desktop --modules 5.15.2 wasm_32 # available modules

qtcharts qtdatavis3d qtlottie qtnetworkauth qtpurchasing qtquicktimeline qtscript

qtvirtualkeyboard qtwebglplugin

We can install Qt for WASM as before:

$ aqt install-qt windows desktop 5.15.2 wasm_32 -m qtcharts qtnetworkauth

Please note that when you install Qt for WASM version 6 and above, the installation will not

be functional unless you install a non-WASM desktop version of Qt alongside it.

You can do this automatically with the --autodesktop flag:

$ aqt install-qt linux desktop 6.2.0 wasm_32 -m qtcharts qtnetworkauth --autodesktop

Installing Docs

The aqt list-doc command lists documentation

archives for a given Qt version:

$ aqt list-doc mac 6.6.1

qdoc qmake qt5 qtassistant qtcmake qtconcurrent qtcore qtdbus qtdesigner

qtdistancefieldgenerator qtdoc qtgui qthelp qtlabsplatform qtlinguist qtnetwork

qtopengl qtplatformintegration qtprintsupport qtqml qtqmlcore qtqmlmodels qtqmltest

qtqmlworkerscript qtqmlxmllistmodel qtquick qtquickcontrols qtquickdialogs qtsql

qtsvg qttestlib qtuitools qtwaylandcompositor qtwidgets qtxml

All of the above archives will be installed when you run aqt install-doc mac 6.6.1

without any other flags or arguments.

You can select a subset of them with the --archives flag.

The --modules flag lists additional documentation modules that can be installed:

$ aqt list-doc mac 6.6.1 --modules

qt3d qt5compat qtactiveqt qtbluetooth qtcharts qtdatavis3d qtgraphs qtgrpc qthttpserver

qtimageformats qtlocation qtlottie qtmultimedia qtnetworkauth qtnfc qtpdf qtpositioning

qtquick3d qtquick3dphysics qtquickeffectmaker qtquicktimeline qtremoteobjects qtscxml

qtsensors qtserialbus qtserialport qtshadertools qtspeech qtvirtualkeyboard qtwebchannel

qtwebengine qtwebsockets qtwebview

The --archives and --modules flags can be used together.

For example, to only install the docs for qtquick and qt3d,

use the aqt install-doc command like this:

$ aqt install-doc mac 6.6.1 --archives qtquick --modules qt3d

INFO : Downloading qt3d...

INFO : Downloading qtquick...

INFO : Redirected: qt.mirror.constant.com

INFO : Redirected: qt.mirror.constant.com

INFO : Finished installation of qt3d-documentation.tar.xz in 1.51932292

INFO : Finished installation of qtquick-documentation.tar.xz in 2.63531679

INFO : Finished installation

INFO : Time elapsed: 4.00115146 second

Installing Tools

Let’s find out what tools are available for Windows Desktop by using the

aqt list-tool command:

$ aqt list-tool windows desktop

tools_vcredist

...

tools_qtcreator

tools_qt3dstudio

tools_openssl_x86

tools_openssl_x64

tools_openssl_src

tools_ninja

tools_mingw

tools_mingw90

tools_ifw

tools_conan

tools_cmake

Let’s see what tool variants are available in tools_mingw:

$ aqt list-tool windows desktop tools_mingw

qt.tools.mingw47

qt.tools.win32_mingw48

qt.tools.win32_mingw482

qt.tools.win32_mingw491

qt.tools.win32_mingw492

qt.tools.win32_mingw530

qt.tools.win32_mingw730

qt.tools.win32_mingw810

qt.tools.win64_mingw730

qt.tools.win64_mingw810

This gives us a list of things that we could install using

aqt install-tool.

Let’s see some more details, using the -l or --long flag:

$ aqt list-tool windows desktop tools_mingw -l

Tool Variant Name Version Release Date

=============================================================

qt.tools.mingw47 4.7.2-1-1 2013-07-01

qt.tools.win32_mingw48 4.8.0-1-1 2013-07-01

qt.tools.win32_mingw482 4.8.2 2014-05-08

qt.tools.win32_mingw491 4.9.1-3 2016-05-31

qt.tools.win32_mingw492 4.9.2-1 2016-05-31

qt.tools.win32_mingw530 5.3.0-2 2017-04-27

qt.tools.win32_mingw730 7.3.0-1-202004170606 2020-04-17

qt.tools.win32_mingw810 8.1.0-1-202004170606 2020-04-17

qt.tools.win64_mingw730 7.3.0-1-202004170606 2020-04-17

qt.tools.win64_mingw810 8.1.0-1-202004170606 2020-04-17

The -l flag causes aqt list-tool to print a table

that shows plenty of data pertinent to each tool variant available in tools_mingw.

aqt list-tool additionally prints the ‘Display Name’

and ‘Description’ for each tool if your terminal is wider than 95 characters;

terminals that are narrower than this cannot display this table in a readable way.

Please be aware that the tool tools_mingw90 appears to be mislabelled:

$ aqt list-tool windows desktop tools_mingw90 -l

Tool Variant Name Version Release Date

=============================================================

qt.tools.win64_mingw900 9.0.0-1-202203221220 2022-03-22

$ aqt list-tool windows desktop tools_mingw90 -l

Tool Variant Name Version Release Date Display Name Description

============================================================================================================

qt.tools.win64_mingw900 9.0.0-1-202203221220 2022-03-22 MinGW 11.2.0 64-bit MinGW-builds 11.2.0

64-bit toolchain with

gcc 11.2.0

The ‘narrow display’ for tools_mingw90 cuts off the two columns of the table that

show you what’s really in that package: MinGW 11.2.0 64-bit.

If you are using the win64_mingw architecture for Qt 6.2.2+, then this is

probably the compiler you want to install (see long_modules explanation).

Now let’s install mingw, using the aqt install-tool command.

This command receives four parameters:

The host operating system (windows, mac, or linux)

The target SDK (desktop, android, ios, or winrt)

The name of the tool (this is tools_mingw in our case)

(Optional) The tool variant name. We saw a list of these when we ran

aqt list-tool with the tool name argument filled in.

To install mingw, you could use this command (please don’t):

$ aqt install-tool windows desktop tools_mingw # please don't run this!

Using this command will install every tool variant available in tools_mingw;

in this case, you would install 10 different versions of the same tool.

For some tools, like qtcreator or ifw, this is an appropriate thing to do,

since each tool variant is a different program.

However, for tools like mingw and vcredist, it would make more sense to use

aqt list-tool to see what tool variants are available,

and then install just the tool variant you are interested in, like this:

$ aqt install-tool windows desktop tools_mingw qt.tools.win64_mingw730

Please note that aqt install-tool does not recognize the installscript.qs

related to each tool. When you install these tools with the standard gui installer,

the installer may use the installscript.qs script to make additional changes

to your system. If you need those changes to occur, it will be your responsibility

to make those changes happen, because aqt is not capable of running this script.

Installing a subset of Qt archives [Advanced]

Introduction

You may have noticed that by default, aqt install-qt installs a lot of

archives that you may or may not need, and a typical installation can take up

more disk space than necessary. If you installed the module debug_info, it

may have installed more than 1 gigabyte of data. This section will help you to

reduce the footprint of your Qt installation.

Note

Be careful about using the --archives flag; it is marked Advanced for a reason!

It is very easy to misuse this command and end up with a Qt installation that

is missing the components that you need.

Don’t use it unless you know what you are doing!

Minimum Qt Installation

Normally, when you run aqt install-qt, the program will print a long list

of archives that it is downloading, extracting, and installing,

including qtbase, qtmultimedia, qt3d, and ~25 more items.

We can use the --archives flag to choose which of these archives we will

actually install.

The --archives flag can only affect two modules: the base Qt installation and the debug_info module.

Note

In this documentation, “modules”, “archives”, and “the base Qt installation”

refer to different things, and are defined here:

Archives: In this context, an archive is a bundle of files compressed

with the 7zip algorithm.

It exists on a disk drive as a file with the extension .7z.

Modules: The Qt repository organizes groups of archives into modules.

A module contains one or more archives.

the base Qt installation:

By definition, this is just another module that contains 20-30 archives.

This documentation refers to it as the base Qt installation instead of

a module for several reasons:

The aqt install-qt installs this module by default.

You cannot specify this module with aqt install-qt --modules.

The aqt list-qt --modules command is incapable of printing this module.

aqt transforms the names of modules as they exist in the Qt repository

so that they are easier to read and write.

If the name of the base Qt installation were transformed using the

same rules, the name would be empty.

The fully-qualified name of the base Qt installation module is

usually something like qt.qt6.620.gcc_64.

The fully-qualified name of the qtcharts module could be

something like qt.qt6.620.qtcharts.gcc_64.

It would be difficult to read and write a list of 20 modules with the prefix

qt.qt6.620. and the suffix .gcc_64, because these parts are

repetitive and not meaningful. Only the qtcharts part is useful.

Let’s say that we want to install Qt 5.15.2 for Linux desktop, using the gcc_64 architecture.

The qtbase archive includes the bare minimum for a working Qt installation,

and we can install it alone with the --archives flag:

$ aqt install-qt linux desktop 5.15.2 --archives qtbase

This time, aqt install-qt will only install one archive, qtbase, instead

of the ~27 archives it installs by default.

Installing More Than The Bare Minimum

Let’s say that the qtbase archive is missing some features that you need.

Using the --archives qtbase flag causes aqt install-qt to omit roughly 27 archives.

We can print a list of these archives with the aqt list-qt --archives command:

$ aqt list-qt linux desktop --archives 5.15.2 gcc_64

icu qt3d qtbase qtconnectivity qtdeclarative qtgamepad qtgraphicaleffects qtimageformats

qtlocation qtmultimedia qtquickcontrols qtquickcontrols2 qtremoteobjects qtscxml

qtsensors qtserialbus qtserialport qtspeech qtsvg qttools qttranslations qtwayland

qtwebchannel qtwebsockets qtwebview qtx11extras qtxmlpatterns

Here, we have used the --archives flag with two arguments:

the version of Qt we are interested in, and the architecture we are using.

As a result, the command printed a list of archives that are part of the base

(non-minimal) Qt installation.

Let’s say we need to use qtmultimedia, qtdeclarative, qtsvg, and

nothing else. Remember that the qtbase archive is required for a minimal

working Qt installation. We can install these archives using this command:

$ aqt install-qt linux desktop 5.15.2 --archives qtbase qtmultimedia qtdeclarative qtsvg

Installing Modules With Archives Specified

As of aqt v2.1.0, the --archives flag will only apply to

the base Qt installation and to the debug_info module.

Previous versions of aqt required that when installing modules with the --archives flag,

the user must specify archives for each module, otherwise they would not be installed.

This behavior has been changed to prevent such mistakes.

Let’s say that we need to install the bare minimum Qt 5.15.2, with the modules qtcharts and qtlottie:

$ aqt install-qt linux desktop 5.15.2 --modules qtcharts qtlottie --archives qtbase

This command will successfully install 3 archives: 1 for qtbase, and one each for the two modules.

If we had tried to use this command with previous versions of aqt, we would not have

installed the two modules because we did not specify them in the --archives list.

Note

You can still misuse the --archives flag by omitting the qtbase archive,

or by omitting archives that another archive or module is dependent on.

You may not notice that there is a problem until you try to compile a program,

and compilation fails.

Installing the debug_info module

Now let’s say we need to install the debug_info module, which is particularly large: around one gigabyte.

We do not want to install all of it, so we can use aqt install-qt --archives

to choose which archives we want to install. Remember that the --archives flag

aqt list-qt --archives

to print which archives are part of the debug_info module:

$ aqt list-qt linux desktop --archives 5.15.2 gcc_64 debug_info

qt3d qtbase qtcharts qtconnectivity qtdatavis3d qtdeclarative qtgamepad qtgraphicaleffects

qtimageformats qtlocation qtlottie qtmultimedia qtnetworkauth qtpurchasing qtquick3d

qtquickcontrols qtquickcontrols2 qtquicktimeline qtremoteobjects qtscript qtscxml qtsensors

qtserialbus qtserialport qtspeech qtsvg qttools qtvirtualkeyboard qtwayland qtwebchannel

qtwebengine qtwebglplugin qtwebsockets qtwebview qtx11extras qtxmlpatterns

This is a lot of archives.

Note that there’s a name collision between the debug_info archives and the

archives in every other module/Qt base install:

this is because there’s a debug_info archive that corresponds to almost

every other archive available.

Let’s install Qt with qtcharts and debug_info with some archives specified:

$ aqt install-qt linux desktop --modules qtcharts debug_info \

--archives qtcharts qtbase qtdeclarative

Notice what we did here: We specified the qtcharts and debug_info modules,

and we specified the qtbase, qtcharts, and qtdeclarative archives.

This will install a total of 6 archives:

the 3 archives named qtbase, qtcharts, and qtdeclarative from the debug_info module,

the 1 archive qtcharts from the qtcharts module, and

the 2 archives qtbase and qtdeclarative from the base Qt installation.

Note

At present, aqt install-qt is incapable of installing any archive from

the debug_info module without also installing the corresponding module

from the base Qt installation.

For instance, you cannot install the debug_info archive for qtbase

without also installing the usual qtbase archive.

Previous

Next

© Copyright 2019-2023, Hiroshi Miura.

Revision 8592b1d9.

Built with Sphinx using a

theme

provided by Read the Docs.

Read the Docs

v: latest

Versions

latest

stable

v3.1.12

v3.1.11

v3.1.10

v3.1.9

v3.1.8

v3.1.7

v3.1.6

v3.1.5

v3.1.4

v3.1.3

v3.1.2

v3.1.1

v3.1.0

v3.0.2

v3.0.1

v3.0.0

v2.2.3

v2.2.2

v2.2.1

v2.2.0

v2.1.0

v2.0.6

v2.0.5

v2.0.4

v2.0.2

v2.0.1

v2.0.0

v1.2.5

v1.2.4

v1.2.3

v1.2.2

v1.2.1

v1.2.0

v1.1.6

v1.1.5

v1.1.4

v1.1.3

v1.1.2

v1.1.1

v1.1.0

v1.0.0

v0.11.2

v0.11.1

v0.11.0

v0.10.1

v0.10.0

v0.9.8

v0.9.7

v0.9.6

v0.9.5

v0.9.4

v0.9.3

v0.9.2

v0.9.1

v0.9.0

v0.8

v0.7.9

v0.7.8

v0.7.7

v0.7.6

v0.7.5

v0.7.4

v0.7.3

v0.7.2

v0.7.1

v0.7

v0.6

v0.5.2

v0.5.1

v0.5

v0.4.3

Downloads

pdf

epub

On Read the Docs

Project Home

Builds

标准文本--中华人民共和国应急管理部

标准文本--中华人民共和国应急管理部

首页

机构

新闻

时政专栏

应急要闻

工作动态

地方应急

救援力量

灾害事故信息

新闻发布会

媒体信息

公开

政府信息公开

通知公告

政策解读

事故及灾害查处

人事信息

财务信息

计划规划

统计数据

建议提案办理

原国家安全监管总局文件

服务

政务服务

警示信息

法律法规标准

应急预案

应急管理部行政许可

行政执法公示

应急普法

查询服务

业务系统

应急管理部电子证照

互动

在线访谈

征求意见

回应关切

公众留言

国家政务服务投诉与建议

党建

党建要闻

基层党建

党风廉政

巡视工作

公文公告

规章制度

群团统战

学习园地

热点专题

社会救援服务

工作信息

队伍风采

应急科普

应急指南

生活安全

自然灾害

安全生产

首页>服务>法律法规标准>标准>标准文本

制度文件

标准文本

AQ 5213—2023 鳞片状锌铝粉防腐涂层涂装作业安全规定2024-01-15 20:29

AQ 6111—2023 个体防护装备安全管理规范2024-01-15 20:28

AQ 9012—2023 生产安全事故应急救援评估规范2024-01-15 20:28

AQ 3059—2023 化工企业液化烃储罐区安全管理规范2024-01-15 20:27

AQ 8011—2023 安全生产培训机构基本条件2024-01-15 20:27

AQ 3058—2023 内浮顶储罐检修安全规范2024-01-15 20:26

AQ 3010—2022 加油站作业安全规范2022-12-13 17:38

AQ/T 3034—2022 化工过程安全管理导则2022-12-13 17:28

AQ/T 3033—2022 化工建设项目安全设计管理导则2022-03-18 16:29

AQ/T 8012—2022 安全生产检测检验机构诚信建设规范2022-03-18 16:29

XF/T 3014.1—2022消防数据元第1部分:基础业务信息2022-01-29 12:54

XF/T 3016.1—2022消防信息代码第1部分:基础业务信息2022-01-29 12:53

XF/T 3015.1—2022消防数据元限定词第1部分:基础业务信息2022-01-29 12:53

XF/T 3017.1—2022消防业务信息数据项第1部分:灭火救援指挥基本信息2022-01-29 12:52

XF/T 3017.2—2022消防业务信息数据项第2部分:消防产品质量监督管理基本信息2022-01-29 12:51

XF/T 3017.4—2022消防业务信息数据项第4部分:消防信息通信管理基本信息2022-01-29 12:50

XF/T 3017.3—2022消防业务信息数据项第3部分:消防装备基本信息2022-01-29 12:50

XF/T 3017.5—2022消防业务信息数据项第5部分:消防安全重点单位与建筑物基本信息2022-01-29 12:49

XF/T 3018—2022消防业务信息系统运行维护规范2022-01-29 12:48

AQ/T 1009-2021矿山救护队标准化考核规范2022-01-17 17:24

网站地图

|

联系我们

网站技术支持电话: 010-64463685

主办单位:应急管理部

网站标识码bm34000001京ICP备18056520号-2京公网安备11040102700086号

追踪美国量子计算:伯克利国家实验室进展报告 - 知乎

追踪美国量子计算:伯克利国家实验室进展报告 - 知乎切换模式写文章登录/注册追踪美国量子计算:伯克利国家实验室进展报告光子盒光子盒研究院出品2022年4月,劳伦斯-伯克利国家实验室发布了旗下高级量子测试平台(Advanced Quantum Testbed,AQT)的相关进展报告。通过本文,我们可以了解美国领先的国家实验室在量子计算领域的实际进展。高级量子测试平台(AQT)是领先的合作研究平台,于2018年成立于劳伦斯-伯克利国家实验室,并由美国能源部(DOE)科学办公室“高级科学计算研究项目”资助。第一阶段的重点是部署并整合先进的超导硬件,和开发新的量子基准技术;这包括验证和确认、噪声的检测、抑制和缓解。2020年,AQT开放实验平台。收到了来自学界、国家实验室、初创公司的众多实验申请;内容涵盖:量子算法、模拟、表征、验证、硬件控制、固件、软件和处理器架构等。在2018至2021这三年间,AQT已经在量子模拟、优化、量子化学和凝聚态物质、核物理和高能物理领域进行了各种演示。基于上述合作机会和实验设施,AOT也致力于培养下一代量子计算科学家和工程师。提供量子领域导师带教、开放讨论、多源合作等培训机会。AQT的使用者也经过层层严选,将获得对硬件和软件系统的全方位权限:包括关于设计、性能和操作的数据。这也将进一步加强量子硬件的使用性能。经过一系列交叉学科的前沿实验,AQT已经搭建起了适用于联合超导量子信息的全栈处理平台。这一平台包括设计与制造新型量子比特、量子处理器架构、低温封装等技术、包含硬件固件和软件在内的室温控制链、量子电路优化工具、量子表征验证和核实工具等。这些都对平台参与和使用者开源开放,构成量子研究相关的良性循环。1)软件堆栈包含适用于多种开源量子电路格式、配备高效编译和缓解错误等一系列算法优化工具的多功能软件堆栈。这一堆栈能为用户提供低级别访问和非标准软件访问需求。2)商业和自定义控制包括自定义和内部电子控制。内部电子控制堆栈——QubiC,可满足平台用户的需求。与已有的商业量子计算平台相比,用户和AQT科学家的密切合作提供了更多灵活性。3)低温平台包含一台Bluefors稀释制冷机——Blizzard,装备有160RF线路,并在10mk的温度下运行。Blizzard是与伯克利初创公司Bleximo合作开发的,包括一个可容纳模块化和可扩展的成套实验的实验台,以及用于改善电磁卫生的低温封装。这一平台可控制并读取128量子比特,并且可以容纳多个量子处理器。4)超导量子处理器AQT处理器组合包括一系列不同的架构,具有不同的连接性和本地门组。目前针对用户实验的标准处理器是一个具有高相干性量子比特、高保真门(双量子比特门保真度达99%)的8量子比特QPU。具有任意的动态可重构(最高可全部)连接的新型8量子比特处理器正在研发。AQT也正和MIT林肯实验室合作,研发实验室适用的新型处理器。在伯克利实验室长期进行的粒子加速器研究基础上,AQT开发了自己的室内控制堆栈。其中最重要是一个新型的、基于FPGA架构的控制处理系统——QubiC,并已经实现模块化和开源。QubiC能够以最小负载有效地上传和执行量子实验,可以定制以适应用户的独特需求,并快速反馈。如今,AQT科学家已经利用QubiC针对双量子比特门进行自动化校准实验。“更新的控制电路并非适配量子处理器,所以量子科学家采购更多仪器来适应量子硬件的优化需求。然而,在控制硬件的花费并非线性或指数型增长,这一领域也是我们正试图涉猎的。在切实意识到未来整合和设计的需求后,我们搭建了可行性更高、更具经济效益的QubiC系统。”伯克利实验室加速器技术与应用物理事业部、QubiC研发合作领导者Guang Huang表示。AQT作为开源的实验平台,并鼓励学界、产业界、国家实验室的跨领域的研究团队使用,以此来支持美国能源部(DOE)的科学和能源计划。为此,AQT提供易于访问的深厚专业知识,以完善项目创意以获得最大的潜在影响,甚至通常带来实施它们的新方法。除此之外,AQT正搭建自己的用户社区,允许用户交换创意并共享知识。在2020至2021年度,超过一半的项目正与国家实验室团队合作。测试平台的用户包含Quantum Benchmark、是德科技和Super. tech等行业合作伙伴。2021年10月,AQT向用户发起了第二次倡议,收到多个主题的项目申请。包含在科学计算机上实施算法、含噪声中等规模量子(NISQ)硬件基准,以及联合搭建下一代架构和算法。如今,作为快速发展的量子信息科学社区实验室,AQT持续滚动接收科研项目申请。自成立之初,AQT已经在多个量子信息科学领域取得广泛的进展,具体的实验亮点整理如下:1)高保真iToffoli门NISQ器件的发展扩展了具有高保真单量子和双量子比特门的可执行量子电路的范围。为NISQ器件配备三量子比特门将能够实现更复杂的量子算法和高效的量子纠错协议,并减少电路深度。2021年,研究人员使用固定频率超导量子比特,展示了一种基于双量子比特相互作用的高保真iToffoli门[1],即所谓的交叉共振效应。与Toffoli门一样,这个三量子比特门可用于执行通用量子计算,并具有高达98.26%的保真度,提供了比Toffoli门更有效的门合成。2)qutrit随机基准测试表征错误三元量子处理器利用qutrit(三能级系统)中的量子信息编码和处理,提供了优于传统量子比特技术的显著潜在计算优势。为了评估和比较这种三元量子处理器的硬件性能,研究人员展示了行业标准随机基准测试(RB)协议的扩展,该协议被广泛开发和用于量子比特[2],适用于三元量子逻辑。通过交错RB表征了几个相关的门,并采用同步RB来全面表征串扰错误。最后将周期基准应用于双量子CSUM门,并获得0.85的双qutrit过程保真度。这一结果呈现并演示了基于RB的工具、用于表征qutrit处理器的性能,以及诊断未来qudit硬件控制错误的一般方法。3)利用QITE算法的随机编译NISQ硬件的成功表明,即使没有纠错,量子硬件也能够解决复杂的问题。一个悬而未决的问题是,由于这些设备的复杂性增加而产生的相干错误:这些错误可以通过电路累积,使其对算法的影响难以预测和缓解。AQT的研究介绍了使用随机编译的噪声定制和使用纯化的错误缓解的组合;还表明,循环基准测试给出了纯化的可靠性估计。研究人员将这种方法应用于横向场存在模型的量子虚时间演化,并报告能量估计和基态错误率均低于1%。本次研究展示了如何将噪声定制和错误缓解相结合,以提高NISQ器件的性能[3]。4)优化的费米子SWAP网络AQT开发的费米子SWAP网络是一个量子比特路由序列,可用于有效执行量子近似优化算法(QAOA)。这项工作中,研究人员通过两种技术优化了QAOA的费米子SWAP网络的执行:首先,利用一组超完成的原生硬件操作(包括150 ns可控π/2相位门,保真度高达99.67%),以最小化电路深度和最大化门消除的方式分解相关的量子门和SWAP网络;其次,引入了等效电路平均,它在量子电路编译中随机化超过自由度,以减少系统相干错误的影响。这一技术通过执行QAOA电路在高级量子测试台上进行了实验验证,以找到具有各种随机采样参数的两节点和四节点Sherrington-Kirkpatrick自旋玻璃模型的基态。最后观察到,在超导量子处理器上的四个量子比特上,深度p=1的QAOA的错误平均降低了约60%[4]。5)进行可扩展量子计算的随机编译在NISQ时代,量子比特控制中的系统性错误校准、漂移和串扰会导致没有经典模拟的相干错误。相干错误以不可预测的方式严重限制了量子算法的性能,减轻其影响对于实现可靠的量子计算是必要的。随机编译是一种协议,旨在通过将相干错误转换为随机噪声来克服这些性能限制,从而大大减少量子算法中不可预测的错误,并通过周期基准测试测量的错误率准确预测算法性能。在这项工作中,研究人员展示了在超导量子处理器上对四量子比特量子傅里叶变换算法和可变深度随机电路进行随机编译的显着性能提升;并使用实验测量的错误率准确预测算法性能。研究结果表明,随机编译可用于利用和预测现代嘈杂量子处理器的功能,为可扩展的量子计算铺平了道路[5]。6)有效提高噪声量子计算机的性能研究人员开发并实验验证了两种名为“无噪声输出外推”和“泡利错误消除”的有效错误缓解协议,从而大大提高由门极噪声循环组成的量子电路的性能。通过将概率错误消除和噪声放大等流行的缓解策略与有效的噪声重建方法相结合,这一协议可以缓解各种噪声过程,这些过程不满足现有缓解协议的假设,包括非本地和门相关过程。研究人员在高级量子测试台上的四量子比特超导处理器上测试该协议,观察到结构化和随机电路的性能都有显著改善,最多86%未调整输出的变化距离有所改善。这一实验证明了此次研究协议的有效性,以及它们在当前硬件平台上的实用性[6]。自建立之初,AQT已经吸纳聘请了大量不同背景、不同学科领域的科学家,以组建一个跨国家、多领域的联合交流社区,同时培养量子劳动力。AQT培养在读本科生开展为期一年的论文项目,也为研究生提供实验室培训和参与量子算法应用的项目机会。在AQT的培训项目中,学生和博士后与国家实验室、企业联合开展,学习更为广泛的量子知识。AQT也为高中和本科学生提供额外的教育机会。例如,硬件部门主管Kasra Nowrouzih在过去的几年间,带领加州大学戴维斯分校(UC Davis)学生开展暑期国家科学基金会“本科生研究经历”(REU)项目;AQT也联合伯克利实验室的K-12 STEM“教育和推广计划”,组织与测量部门主管Ravi Naik的职业访谈。AQT的学生和往届毕业生在全球实验室和顶尖机构就职,具体包括谷歌、Alice & Bob、韩国科学技术研究所、耶鲁量子研究所、罗切斯特大学等。报告原文:https://aqt.lbl.gov/wp-content/uploads/sites/4/2022/04/AQT-Progress-Report-2021-Online.pdf参考链接:[1]https://arxiv.org/abs/2108.10288[2]https://journals.aps.org/prl/abstract/10.1103/PhysRevLett.126.210504[3]https://arxiv.org/abs/2104.08785[4]https://arxiv.org/abs/2111.04572[5]https://journals.aps.org/prx/abstract/10.1103/PhysRevX.11.041039[6]https://arxiv.org/abs/2201.10672发布于 2022-04-19 10:38量子计算量子物理量子计算与量子信息​赞同​​添加评论​分享​喜欢​收藏​申请

世界最小量子计算机诞生,离子阱量子技术或成为最终赢家? - 知乎

世界最小量子计算机诞生,离子阱量子技术或成为最终赢家? - 知乎切换模式写文章登录/注册世界最小量子计算机诞生,离子阱量子技术或成为最终赢家?Qtumist量子客以第一线视角为您解读量子科技的前沿技术动态迄今为止,世界现存的量子计算机都是独一无二的设备,它们的体积之庞大,可以占满整个实验室。而现在,奥地利因斯布鲁克大学的物理学家们,已经搭建了一个商用离子阱量子计算机的原型机[1,2]。该机器可以安装在两个19英寸 (约100厘米) 宽的服务器机架上,设备十分紧凑,具有自我维持特性,侧面印证了量子计算技术将很快为人所用。图1|可以置于100厘米宽的机架上 (来源:因斯布鲁克大学)在过去的三十年里,因斯布鲁克大学已经率先开始为建造量子计算机打基础了。作为欧洲量子技术旗舰计划 (EU Flagship Quantum Technologies) 的一部分,因斯布鲁克大学物理系的研究人员现已搭建了一个十分紧凑的离子阱量子计算机的原型机。因斯布鲁克大学实验物理研究所Rainer Blatt​研究小组成员Thomas Monz表示,他们进行的量子计算实验,通常会占据30-50平方米的实验室空间,不易于量子硬件的扩展。研究人员现在希望以尽可能小的空间来开展相关技术的研究,同时达到工业上常用的标准。新的设备旨在表明,很快就能够在数据中心使用量子计算机。研究人员证明了紧凑的设备不一定要牺牲性能。这个世界上第一台紧凑型量子计算机的各个构件的尺寸,也需要随量子计算机体积的缩小而缩小。例如,该量子计算机的核心部分,即安装在真空室内的离子阱,只占用了之前所需空间的一小部分。该离子阱是由奥地利量子硬件初创公司Alpine Quantum Technologies (AQT) 提供,AQT是因斯布鲁克大学和奥地利科学院的衍生公司,该公司旨在建立一台商用量子计算机。图2|真空室内的离子阱 (来源:因斯布鲁克大学)其他的构件由德国弗劳恩霍夫协会应用光学和精密机械研究所,和德国精密激光制造商Toptica Photonics提供。这个紧凑的设备可以进行自主操作,并将很快实现在线编程。在构造该量子计算机的过程中,其中一个较为特殊的挑战是需要确保量子计算机的稳定性。量子设备是十分敏感的,在实验室里,通常会得到精心的保护措施,以保证其不受到外部干扰。令人惊讶的是,因斯布鲁克大学的研究团队成功将这一标准应用到了该紧凑型量子设备上,确保其能够安全且不间断地运行。除了稳定性之外,量子计算机能否实现商用的一个决定性因素在于,其可用量子比特的数量。对此,德国政府预设最初建造具有24个完全纠缠的量子比特量子计算原型机的目标。因斯布鲁克大学的量子物理学家们已经实现了这一目标,他们能够单独控制并成功地用新设备纠缠多达24个离子。Thomas Monz表示,团队希望明年能够提供一个多达50个单独可控的量子比特的设备。参考链接:[1]https://www.uibk.ac.at/newsroom/compact-quantum-computers-for-server-centers.html.en[2]https://journals.aps.org/prxquantum/abstract/10.1103/PRXQuantum.2.020343声明:此文出于传递高质量信息之目的,若来源标注错误或侵权,请作者持权属证明与我们联系,我们将及时更正、删除,所有图片的版权归属所引用组织机构,此处仅引用,原创文章转载需授权。发布于 2021-06-21 20:56量子计算量子量子计算机​赞同 6​​6 条评论​分享​喜欢​收藏​申请

Download AQT

Download AQT

Home

Features

Get AQT

Pricing

Support

Download AQT

Hide menu

Download AQT

Pricing

Purchase

Prerequisites

Upgrade policy

License agreement

Download AQT

New, upgrade & evaluation users

 

Download AQT

 (v11.0.5)

Download from mirror site

Installation

To install AQT:

download the install file and unzip into a temp directory

double-click aqtxxx_setup.exe

follow the installation instructions

Evaluation Version

If you are a new AQT user, you will be able to run AQT for 30 days (though some minor functions will be hobbled). This will enable you to determine whether AQT meets your requirements. After this time you will need to either purchase a license or de-install AQT.

Once you purchase an AQT license you enter the key into AQT; this turns AQT from an evaluation version to a licensed version. You will not need to download another install file.

Upgrading

If you are currently running AQT v9 or AQT v10, the install file will de-install AQT v9/v10 and install AQT v11. All your settings and saved files will be retained.

If you are licensed for an earlier version of AQT, you will get a 30-day trial period of AQT v11, after which AQT will revert to an evaluation version. At this point you will need to either de-install AQT v11 or purchase a Version 11 Upgrade license. If you de-install AQT v11 you will need to reinstall AQT v9/v10. Your license key or settings will not be removed during this process so AQT v9/v10 will run as they were previously.

The cost for upgrading to AQT v11 from AQT v10 or an earlier version is US $50. Volume discounts apply - see the pricing page or the purchase page. This version upgrade cost is the same irrespective of the version you are upgrading from or the edition you are upgrading.

Uninstalling AQT

To uninstall AQT:

if you have entered and activated an AQT license, you must first deactivate

the license

uninstall the code with Start > Advanced Query Tool v11 > Uninstall AQT

alternatively, you can uninstall with Control Panel > Add / Remove Programs

Uninstalling AQT will just remove the files placed there during the install process. It will not remove:

your license key and other settings in the registry

your saved queries, AQT History and other files created when AQT runs

Latest builds

The following are provisional builds of newer releases. They haven't undergone the full testing of an official release.

Use with caution and be aware that they may have bugs and incomplete new features

Version

Released

 

AQT v11.0.6a

12 October 2023

Legacy versions

Version

Released

 

AQT v10.1.2q

1 Feb 2023

AQT v10.1.1

6 January 2021

AQT v9.1.4

4 June 2014

AQT v8.2.8

31 Aug 2009

Version History

10 September 2023. Version 11.0.5 released.

14 August 2022. Version 11.0.1 released.

6 January 2021. Version 10.1.1 released.

7 May 2019. Version 10.1.0 released.

12 June 2017. Version 10.0.4 released.

20 Dec 2016. Version 10.0.3 released.

18 March 2015. Version 10.0.2 released.

24 August 2014. Version 10.0.1 released.

4 June 2014. Version 9.1.4 released.

19 September 2013. Version 9.1.3 released.

19 February 2013. Version 9.1.2 released.

9 October 2012. Version 9.1.1 released.

2 April 2012. Version 9.1.0 released.

31 October 2011. Version 9.0.9 released.

15 June 2011. Version 9.0.8 released.

2 March 2011. Version 9.0.7 released.

26 October 2010. Version 9.0.6 released.

28 July 2010. Version 9.0.5 released.

15 May 2010. Version 9.0.4 released.

9 April 2010. Version 9.0.3 released.

31 August 2009. Version 8.2.8 released.

23 April 2009. Version 8.2.7 released.

13 January 2009. Version 8.2.6 released.

16 August 2008. Version 8.2.5 released.

28 April 2008. Version 8.2.4 released.

19 February 2008. Version 8.2.3 released.

26 October 2007. Version 8.2.2 released.

29 September 2007. Version 8.2.1 released.

30 July 2007. Version 8.2.0 Beta released.

11 July 2007. Version 8.1.7 released.

13 April 2007. Version 8.1.6 released.

3 January 2007. Version 8.1.5 released.

13 November 2006. Version 8.1.4 released.

9 October 2006. Version 8.1.3 released.

26 August 2006. Version 8.1.2 released.

30 June 2006. Version 8.1.0 released.

12 March 2006. Version 7.1.7 released.

18 December 2005. Version 7.1.6 released.

16 October 2005. Version 7.1.5 released.

23 August 2005. Version 7.1.4 released.

11 June 2005. Version 7.1.3 released.

18 April 2005. Version 7.1.2 released.

7 March 2005. Version 7.1.1 released.

28 February 2005. Version 7.1.0 released.

20 December 2004. Version 6.1.7 released.

4 October 2004. Version 6.1.6 released.

15 August 2004. Version 6.1.5 released.

16 June 2004. Version 6.1.4 released.

3 June 2004. Version 6.1.3 released.

27 April 2004. Version 6.1.2 released.

1 April 2004. Version 6.1 released.

31 January 2004. Version 6.0.0 Beta released.

12 November 2003. Version 5.6.0 released.

3 September 2003. Version 5.5.8 released.

16 July 2003. Version 5.5.7 released.

19 March 2003. Version 5.5.5 released.

31 March 2003. Version 5.5 released.

16 February 2003. Version 5.5 Beta released.

2 December 2002. Version 5.3 released.

22 October 2002. Version 5.3 Beta released.

22 July 2002. Version 5.2.0 released.

29 June 2002. Version 5.1.2 released.

4 June 2002. Version 5.1 released.

26 Mar 2002. Version 5.0.0 Beta released.

25 Feb 2002. Version 4.2.7 released.

4 Feb 2002. Version 4.2.6 released.

28 Jan 2002. Version 4.2.5 released.

11 Dec 2001. Version 4.2.4 released.

20 Aug 2001. Version 4.2 released.

8 Apr 2001. Version 4.1 "officially launched". Phew!

12 Feb 2001. Version 4.0 Beta released.

29 October 2000. Version 3.4 released.

2 October 2000. Version 3.3 released.

27 May 2000. Version 3.0 released.

7 Feb 2000, Version 2.4 released.

6 Nov 99. Product complete and "officially launched".

Cardett Associates LtdPO Box 153, TakakaNew Zealand

aqt@dbquerytool.com

Privacy policy

Copyright 2002-2023 Cardett Associates Ltd. All rights reserved. AQT is a registered trademark of Cardett Associates Ltd.

Last reviewed on 11 October 2023

X

To verify that you are a human...

Type the above text into the following box

Download AQT