ichthyo/LUMIERA.clone
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
LUMIERA.clone/src/SConscript

57 lines
2.2 KiB
Python
Raw Normal View History

SCons overhaul/clean-up: disentangle main build The goal is to make the build scrips more clear at first sight. So move the main build targets into a separate SConscript, to make them similar to the tests, research and tools. The final goal of this makeover is to reduce the main SConstruct as much as possible
2012-01-09 01:32:24 +01:00
# -*- python -*-
##
## SConscript - SCons buildscript for the Lumiera Application.
## Definitions how to build the main tree
##
from Buildhelper import srcSubtree
from Buildhelper import scanSubtree
use import/export instead of passing an artefacts map
2012-01-09 02:56:29 +01:00
Import('env icons config')
SCons overhaul/clean-up: disentangle main build The goal is to make the build scrips more clear at first sight. So move the main build targets into a separate SConscript, to make them similar to the tests, research and tools. The final goal of this makeover is to reduce the main SConstruct as much as possible
2012-01-09 01:32:24 +01:00
SConstruct: reduce the remaining defs no need to use functions anymore, since only the clean and phony targets are left
2012-01-09 05:13:15 +01:00
# define the source file/dirs comprising each artifact to be built.
SCons overhaul/clean-up: disentangle main build The goal is to make the build scrips more clear at first sight. So move the main build targets into a separate SConscript, to make them similar to the tests, research and tools. The final goal of this makeover is to reduce the main SConstruct as much as possible
2012-01-09 01:32:24 +01:00
Global-Layer-Renaming: adapt the build system to the new layer names ...with one exception: I'll retain the name "gui" for the final product to be built.
2018-11-16 15:25:28 +01:00
lLib = env.SharedLibrary('lumierasupport', srcSubtree('lib'), install=True)
Application: Adjustments to the Layer structure During the last months, a lot of gradual changes to policies and guidelines had been finalised and documented. Moreover, recent clarifications regarding memory management in the render engine will lead to a clearer definition of the »Vault« Layer's role, with some ''engine code'' expected to move down. On this occasion, I reworked relevant sections in the documentation to confirm the role that now falls to central parts of the overall architecture. Notably I decided to rename those parts related to the application backbone as »Vessel« — to underpin the more active and defining role they assumed.
2026-02-28 22:55:09 +01:00
lApp = env.SharedLibrary('lumieravessel', srcSubtree('vessel'),addLibs=lLib, install=True)
lVault = env.SharedLibrary('lumieravault', srcSubtree('vault'), addLibs=lLib+lApp, install=True)
lSteam = env.SharedLibrary('lumierasteam', srcSubtree('steam'), addLibs=lLib+lApp+lVault, install=True)
SCons overhaul/clean-up: disentangle main build The goal is to make the build scrips more clear at first sight. So move the main build targets into a separate SConscript, to make them similar to the tests, research and tools. The final goal of this makeover is to reduce the main SConstruct as much as possible
2012-01-09 01:32:24 +01:00
Global-Layer-Renaming: fix handling of GuiResources in the build the new structure causes them now to be installed into $TARGET/stage which is simply not what I want. I still consider $TARGET/gui the better choice, since an administrator or packager is not aware of our layer namings. The existing solution was half baked anyway, it did not really replicate the source tree. On the other hand, I want to retain the location of the CSS files within the GUI tree, since I consider it a good practice, to keep "code-like" resources with the actual code, and not far away in some arcane "data" directory. No I've noticed, that the env.GuiResource() function is only used once, for this very task. So, for the time being, we can keep it simple and deditaced to that task, i.e we pick up all CSS files we find and install it into a single target directory. NOTE: this issue has brought to my attention two further, completely unrelated issues * Ticket #1192 (Lumiera hangs on failed GUI start) * The ProcDispatcher does an idle wait, due to an error in timed-wait implementation
2018-11-16 18:18:33 +01:00
# in reverse dependency order
core = lSteam+lVault+lApp+lLib # used to build the core application
support_lib = lLib # use to link against the support lib only
Application: Adjustments to the Layer structure During the last months, a lot of gradual changes to policies and guidelines had been finalised and documented. Moreover, recent clarifications regarding memory management in the render engine will lead to a clearer definition of the »Vault« Layer's role, with some ''engine code'' expected to move down. On this occasion, I reworked relevant sections in the documentation to confirm the role that now falls to central parts of the overall architecture. Notably I decided to rename those parts related to the application backbone as »Vessel« — to underpin the more active and defining role they assumed.
2026-02-28 22:55:09 +01:00
vessel_lib = lApp+support_lib # use to link against the application-framework
vault_lib = lVault+vessel_lib # use to link against the low-level backend
core_lib = lSteam+vault_lib # use to link against the core application
SCons overhaul/clean-up: disentangle main build The goal is to make the build scrips more clear at first sight. So move the main build targets into a separate SConscript, to make them similar to the tests, research and tools. The final goal of this makeover is to reduce the main SConstruct as much as possible
2012-01-09 01:32:24 +01:00
use import/export instead of passing an artefacts map
2012-01-09 02:56:29 +01:00
lumiera = ( env.Program('lumiera', ['lumiera/main.cpp'] + core, install=True)
+ config
)
SCons overhaul/clean-up: disentangle main build The goal is to make the build scrips more clear at first sight. So move the main build targets into a separate SConscript, to make them similar to the tests, research and tools. The final goal of this makeover is to reduce the main SConstruct as much as possible
2012-01-09 01:32:24 +01:00
SConstruct: reduce the remaining defs no need to use functions anymore, since only the clean and phony targets are left
2012-01-09 05:13:15 +01:00
# Install the lumiera application:
# symlink the executable into the bin dir
Build: fix problem that prevented installation into absolute path ...funny enough I never noticed this obvious mistake, since I never install software directly into my system, while the DEB-build does not use absolute paths... Solution: * SCons has this speical convention that a path prefixed with '#' is resolved relative to the root of the build (where the SConstruct resides) * now we apply this automatically to the two relevant settings ** INSTALLDIR ** TARGDIR * but only (conditionally) if the configured path is relative, not absolute As a consequence, most other hard-coded usages of the '#'-prefix can then be dropped
2025-11-19 22:40:08 +01:00
env.SymLink('$DESTDIR/bin/lumiera',env.path.installExe+'lumiera','../lib/lumiera/lumiera')
SConstruct: reduce the remaining defs no need to use functions anymore, since only the clean and phony targets are left
2012-01-09 05:13:15 +01:00
Tests: build an link a test-support library This is something I wanted to clean-up since a very long time indeed, but always postponed it, since it requires a lot of nasty clean-up and disentangling.... Several parts had been stashed away into `src/lib/test`, which are not really related: * the testrunner and testsuite builder * generic helper utilities * specialised test-support facilities, e.g. the EventLog This changeset introduces a new top-level test folder and a namespace `::test` Code from this folder is linked into a shared library `libtestsupport.so`, which resides in the linkage hierarchy between »Vessel« and »Vault«, yet is no longer part of the Lumiera application and only linked into the test-suite.
2026-03-06 21:34:20 +01:00
# Unit/Integration test support
test_support = env.SharedLibrary('testsupport', srcSubtree('test'), addLibs=vessel_lib, install=False)
SCons overhaul/clean-up: disentangle main build The goal is to make the build scrips more clear at first sight. So move the main build targets into a separate SConscript, to make them similar to the tests, research and tools. The final goal of this makeover is to reduce the main SConstruct as much as possible
2012-01-09 01:32:24 +01:00
# building Lumiera Plugins
clean-up: trifles
2025-06-07 23:59:57 +02:00
plugins = [] # currently none
SCons overhaul/clean-up: disentangle main build The goal is to make the build scrips more clear at first sight. So move the main build targets into a separate SConscript, to make them similar to the tests, research and tools. The final goal of this makeover is to reduce the main SConstruct as much as possible
2012-01-09 01:32:24 +01:00
# the Lumiera GTK GUI
envGtk = env.Clone()
build/platform: make lib SigC++ available for GUI test code Explanation: sigC++ was already linked as transitive dependency from gtkmm, since it is used for the "signal-slot" system wihin GTK. But now we want to use sigC++ itself from our generic UI-Backbone, so we need to pick up the additional compiler and linker flags and use them when building the relevant parts of both the application and the test suite
2015-12-25 03:06:33 +01:00
envGtk.mergeConf(['gtkmm-3.0','sigc++-2.0','gthread-2.0','cairomm-1.0','gdl','xv','x11','xext','sm'])
SCons overhaul/clean-up: disentangle main build The goal is to make the build scrips more clear at first sight. So move the main build targets into a separate SConscript, to make them similar to the tests, research and tools. The final goal of this makeover is to reduce the main SConstruct as much as possible
2012-01-09 01:32:24 +01:00
Global-Layer-Renaming: adapt the build system to the new layer names ...with one exception: I'll retain the name "gui" for the final product to be built.
2018-11-16 15:25:28 +01:00
guimodule = envGtk.LumieraPlugin('gtk_gui', srcSubtree('stage') + core, install=True)
Global-Layer-Renaming: fix handling of GuiResources in the build the new structure causes them now to be installed into $TARGET/stage which is simply not what I want. I still consider $TARGET/gui the better choice, since an administrator or packager is not aware of our layer namings. The existing solution was half baked anyway, it did not really replicate the source tree. On the other hand, I want to retain the location of the CSS files within the GUI tree, since I consider it a good practice, to keep "code-like" resources with the actual code, and not far away in some arcane "data" directory. No I've noticed, that the env.GuiResource() function is only used once, for this very task. So, for the time being, we can keep it simple and deditaced to that task, i.e we pick up all CSS files we find and install it into a single target directory. NOTE: this issue has brought to my attention two further, completely unrelated issues * Ticket #1192 (Lumiera hangs on failed GUI start) * The ProcDispatcher does an idle wait, due to an error in timed-wait implementation
2018-11-16 18:18:33 +01:00
resources = ( [env.GuiResource(f) for f in scanSubtree('stage', ['*.css'])] # note: collected into one target dir
)
use import/export instead of passing an artefacts map
2012-01-09 02:56:29 +01:00
gui = ( guimodule
Global-Layer-Renaming: fix handling of GuiResources in the build the new structure causes them now to be installed into $TARGET/stage which is simply not what I want. I still consider $TARGET/gui the better choice, since an administrator or packager is not aware of our layer namings. The existing solution was half baked anyway, it did not really replicate the source tree. On the other hand, I want to retain the location of the CSS files within the GUI tree, since I consider it a good practice, to keep "code-like" resources with the actual code, and not far away in some arcane "data" directory. No I've noticed, that the env.GuiResource() function is only used once, for this very task. So, for the time being, we can keep it simple and deditaced to that task, i.e we pick up all CSS files we find and install it into a single target directory. NOTE: this issue has brought to my attention two further, completely unrelated issues * Ticket #1192 (Lumiera hangs on failed GUI start) * The ProcDispatcher does an idle wait, due to an error in timed-wait implementation
2018-11-16 18:18:33 +01:00
+ resources
use import/export instead of passing an artefacts map
2012-01-09 02:56:29 +01:00
+ icons
)
SCons overhaul/clean-up: disentangle main build The goal is to make the build scrips more clear at first sight. So move the main build targets into a separate SConscript, to make them similar to the tests, research and tools. The final goal of this makeover is to reduce the main SConstruct as much as possible
2012-01-09 01:32:24 +01:00
Tests: build an link a test-support library This is something I wanted to clean-up since a very long time indeed, but always postponed it, since it requires a lot of nasty clean-up and disentangling.... Several parts had been stashed away into `src/lib/test`, which are not really related: * the testrunner and testsuite builder * generic helper utilities * specialised test-support facilities, e.g. the EventLog This changeset introduces a new top-level test folder and a namespace `::test` Code from this folder is linked into a shared library `libtestsupport.so`, which resides in the linkage hierarchy between »Vessel« and »Vault«, yet is no longer part of the Lumiera application and only linked into the test-suite.
2026-03-06 21:34:20 +01:00
Export('lumiera core core_lib vessel_lib vault_lib support_lib test_support plugins envGtk guimodule gui')
Reference in a new issue Copy permalink