Customize Consent Preferences

We use cookies to help you navigate efficiently and perform certain functions. You will find detailed information about all cookies under each consent category below.

The cookies that are categorized as "Necessary" are stored on your browser as they are essential for enabling the basic functionalities of the site. ... 

Always Active

Necessary cookies are required to enable the basic features of this site, such as providing secure log-in or adjusting your consent preferences. These cookies do not store any personally identifiable data.

No cookies to display.

Functional cookies help perform certain functionalities like sharing the content of the website on social media platforms, collecting feedback, and other third-party features.

No cookies to display.

Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics such as the number of visitors, bounce rate, traffic source, etc.

No cookies to display.

Performance cookies are used to understand and analyze the key performance indexes of the website which helps in delivering a better user experience for the visitors.

No cookies to display.

Advertisement cookies are used to provide visitors with customized advertisements based on the pages you visited previously and to analyze the effectiveness of the ad campaigns.

No cookies to display.

川普在美国宾州巴特勒的一次演讲中遇刺_20240714川普在美国宾州巴特勒的一次演讲中遇刺_20240714
0

SQLite, thepopular embedded database, is transitioning from GNU Autotools to Autosetup for its upcoming release.While the team assures most users will experience minimal impact, they acknowledge some build-level breakage is unavoidable.

This change stems from the inherent differences betweenAutotools and Autosetup, tools designed to configure and customize builds for specific environments based on developer requirements. They generate makefiles, which guide the build process using the make utility.

While GNU Autotools is widely used in open-source projects, the SQLite team found several advantages in Autosetup, developed by embedded Linux consultant Steve Bennett. Autosetup, driven by the TCL scripting language, offers a moreuser-friendly experience compared to GNU Autoconf’s reliance on the GNU M4 macro processor. This makes maintaining Autosetup build files easier. Additionally, Autosetup’s files are contained within the SQLite source code tree, unlike GNU Autotools, which is an external dependency.

The shift to Autosetup aligns with the use of this tool by Fossil SCM, the software configuration manager created by SQLite developer Dr. D Richard Hipp. Stephan Beal, a Fossil contributor, notes in an official article about the transition that for those who simply run ‘./configure && make’, the changes will be minimal.

However, Autotools and Autoconf are not fully compatible. For instance, SQLite’s –enable-tempstore option becomes –with-tempstore in Autosetup, as –enable carries a specific meaning.

The primary concern lies not with developersbuilding SQLite as a standalone tool, but with automated build processes embedding SQLite into other projects. This might require reconfiguration in some cases.

Another issue is Autosetup’s limited platform support compared to Autoconf, potentially affecting certain environments.

Despite these potential challenges, the SQLite team emphasizes the benefits of Autosetup, particularly its user-friendliness and streamlined integration. The transition is expected to enhance the overall build process for SQLite in the long run.

References:


>>> Read more <<<

Views: 0

0

发表回复

您的邮箱地址不会被公开。 必填项已用 * 标注