TBOOX Open Source Project

• xmake v2.5.7 released, Use lockfile to freeze package dependencies and Vala/Metal language support

  2021-08-29

  xmake

  xmake  lua  C/C++  lock  package  vala

  xmake is a lightweight cross-platform build tool based on Lua. It uses xmake.lua to maintain project builds. Compared with makefile/CMakeLists.txt, the configuration syntax is more Concise and intuitive, it is very friendly to novices, and you can get started quickly in a short time, allowing users to focus more on actual project development.

  In this version, we have added a lot of new features. Not only did we increase the compilation support for Vala and Metal languages, we also improved the package dependency management, which can support the locking and updating of dependent packages like npm/package.lock, so The user’s project will not be affected by the update and change of the upstream package repository.

  In addition, we also provide some more practical rules. For example, utils.bin2c allows users to easily and quickly embed some binary resource files into the code, and obtain relevant data in the form of header files.

  • Github
  • Document

  New feature introduction

  Added Vala language support

  In this version, we can already initially support the construction of Vala programs, just apply the add_rules("vala") rule.

  At the same time, we need to add some dependency packages, among which the glib package is necessary because Vala itself will also use it.

  add_values("vala.packages") is used to tell valac which packages the project needs, it will introduce the vala api of the relevant package, but the dependency integration of the package still needs to be downloaded and integrated through add_requires("lua").

  E.g:

  add_rules("mode.release", "mode.debug")
  
  add_requires("lua", "glib")
  
  target("test")
      set_kind("binary")
      add_rules("vala")
      add_files("src/*.vala")
      add_packages("lua", "glib")
      add_values("vala.packages", "lua")
  

  More examples: Vala examples

  Added package dependency lock support

  This feature is similar to npm’s package.lock and cargo’s cargo.lock.

  阅读中文 Read All

  ---

• xmake v2.5.6 released, Improve compatibility of pre-compiled binary package

  2021-07-26

  xmake

  xmake  lua  C/C++  mirror  package

  xmake is a lightweight cross-platform build tool based on Lua. It uses xmake.lua to maintain project builds. Compared with makefile/CMakeLists.txt, the configuration syntax is more Concise and intuitive, it is very friendly to novices, and you can get started quickly in a short time, allowing users to focus more on actual project development.

  This is a stability fix version, which mainly fixes and improves some compatibility issues related to pre-compiled binary packages. In addition, some useful interfaces have been added to set the default compilation platform, architecture and mode, as well as the allowed compilation platform, architecture list, and so on.

  • Github
  • Document

  New feature introduction

  Fix windows precompiled package compatibility

  The previous version provided preliminary support for the installation of pre-compiled packages under Windows, but because the compatibility of the toolset version was not considered, if the user’s VS version is too low, link problems will occur when the package is integrated.

  According to the official description of ms, the binary library of msvc is backward compatible with the version of toolset. https://docs.microsoft.com/en-us/cpp/porting/binary-compat-2015-2017?view=msvc-160

  You can mix binaries built by different versions of the v140, v141, and v142 toolsets. However, you must link by using a toolset at least as recent as the most recent binary in your app. Here’s an example: you can link an app compiled using any 2017 toolset (v141, versions 15.0 through 15.9) to a static library compiled using, say, Visual Studio 2019 version 16.2 (v142), if they’re linked using a version 16.2 or later toolset. You can link a version 16.2 library to a version 16.4 app as long as you use a 16.4 or later toolset.

  In other words, the cloud uses the library compiled by v141, and the user’s msvc toolset can be compatible and supported as long as it is >=141.

  Therefore, we have improved the pre-compilation logic of the cloud, and pre-compiled the two toolsets of vs2015/14.16 and vs2019/14.29 respectively, and then xmake will select the best compatible version library to download and integrate according to the user’s msvc version of toolset.

  阅读中文 Read All

  ---

• xmake v2.5.5 released, Support to download and install precompiled image packages

  2021-06-30

  xmake

  xmake  lua  C/C++  mirror  package

  xmake is a lightweight cross-platform build tool based on Lua. It uses xmake.lua to maintain project builds. Compared with makefile/CMakeLists.txt, the configuration syntax is more Concise and intuitive, it is very friendly to novices, and you can get started quickly in a short time, allowing users to focus more on actual project development.

  In version 2.5.5, we continue to improve the experience of remote package integration, realize the pre-compiled package in the cloud, and then directly download the integrated pre-compiled binary package. This can greatly reduce the installation time of some packages that are very slow to compile.

  In addition, in the new version, we have also re-implemented the new version of the local package generation scheme, which fully supports add_requires and add_packages seamlessly. From then on, remote packages and local packages can be maintained in a unified way.

  • Github
  • Document

  New feature introduction

  Download and install the pre-compiled package

  Each time you install a package by the built-in package manager of xmake, you must download the corresponding package source code, and then perform local compilation and installation integration. This is for some large packages that compile very slowly, and some packages that rely on a lot of compilation tools. It will be very slow.

  Especially on windows, not only the dependence of the third party package on the compilation environment is more complicated, but also many packages and compilation are very slow, such as boost, openssl and so on.

  To this end, we implement cloud pre-compilation of packages based on github action, and pre-compile all commonly used packages, and then store them in build-artifacts under Releases of the repository.

  Then, when we install the package, we will automatically download it from the binary image package source to achieve rapid integration (currently only pre-compiled windows packages are supported, and will be gradually released to other platforms in the future).

  We will pre-compile various configuration combinations such as plat/arch/MT/MD/static/shared of each package, and accurately pull the packages that users actually need according to the unique buildhash. All compiled products will be compressed and packaged with 7zip, as follows Picture:

  

  阅读中文 Read All

  ---

