README.md
1Lumina
2======
3This is the official source tree for the Lumina Desktop Environment.
4
5For additional information about the project, please browse the official website for documentation, screenshots, and more:
6https://lumina-desktop.org/
7
8**Community Chat Channels:**
9 - Telegram: ["Lumina Desktop" public channel](https://t.me/luminadesktop)
10
11**Lumina Project Info: Table of Contents**
12
13- [Description](#description)
14- [Latest Versions](#latestversions)
15- [Translations](#translations)
16- [How to file bug reports or feature requests](#filebugs)
17- [How to build from source](#buildfromsource)
18
19---
20
21Description <a name="description"></a>
22=====
23
24The Lumina Desktop Environment is a lightweight system interface that is designed for use on any Unix-like operating system. It takes a plugin-based approach, allowing the entire interface to be assembled/arranged by each individual user as desired, with a system-wide default layout which can be setup by the system administrator. This allows every system (or user session) to be designed to maximize the individual user's productivity.
25
26Supported operating systems include (but are not limited to):
27 * BSD: TrueOS, FreeBSD, OpenBSD, NetBSD, DragonflyBSD, GNU/kFreeBSD
28 * Linux: Gentoo, Debian, "Generic" Linux (including Arch, Ubuntu, and more)
29
30
31Latest Versions <a name="latestversions"></a>
32----
33Click [HERE](https://github.com/lumina-desktop/lumina/releases) to see all the available releases for the Lumina Desktop.
34
35Click [HERE]() to see all the available branches of the Lumina Desktop source tree (includes development versions: X.Y.(Z > 0)).
36The master branch is where all development is performed and tested before the next version is tagged. Additionally, every version (development **and** release) of the project gets branched off of master at the time the version is tagged, so older versions may be fetched/patched/used as desired.
37
38Occasionally there may be patches committed for particular versions which are not included in the static "release" archives. On the release page these can be identified by a note stating the release is a number of commits behind it's corresponding branch. In this situation, it may be preferable to fetch/use the corresponding branch of the source tree rather than the static archive if the patch(es) which were committed impact your particular operating system.
39
40Translations <a name="translations"></a>
41----
42**Legacy Versions (1.0.0 and older)**
43
44All the translation files for Lumina are available through the trueos/lumina-i18n reposotiry (Qt5+ only). Please follow the directions in that repository for installing localization files.
45
46**Version 1.1.0+**
47
48All the translations for Lumina are contained within this repository directly (the i18n/ subdirectories within each project source tree). To include these translation files, the `WITH_I18N` build flag must be set at compilation time, in which case the translation files will automatically get synced/built alongside the corresponding binaries.
49
50To submit translations, please edit those i18n/*.ts translation files and submit a pull request to this repository.
51
52How to file bug reports or feature requests <a name="filebugs"></a>
53----
54Please create a ticket through the [GitHub issues tracker](https://github.com/lumina-desktop/lumina/issues) on this repository. Similarly, if you want to send in patches or other source contributions, please send in a GitHub pull request so that it can get reviewed/committed as quickly as possible.
55
56
57How to build from source <a name="buildfromsource"></a>
58----
591) Checkout the source repo to your local box (GitHub gives a few methods for this)
60
61Examples:
62* To checkout the master branch of the repo, run `git clone https://github.com/lumina-desktop/lumina` to create a "lumina" directory with a local copy of the source tree.
63* To update an exising checkout of the Lumina repo, run "git pull" while within your local copy of the source tree.
64
652) In a terminal, change to the lumina repo directory (base dir, not one of the sub-projects)
66
673) Run "qmake" on your local system to turn all the Qt project files (*.pro) into Makefiles
68 * NOTE 1: The Qt5 version of qmake is located in /usr/local/lib/qt5/bin/qmake on FreeBSD, other OS's may have slightly different locations or names for qmake (such as qmake-qt5 for example)
69 * NOTE 2: Check the terminal output of the qmake command to ensure that your OS build settings were loaded properly. Here is an example:
70
71> Project MESSAGE: Build OS Info: FreeBSD, amd64, FreeBSD 10.2-RELEASE-p11 #0: Thu Jan 14 15:48:17 UTC 2016 root@amd64-builder.pcbsd.org:/usr/obj/usr/src/sys/GENERIC
72
73> Project MESSAGE: Build Settings Loaded: FreeBSD
74
75 * Build Note: Compile-time options may be set at this time using qmake. This is typically not needed unless you are setting up Lumina for automated build/packaging. If the automatically-detected build settings for your particular OS are invalid or need adjustment, please update the "OS-detect.pri" file as needed and send in your changes so that it can be corrected for future builds.
76 * PREFIX: Determines the base directory used to install/run Lumina ("/usr/local" by default)
77 Example: `qmake PREFIX=/usr/local`
78 * LIBPREFIX: Determines the location to install the Lumina library ("PREFIX/lib" by default)
79 Example: `qmake LIBPREFIX=/usr/local/lib`
80 * DESTDIR: An optional directory where the compiled files will be placed temporary (such as for packaging/distributing via some other system).
81 Example: `qmake DESTDIR=/my/build/dir`
82 * DEFAULT_SETTINGS: An optional flag to install the default settings/wallpaper for some other operating system (Note: Make sure the OS name is capitalized appropriately!)
83 Example: `qmake DEFAULT_SETTINGS=TrueOS`
84 * WITH_I18N: Generate/install the translation files. (Note: For versions prior to 1.1.0, do *not* use this flag! The localization files for versions up through 1.0.0 are available in the lumina-i18n repository instead).
85 Example: `qmake CONFIG+=WITH_I18N`
86 * debug: (not recommended for release builds) Do not strip all the debugging information out of the binaries (useful for performing backtraces on builds that crash or for other development tests)
87 Example: `qmake CONFIG+=debug`
88
894) Run "make" to compile all the Lumina projects (can be done as user)
90
915) Run "make install" to install the Lumina desktop on your local system (requires admin/root privileges usually)
92
936-optional) Run "make distclean" to clean up all the build files in the Lumina source tree. (go back to step 3 later)
94
95NOTE: The Lumina project is naturally broken down into a number of individual "sub-projects" which are designed to be built and packaged individually. These sub-projects all use the same overall dependencies, but might have differing library/runtime dependencies or even an alternate minimum-supported version of Qt.
96The sub-projects are broken down as follows:
97 * [lumina-core](https://github.com/lumina-desktop/lumina/tree/master/src-qt5/core): The core of the project (desktop itself)
98 * [lumina-coreutils](https://github.com/lumina-desktop/lumina/tree/master/src-qt5/core-utils): The core utilities for configuring/managing the desktop
99 * [desktop-utilities](https://github.com/lumina-desktop/lumina/tree/master/src-qt5/desktop-utils): Various support utilities for desktop systems. Every one of these utilities should be independently packaged.
100
101The desktop utilities are gradually getting migrated out into their own repositories under the lumina-desktop github organization as well. These repositories are open for individual versioning and updates if an individual would like to "adopt" these utilities and develop them independantly of the release schedule for the desktop components themselves.
102