- May 11, 2023
-
-
Simon Rose authored
This removal allows us to remove the `hdrs` target from every module; there were only two modules that still used it, and they have both been fixed.
-
- May 04, 2023
-
-
Simon Rose authored
-
Simon Rose authored
-
- Feb 08, 2023
-
-
Simon Rose authored
The purpose of this is to remove the dependency on tclx, a non-standard package.
-
- Dec 16, 2022
-
-
Simon Rose authored
-
Simon Rose authored
-
Simon Rose authored
-
- Nov 30, 2022
-
-
Lucas Magalhães authored
-
- Nov 21, 2022
-
-
Simon Rose authored
-
- Nov 03, 2022
-
-
Anders Lindh Olsson authored
-
Anders Lindh Olsson authored
-
Anders Lindh Olsson authored
-
- Oct 13, 2022
-
-
Simon Rose authored
-
- Sep 14, 2022
-
-
Simon Rose authored
If a user runs the build from the E3_SITEMODS_PATH, then it can happen that false dependencies get registered due to how the generated .d files are parsed to determine module dependencies. Specifically, if you have header file being used that is located at ${E3_SITEMODS_PATH}/e3-module/module/src/header.h and it is _not_ being installed, then the dependency parsing script will see a dependency as an absolute path, and so register that your module depends on the module `e3-module` version `module`, which is obviously not what was intended. While we don't want to stricly _prevent_ a user from building there, it seems wise to _warn_ a user that there may be unintended consequences.
-
- Aug 18, 2022
-
-
Lucas Magalhães authored
The test rule for e3 modules actually does a cellinstall and run the tests inside this temporary installation. The cellinstall needs to overwrite some path variables to work this variables were not accessible through the test rule as they are just changed if cell is on MAKECMDGOALS. This made impossible to use the standard path variables inside module's custom test rules. To fix it the same mechanism used in cellinstall is implemented for test and the variables paths are now overwritten. This makes possible ie. to use E3_MODULES_INSTALL_LOCATION_BIN inside custom test rules. This commit also introduces an unwanted behavior. As the test rule is now overwriting the standard path variables it cannot longer be along with the install rule. For example, running `make test install` will install the module inside the test dir. This is a known issue for cellinstall as well and a restructure of the Makefile code should be made to isolate the rules.
-
- Aug 17, 2022
-
-
Lucas Magalhães authored
-
- Aug 09, 2022
-
-
Lucas Magalhães authored
-
- May 30, 2022
-
-
Simon Rose authored
-
Simon Rose authored
-
Simon Rose authored
-
- Apr 07, 2022
-
-
Alfio Rizzo authored
-
- Mar 21, 2022
-
-
Simon Rose authored
-
- Mar 15, 2022
-
-
Juntong Liu authored
-
Juntong Liu authored
-
- Feb 09, 2022
-
-
Anders Lindh Olsson authored
-
- Jan 17, 2022
-
-
Juntong Liu authored
-
- Jan 16, 2022
-
-
Juntong Liu authored
-
- Jan 13, 2022
-
-
Simon Rose authored
This was needed since we had to have a way for the test suites to override this value. However, this can also be acheived by writing to configure/CONFIG_CELL.local. This was added in a refactoring of run_make to make more clear what variables can be passed there.
-
- Jan 12, 2022
-
-
Simon Rose authored
-
- Dec 10, 2021
-
-
Wayne Lewis authored
-
Wayne Lewis authored
-
- Nov 12, 2021
-
-
Simon Rose authored
-
- Nov 11, 2021
-
-
Simon Rose authored
-
- Nov 01, 2021
-
-
Simon Rose authored
Local source mode can theoreticaly run 'make devbuild' and other related targets. However, this yields somewhat undefined behaviour, since those will potentially be missing configuration data or clashing with the regular build location. There is no reason to include dev targets for local source mode, so they should be removed.
-
Simon Rose authored
-
Simon Rose authored
-
Simon Rose authored
-
Simon Rose authored
-
Simon Rose authored
-
Simon Rose authored
-