• xmake v2.5.4 Released, Support apt/portage package manager and improve xrepo shell

  2021-05-15

  xmake

  xmake  lua  C/C++  apt  portage  shell  package

  xmake is a lightweight cross-platform build tool based on Lua. It uses xmake.lua to maintain project builds. Compared with makefile/CMakeLists.txt, the configuration syntax is more Concise and intuitive, it is very friendly to novices, and you can get started quickly in a short time, allowing users to focus more on actual project development.

  In version 2.5.4, we added support for Apt and Portage package managers. On Ubuntu/Gentoo, we can also use add_requires to quickly integrate the packages they provide.

  And we have also improved the support for the Vcpkg package manager, and added support for the installation of arm/arm64 architecture packages.

  In addition, we have also enhanced the xrepo env shell environment. You can load a shell environment with a specific package configuration by configuring a series of add_requires package configurations in xmake.lua.

  • Github
  • Document

  New feature introduction

  New package manager support

  Add dependency package of ubuntu/apt

  Now we support the use of apt to integrate dependent packages, and will also automatically find packages that have been installed on the ubuntu system.

  add_requires("apt::zlib1g-dev", {alias = "zlib"})
  
  target("test")
      set_kind("binary")
      add_files("src/*.c")
      add_packages("zlib")
  

  Add gentoo/portage dependency package

  We also support the use of Portage to integrate dependency packages, and will automatically find packages already installed on the Gentoo system.

  add_requires("portage::libhandy", {alias = "libhandy"})
  
  target("test")
      set_kind("binary")
      add_files("src/*.c")
      add_packages("libhandy")
  

  阅读中文 Read All

  ---

• C/C++ build system, I use xmake

  2021-05-03

  xmake

  xmake  lua  C/C++  buildsystem

  What is XMake?

  XMake is a modern C/C++ build system based on Lua.

  Its grammar is concise and easy to use, friendly to novices, even if you don’t know Lua at all, you can get started quickly, and it is completely free of any dependencies, lightweight, and cross-platform.

  At the same time, it is also a self-satisfied build system with a powerful package management system and a fast build engine.

  Compared with Ninja/Scons/Make as Build backend, CMake/Meson as Project Generator, and XMake not only provides Build backend and Project Generator at the same time, it also provides a built-in package manager.

  xmake = Build backend + Project Generator + Package Manager
  

  Therefore, you only need to install an XMake installation package that is less than 3M, and you don’t need to install other tools. You don’t even need to install make, and you don’t need to install heavyweight runtime environments such as Python and Java. You can quickly start your C/C++ development journey.

  Maybe someone will say that the compiler always needs to be installed. This is not necessary, because XMake’s package management also supports automatically to pull remote compilation toolchains, such as llvm, Mingw, Android NDK or cross-compilation toolchain.

  Why do XMake

  Whenever discussing XMake with others in the Reddit community, everyone will always use the following picture to complain.

  

  Although I was a little helpless and numb by the complaints, I still want to explain that the original intention of XMake was not to split the C/C++ ecology. On the contrary, XMake reuses the existing ecology as much as possible.

  At the same time, it also allows users to have the same good experience as other languages when developing C/C++ projects, such as Rust/Cargo, Nodejs/Npm, Dlang/Dub, instead of looking for the third package everywhere, and studying how to transplant and compile. toss.

  Therefore, if you don’t know XMake, please don’t draw conclusions too early, you can try it first, or take a moment to read the detailed introduction below.

  Features and advantages of XMake

  People often ask me what is special about XMake and what are the advantages compared to existing build tools such as CMake and Meson. Why should I use XMake instead of CMake?

  Let me talk about the features and advantages first, XMake has the following points:

  • Concise and easy-to-learn configuration syntax, non-DSL
  • Powerful package management, support semantic version, toolchain management
  • Lightweight enough, no dependence
  • Fast, the build speed is as fast as Ninja
  • Simple and convenient multi-platform and toolchain switching
  • Complete plugin system
  • Flexible build rules
  阅读中文 Read All

  ---