| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
Generates file contains command line cmake run to reproduce previous
cmake pass through.
CI service use this run file to start pipeline with needs cmake
configuration that developer was make.
Following code pushing workflow: Commit pushed to a code review system
(`CMakeReplication.txt` required) -> CI service intercepts changes ->
Pipeline start using passed in commit cmake replication command -> CI
submit pipeline finished status
Signed-off-by: Alexey Gavrilov <alexey.gavrilov@mail.com>
|
|
Implements a new feature module function `outFeaturesToFile` to output all
available features into 'CMakeFeatureOut.txt' file. Format of that file
is set of FEATURE_<feature>_<property> variables like defines in `CMakeCache.txt`.
Will to use as proxy between cmake and configuration tools. Those
utilities read features out file to build configuration kernel tree.
Signed-off-by: Alexey Gavrilov <alexey.gavrilov@mail.com>
|
|
Feature is abstraction around cmake build target used to contains
descriptive information in target properties as name, dependencies, tags
and etc.. Feature creation divided by three processes: start creation
process, fields filling and stop creation process. Start creation
process means passed target is handle now, and stop process is finish to
handle a current feature. Using this way helps to construct correct
features hierarchy and simplify kernel configuration process.
This will use in standalone automating kernel configuration tools:
1. Cmake generate a features file with information about them all.
2. Tool read this file and display features tree.
3. User start to configuring his kernel.
Signed-off-by: Alexey Gavrilov <alexey.gavrilov@mail.com>
|
|
Copyright disclaimer and copyright note are prepending to a every source
file.
Add license section in the `README.md` file.
Create the LICENSE` file with license information.
Signed-off-by: Alexey Gavrilov <alexey.gavrilov@mail.com>
|
|
Reinforce of compiler, C runtime, architecture checks at cmake
configuration.
Compiler check means continue building at the cmake configure
stage only for supported compilers. Use unsupported compiler
involves immediate build process stopping.
C runtime check means finding of runtime objects. Especially for
*crtbegin.o* and *crtend.o* files.
Architecture means *ObjectiveProject_ARCHITECTURE* variable is set.
That variable configure at toolchain file by default and cannot
override if toolchain file is passed.
TODO
- Image creation
- Build under window platform (optional)
Signed-off-by: Alexey Gavrilov <alexey.gavrilov@mail.com>
|
|
Fix in *nasm* files - set architecture bitness.
Move compiler flags from *toolchain* file to *requirements target*
considering cmake files. This solution allows available of
multi-configurations generators to pass compiler options
without affecting on single-configuration generators.
TODO
- Debug information
- Image creation
- Build under window platform (optional)
Signed-off-by: Alexey Gavrilov <alexey.gavrilov@mail.com>
|
|
Two toolchain files for clang and gcc compilers under x86 platform.
Debug flags also passed at the configure time.
Signed-off-by: Alexey Gavrilov <alexey.gavrilov@mail.com>
|
|
Multi-target architecture implementation:
each root source code directory presents the one
*INTERFACE* target to it's subdirectory subtargets
that link only as *STATIC* library.
For instance, *arch* directory presents *Architecture* target
then *Architecture* target has *CPUID*, *IO*, *PORT*
and etc. dependencies
Exact order of linking targets is: boot.o CRTIBUNDLE <TARGETS> CRTNBUNDLE.
Sequence destruction cause to UB. Please to pay attention to this.
TODO
- Debug information
- Build type
- Toolchain file
- Image creation
- Build by WinGW compiler on Windows platform (optional)
Signed-off-by: Alexey Gavrilov <alexey.gavrilov@mail.com>
|
