List of updated and new Recipes

Hello

Instead of opening a new topic for each updated or new recipes I’m working on, this topic will now be used for this purpose.

My architekt-recipes repository will contain all of the recipes and a table will be set up to inform of the status of each Recipe. It will be something like:

Software: Qt
Version: 5.15.3.1
Status: Testing
Build: Yes
Install: Yes
Symlinking: Not Tested
Issues: None reported or an URL to a list of issues

If you have other suggestions on this subject, I’m listening.

On this topic there will be a direct link to the updated or new Recipe.

1 Like

Recipes Table

FVWM3 1.0.4
LibJPEG-Turbo 2.1.0
OpenSSH 8.6p1
Qt 5.15.3.1

1 Like
  • ALSA-Lib
  • ALSA-Topology-Conf
  • ALSA-UCM-Conf
  • Autoconf
  • Autogen
  • Automake
  • Bzip2
  • Cairo
  • Cdparanoia-III
  • Clang
  • CMake
  • Eudev
  • FreeType
  • FVWM3
  • GCC
  • Git
  • GLSLang
  • GLU
  • GMP
  • Graphene
  • GStreamer
  • Guile
  • ISO-Codes
  • JACK2
  • LibB2
  • LibCDDB
  • LibCDIO
  • LibCDIO-Paranoia
  • LibCLC
  • LibDRM
  • LibGLVnd
  • LibInput
  • LibJPEG-Turbo
  • LibOGG
  • LibSamplerate
  • LibSDL
  • LibSndfile
  • LibTheora
  • LibTool
  • Libunistring
  • LibVorbis
  • LibXML2
  • LLVM
  • Mesa
  • MPFR
  • OpenSSH
  • Opus
  • PCRE2
  • Qjackctl
  • Qt3d
  • QtBase
  • QtCharts
  • QtDeclarative
  • QtQuickcontrols2
  • QtShadertools
  • QtSvg
  • QtTools
  • QtVirtualkeyboard
  • QtWayland
  • SPIRV-Headers
  • SPIRV-LLVM-Translator
  • SPIRV-Tools
  • SQLite
  • TSLib
  • Util-Linux
  • Vulkan-Headers
  • Vulkan-Loader
  • Vulkan-Tools
  • Wayland
  • Wayland-Protocols
  • Wayland-Utils
  • Wget

NOTE:
All the recipes are currently only in testing stage, files like BuildDependencies and Dependencies may not be present or not updated and other things … , which make these recipes only for testing purpose in order to improve them.

On the other hand, during this work I’m setting up a list of conventions to follow. For example, a software which offers both, a configure and cmake build system, the cmake will be used in priority.
There is also a naming convention which I’m studying in order to avoid a mess in the recipes list and issue with Compile when two recipes have the same name but written differently.

Thx

1 Like

Here is a first draft of the conventions that I’m following:

Build system priority:

  1. cmake
  2. meson
  3. configure
  1. meson
  2. configure
  1. cmake
  2. configure

Recipe naming scheme:

  1. By software archive name
  2. By software name

Recipe Upper/Lower Case scheme:

  • By program name
  • By program acronym

Examples:

example 1 (program name + software archive name)

  • Program: Theora
  • Archive Name: libtheora-1.1.1.tar.bz2
  • Recipe Name: LibTheora
  • Program: Ogg
  • Archive Name: libogg-1.3.5.tar.gz
  • Recipe Name: LibOgg

example 2: (program acronym + software archive name)

  • Program: Simple DirectMedia Layer (SDL)
  • Archive Name: SDL2-2.0.16.tar.gz
  • Recipe Name: SDL2
  • Program: Tag Image File Format (TIFF)
  • Archive Name: libtiff-v4.3.0.tar.gz
  • Recipe Name: LibTIFF

example 3: (program name + software name)

  • Program: Vulkan Tools
  • Archive Name: v1.2.188.tar.gz (github and gitlab archive naming :thinking:)
  • Recipe Name: Vulkan-Tools
1 Like