shundhammer

Doxygen-Generated Autodocs on GitHub Pages

General Idea

GitHub offers hosting documentation on GitHub Pages. This can be done once for each GitHub user, for each GitHub organization, for each GitHub project.

If the process for building the autodocs is already in place (as is the case for libyui), it is just a matter of generating them, moving them to the right place, and deploying them to the project's GitHub Pages.

shundhammer

Finding Files that are Shadowed by a Mount

Outdated; moved to a new location:

https://github.com/shundhammer/qdirstat/blob/master/doc/Shadowed-by-Mount.md

shundhammer

YaST Installer Requirements

What to Install

• Different types of SUSE Linux distributions:

  • SLES / SLED
  • openSUSE Tumbleweed
  • openSUSE Leap

• Simple default product (default installation)

shundhammer

The New (2021/01) CMake Build System for Libyui

• Requirements: https://gist.github.com/shundhammer/d96a63a1cab8245d20c2e3556238a114
• PR: libyui/libyui-old#178

Overview

• Simple
• No voodoo
• Conforming to standard CMake docs

shundhammer

The new libyui CMake Build System and "make doc"

Building doxygen Autodocs

CMake supports generating doxygen-based autodocs pretty much out of the box; it's little more than

find_package( Doxygen REQUIRED dot )
doxygen_add_docs( doc ../src )

shundhammer

Libyui Packaging with the New CMake Build Environment

Current Situation

• Lots of different libyui*.rpm packages from lots of individual, independent GitHub repos

• Most of those packages have a -devel subpackage for the header files and a -doc subpackage for auto-generated doxygen documentation

• The main package of each has a .spec file and a .changes file in the repo's package/ subdirectory

shundhammer

Building libyui with the new CMake Build Environment

Compiler options can now easily be changed in the toplevel CMakeLists.txt:

add_compile_options( "-Wall" )
add_compile_options( "-O3 -g" )

No Compiler Options (GCC Defaults):

shundhammer

YaST libyui Build System Requirements

Current Situation

Custom CMake with a convoluted, hard to understand set of centralized .cmake include files and a toplevel CMakeList.txt that is symlinked to the central one somewhere in a system directory. In each project repo, information is scattered among a dozen file snippets that are magically included from somewhere.

Nobody understands the control flow of that, so everybody avoids touching that,

shundhammer

YaST Partitioner Menus

Other Versions:

• Extended
• Simplistic 01

Simplistic Version 02

• System

shundhammer

YaST Partitioner Menus

Other Versions:

• Extended
• Simplistic 02

Simplistic Version 01