-
Notifications
You must be signed in to change notification settings - Fork 61
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
autotools or cmake support #2
Comments
@sledz Issue duly noted. The support for autotools or cmake is on our roadmap. We will add your +vote to it & see if we can schedule it any sooner. In the mean time, if you are not compiling this code on the architecture of choice (ARM, MIPS etc.) you can cross compile using the following make command:
You can replace the arm-linux-gnueabi-gcc with the toolchain that you need. I updated the Makefile to use the correct archiver, so please pull/clone the latest develop & the above make command will work. Let me know if this solution works for you. |
The meson build system is a build system with many advantages over others, and one I consider to be the best. It is one of the fastest build systems, easy to understand, and extensible (for example a target can be defined to automatically build docs). It supports all platforms the other soltutions do (Linux, Windows, FreeBSD) and is easy to use when cross compiling via a cross file (such as with MingW). It can also programatically generate the version, instead of needing to edit a header file every time. On my Linux computer, meson (configure) took 0.65s and ninja (build) took 16.62s, while the make-based build system took 30.22s. See https://mesonbuild.com/Overview.html and https://mesonbuild.com/Comparisons.html for me info on the meson build system. Meson requires all subprojects to be in the subprojects directory. It unfortunately does not support symlinks in the subprojects directory, so I updated existing submodules to be symlinks to submodules in the subprojects directory. See mesonbuild/meson#8827 for more info. Meson also natively suppors CMake subprojects (such as wingetopt). Meson also supports configurable options, such as whether TCG should be used or if the system's libc is musl. Existing build systems can still be used. BUILDING.md now describes the new meson build system, and the old build docs are at BUILDING_OLD.md. [Seagate#2] Signed-off-by: Reagan Bohan <xbjfk.github@gmail.com>
For more info, see TODO AMMEND [Seagate/openSeaChest#2]
For more info, see TODO AMMEND [Seagate/openSeaChest#2] Signed-off-by: Reagan Bohan <xbjfk.github@gmail.com>
For more info, see TODO AMMEND [Seagate/openSeaChest#2] Signed-off-by: Reagan Bohan <xbjfk.github@gmail.com>
For more info, see openSeaChest@dfce0d6 [Seagate/openSeaChest#2] Signed-off-by: Reagan Bohan <xbjfk.github@gmail.com>
For more info, see Seagate/openSeaChest@dfce0d6 [Seagate/openSeaChest#2] Signed-off-by: Reagan Bohan <xbjfk.github@gmail.com>
The meson build system is a build system with many advantages over others, and one I consider to be the best. It is one of the fastest build systems, easy to understand, and extensible (for example a target can be defined to automatically build docs). It supports all platforms the other soltutions do (Linux, Windows, FreeBSD) and is easy to use when cross compiling via a cross file (such as with MingW). It can also programatically generate the version, instead of needing to edit a header file every time. On my Linux computer, meson (configure) took 0.65s and ninja (build) took 16.62s, while the make-based build system took 30.22s. See https://mesonbuild.com/Overview.html and https://mesonbuild.com/Comparisons.html for me info on the meson build system. Meson requires all subprojects to be in the subprojects directory. It unfortunately does not support symlinks in the subprojects directory, so I updated existing submodules to be symlinks to submodules in the subprojects directory. See mesonbuild/meson#8827 for more info. Meson also natively suppors CMake subprojects (such as wingetopt). Meson also supports configurable options, such as whether TCG should be used or if the system's libc is musl. Existing build systems can still be used. [Seagate/openSeaChest#2] Signed-off-by: Reagan Bohan <xbjfk.github@gmail.com>
The meson build system is a build system with many advantages over others, and one I consider to be the best. It is one of the fastest build systems, easy to understand, and extensible (for example a target can be defined to automatically build docs). It supports all platforms the other soltutions do (Linux, Windows, FreeBSD) and is easy to use when cross compiling via a cross file (such as with MingW). It can also programatically generate the version, instead of needing to edit a header file every time. On my Linux computer, meson (configure) took 0.65s and ninja (build) took 16.62s, while the make-based build system took 30.22s. See https://mesonbuild.com/Overview.html and https://mesonbuild.com/Comparisons.html for me info on the meson build system. Meson requires all subprojects to be in the subprojects directory. It unfortunately does not support symlinks in the subprojects directory, so I updated existing submodules to be symlinks to submodules in the subprojects directory. See mesonbuild/meson#8827 for more info. Meson also natively suppors CMake subprojects (such as wingetopt). Meson also supports configurable options, such as whether TCG should be used or if the system's libc is musl. Existing build systems can still be used. [Seagate/openSeaChest#2] Signed-off-by: Reagan Bohan <xbjfk.github@gmail.com>
The meson build system is a build system with many advantages over others, and one I consider to be the best. It is one of the fastest build systems, easy to understand, and extensible (for example a target can be defined to automatically build docs). It supports all platforms the other soltutions do (Linux, Windows, FreeBSD) and is easy to use when cross compiling via a cross file (such as with MingW). It can also programatically generate the version, instead of needing to edit a header file every time. On my Linux computer, meson (configure) took 0.65s and ninja (build) took 16.62s, while the make-based build system took 30.22s. See https://mesonbuild.com/Overview.html and https://mesonbuild.com/Comparisons.html for me info on the meson build system. Meson requires all subprojects to be in the subprojects directory. It unfortunately does not support symlinks in the subprojects directory, so I updated existing submodules to be symlinks to submodules in the subprojects directory. See mesonbuild/meson#8827 for more info. Meson also natively suppors CMake subprojects (such as wingetopt). Meson also supports configurable options, such as whether TCG should be used or if the system's libc is musl. Existing build systems can still be used. [Seagate/openSeaChest#2] Signed-off-by: Reagan Bohan <xbjfk.github@gmail.com>
The meson build system is a build system with many advantages over others, and one I consider to be the best. It is one of the fastest build systems, easy to understand, and extensible (for example a target can be defined to automatically build docs). It supports all platforms the other soltutions do (Linux, Windows, FreeBSD) and is easy to use when cross compiling via a cross file (such as with MingW). It can also programatically generate the version, instead of needing to edit a header file every time. On my Linux computer, meson (configure) took 0.65s and ninja (build) took 16.62s, while the make-based build system took 30.22s. See https://mesonbuild.com/Overview.html and https://mesonbuild.com/Comparisons.html for me info on the meson build system. Meson requires all subprojects to be in the subprojects directory. It unfortunately does not support symlinks in the subprojects directory, so I updated existing submodules to be symlinks to submodules in the subprojects directory. See mesonbuild/meson#8827 for more info. Meson also natively suppors CMake subprojects (such as wingetopt). Meson also supports configurable options, such as whether TCG should be used or if the system's libc is musl. Existing build systems can still be used. [Seagate#2] Signed-off-by: Reagan Bohan <xbjfk.github@gmail.com>
The meson build system is a build system with many advantages over others, and one I consider to be the best. It is one of the fastest build systems, easy to understand, and extensible (for example a target can be defined to automatically build docs). It supports all platforms the other soltutions do (Linux, Windows, FreeBSD) and is easy to use when cross compiling via a cross file (such as with MingW). It can also programatically generate the version, instead of needing to edit a header file every time. On my Linux computer, meson (configure) took 0.65s and ninja (build) took 16.62s, while the make-based build system took 30.22s. See https://mesonbuild.com/Overview.html and https://mesonbuild.com/Comparisons.html for me info on the meson build system. Meson requires all subprojects to be in the subprojects directory. It unfortunately does not support symlinks in the subprojects directory, so I updated existing submodules to be symlinks to submodules in the subprojects directory. See mesonbuild/meson#8827 for more info. Meson also natively suppors CMake subprojects (such as wingetopt). Meson also supports configurable options, such as whether TCG should be used or if the system's libc is musl. Existing build systems can still be used. [Seagate#2] Signed-off-by: Reagan Bohan <xbjfk.github@gmail.com>
The meson build system is a build system with many advantages over others, and one I consider to be the best. It is one of the fastest build systems, easy to understand, and extensible (for example a target can be defined to automatically build docs). It supports all platforms the other soltutions do (Linux, Windows, FreeBSD) and is easy to use when cross compiling via a cross file (such as with MingW). It can also programatically generate the version, instead of needing to edit a header file every time. On my Linux computer, meson (configure) took 0.65s and ninja (build) took 16.62s, while the make-based build system took 30.22s. See https://mesonbuild.com/Overview.html and https://mesonbuild.com/Comparisons.html for me info on the meson build system. Meson requires all subprojects to be in the subprojects directory. It unfortunately does not support symlinks in the subprojects directory, so I updated existing submodules to be symlinks to submodules in the subprojects directory. See mesonbuild/meson#8827 for more info. Meson also natively suppors CMake subprojects (such as wingetopt). Meson also supports configurable options, such as whether TCG should be used or if the system's libc is musl. Existing build systems can still be used. [Seagate#2] Signed-off-by: Reagan Bohan <xbjfk.github@gmail.com>
The meson build system is a build system with many advantages over others, and one I consider to be the best. It is one of the fastest build systems, easy to understand, and extensible (for example a target can be defined to automatically build docs). It supports all platforms the other soltutions do (Linux, Windows, FreeBSD) and is easy to use when cross compiling via a cross file (such as with MingW). It can also programatically generate the version, instead of needing to edit a header file every time. On my Linux computer, meson (configure) took 0.65s and ninja (build) took 16.62s, while the make-based build system took 30.22s. See https://mesonbuild.com/Overview.html and https://mesonbuild.com/Comparisons.html for me info on the meson build system. Meson requires all subprojects to be in the subprojects directory. It unfortunately does not support symlinks in the subprojects directory, so I updated existing submodules to be symlinks to submodules in the subprojects directory. See mesonbuild/meson#8827 for more info. Meson also natively suppors CMake subprojects (such as wingetopt). Meson also supports configurable options, such as whether TCG should be used or if the system's libc is musl. Existing build systems can still be used. [Seagate#2] Signed-off-by: Reagan Bohan <xbjfk.github@gmail.com>
The meson build system is a build system with many advantages over others, and one I consider to be the best. It is one of the fastest build systems, easy to understand, and extensible (for example a target can be defined to automatically build docs). It supports all platforms the other soltutions do (Linux, Windows, FreeBSD) and is easy to use when cross compiling via a cross file (such as with MingW). It can also programatically generate the version, instead of needing to edit a header file every time. On my Linux computer, meson (configure) took 0.65s and ninja (build) took 16.62s, while the make-based build system took 30.22s. See https://mesonbuild.com/Overview.html and https://mesonbuild.com/Comparisons.html for me info on the meson build system. Meson requires all subprojects to be in the subprojects directory. It unfortunately does not support symlinks in the subprojects directory, so I updated existing submodules to be symlinks to submodules in the subprojects directory. See mesonbuild/meson#8827 for more info. Meson also natively suppors CMake subprojects (such as wingetopt). Meson also supports configurable options, such as whether TCG should be used or if the system's libc is musl. Existing build systems can still be used. [Seagate#2] Signed-off-by: Reagan Bohan <xbjfk.github@gmail.com>
The meson build system is a build system with many advantages over others, and one I consider to be the best. It is one of the fastest build systems, easy to understand, and extensible (for example a target can be defined to automatically build docs). It supports all platforms the other soltutions do (Linux, Windows, FreeBSD) and is easy to use when cross compiling via a cross file (such as with MingW). It can also programatically generate the version, instead of needing to edit a header file every time. On my Linux computer, meson (configure) took 0.65s and ninja (build) took 16.62s, while the make-based build system took 30.22s. See https://mesonbuild.com/Overview.html and https://mesonbuild.com/Comparisons.html for me info on the meson build system. Meson requires all subprojects to be in the subprojects directory. It unfortunately does not support symlinks in the subprojects directory, so I updated existing submodules to be symlinks to submodules in the subprojects directory. See mesonbuild/meson#8827 for more info. Meson also natively suppors CMake subprojects (such as wingetopt). Meson also supports configurable options, such as whether TCG should be used or if the system's libc is musl. Existing build systems can still be used. [Seagate#2] Signed-off-by: Reagan Bohan <xbjfk.github@gmail.com>
The meson build system is a build system with many advantages over others, and one I consider to be the best. It is one of the fastest build systems, easy to understand, and extensible (for example a target can be defined to automatically build docs). It supports all platforms the other soltutions do (Linux, Windows, FreeBSD) and is easy to use when cross compiling via a cross file (such as with MingW). It can also programatically generate the version, instead of needing to edit a header file every time. On my Linux computer, meson (configure) took 0.65s and ninja (build) took 16.62s, while the make-based build system took 30.22s. See https://mesonbuild.com/Overview.html and https://mesonbuild.com/Comparisons.html for me info on the meson build system. Meson requires all subprojects to be in the subprojects directory. It unfortunately does not support symlinks in the subprojects directory, so I updated existing submodules to be symlinks to submodules in the subprojects directory. See mesonbuild/meson#8827 for more info. Meson also natively suppors CMake subprojects (such as wingetopt). Meson also supports configurable options, such as whether TCG should be used or if the system's libc is musl. Existing build systems can still be used. [Seagate/openSeaChest#2] Signed-off-by: Reagan Bohan <xbjfk.github@gmail.com>
The meson build system is a build system with many advantages over others, and one I consider to be the best. It is one of the fastest build systems, easy to understand, and extensible (for example a target can be defined to automatically build docs). It supports all platforms the other soltutions do (Linux, Windows, FreeBSD) and is easy to use when cross compiling via a cross file (such as with MingW). It can also programatically generate the version, instead of needing to edit a header file every time. On my Linux computer, meson (configure) took 0.65s and ninja (build) took 16.62s, while the make-based build system took 30.22s. See https://mesonbuild.com/Overview.html and https://mesonbuild.com/Comparisons.html for me info on the meson build system. Meson requires all subprojects to be in the subprojects directory. It unfortunately does not support symlinks in the subprojects directory, so I updated existing submodules to be symlinks to submodules in the subprojects directory. See mesonbuild/meson#8827 for more info. Meson also natively suppors CMake subprojects (such as wingetopt). Meson also supports configurable options, such as whether TCG should be used or if the system's libc is musl. Existing build systems can still be used. [Seagate#2] Signed-off-by: Reagan Bohan <xbjfk.github@gmail.com>
The meson build system is a build system with many advantages over others, and one I consider to be the best. It is one of the fastest build systems, easy to understand, and extensible (for example a target can be defined to automatically build docs). It supports all platforms the other soltutions do (Linux, Windows, FreeBSD) and is easy to use when cross compiling via a cross file (such as with MingW). It can also programatically generate the version, instead of needing to edit a header file every time. On my Linux computer, meson (configure) took 0.65s and ninja (build) took 16.62s, while the make-based build system took 30.22s. See https://mesonbuild.com/Overview.html and https://mesonbuild.com/Comparisons.html for me info on the meson build system. Meson requires all subprojects to be in the subprojects directory. It unfortunately does not support symlinks in the subprojects directory, so I updated existing submodules to be symlinks to submodules in the subprojects directory. See mesonbuild/meson#8827 for more info. Meson also natively suppors CMake subprojects (such as wingetopt). Meson also supports configurable options, such as whether TCG should be used or if the system's libc is musl. Existing build systems can still be used. [Seagate/openSeaChest#2] Signed-off-by: Reagan Bohan <xbjfk.github@gmail.com>
The meson build system is a build system with many advantages over others, and one I consider to be the best. It is one of the fastest build systems, easy to understand, and extensible (for example a target can be defined to automatically build docs). It supports all platforms the other soltutions do (Linux, Windows, FreeBSD) and is easy to use when cross compiling via a cross file (such as with MingW). It can also programatically generate the version, instead of needing to edit a header file every time. On my Linux computer, meson (configure) took 0.65s and ninja (build) took 16.62s, while the make-based build system took 30.22s. See https://mesonbuild.com/Overview.html and https://mesonbuild.com/Comparisons.html for me info on the meson build system. Meson requires all subprojects to be in the subprojects directory. It unfortunately does not support symlinks in the subprojects directory, so I updated existing submodules to be symlinks to submodules in the subprojects directory. See mesonbuild/meson#8827 for more info. Meson also natively suppors CMake subprojects (such as wingetopt). Meson also supports configurable options, such as whether TCG should be used or if the system's libc is musl. Existing build systems can still be used. [Seagate#2] Signed-off-by: Reagan Bohan <xbjfk.github@gmail.com>
The meson build system is a build system with many advantages over others, and one I consider to be the best. It is one of the fastest build systems, easy to understand, and extensible (for example a target can be defined to automatically build docs). It supports all platforms the other soltutions do (Linux, Windows, FreeBSD) and is easy to use when cross compiling via a cross file (such as with MingW). It can also programatically generate the version, instead of needing to edit a header file every time. On my Linux computer, meson (configure) took 0.65s and ninja (build) took 16.62s, while the make-based build system took 30.22s. See https://mesonbuild.com/Overview.html and https://mesonbuild.com/Comparisons.html for me info on the meson build system. Meson requires all subprojects to be in the subprojects directory. It unfortunately does not support symlinks in the subprojects directory, so I updated existing submodules to be symlinks to submodules in the subprojects directory. See mesonbuild/meson#8827 for more info. Meson also natively suppors CMake subprojects (such as wingetopt). Meson also supports configurable options, such as whether TCG should be used or if the system's libc is musl. Existing build systems can still be used. [Seagate/openSeaChest#2] Signed-off-by: Reagan Bohan <xbjfk.github@gmail.com>
The meson build system is a build system with many advantages over others, and one I consider to be the best. It is one of the fastest build systems, easy to understand, and extensible (for example a target can be defined to automatically build docs). It supports all platforms the other soltutions do (Linux, Windows, FreeBSD) and is easy to use when cross compiling via a cross file (such as with MingW). It can also programatically generate the version, instead of needing to edit a header file every time. On my Linux computer, meson (configure) took 0.65s and ninja (build) took 16.62s, while the make-based build system took 30.22s. See https://mesonbuild.com/Overview.html and https://mesonbuild.com/Comparisons.html for me info on the meson build system. Meson requires all subprojects to be in the subprojects directory. It unfortunately does not support symlinks in the subprojects directory, so I updated existing submodules to be symlinks to submodules in the subprojects directory. See mesonbuild/meson#8827 for more info. Meson also natively suppors CMake subprojects (such as wingetopt). Meson also supports configurable options, such as whether TCG should be used or if the system's libc is musl. Existing build systems can still be used. [Seagate#2] Signed-off-by: Reagan Bohan <xbjfk.github@gmail.com>
The meson build system is a build system with many advantages over others, and one I consider to be the best. It is one of the fastest build systems, easy to understand, and extensible (for example a target can be defined to automatically build docs). It supports all platforms the other soltutions do (Linux, Windows, FreeBSD) and is easy to use when cross compiling via a cross file (such as with MingW). It can also programatically generate the version, instead of needing to edit a header file every time. On my Linux computer, meson (configure) took 0.65s and ninja (build) took 16.62s, while the make-based build system took 30.22s. See https://mesonbuild.com/Overview.html and https://mesonbuild.com/Comparisons.html for me info on the meson build system. Meson requires all subprojects to be in the subprojects directory. It unfortunately does not support symlinks in the subprojects directory, so I updated existing submodules to be symlinks to submodules in the subprojects directory. See mesonbuild/meson#8827 for more info. Meson also natively suppors CMake subprojects (such as wingetopt). Meson also supports configurable options, such as whether TCG should be used or if the system's libc is musl. Existing build systems can still be used. [Seagate/openSeaChest#2] Signed-off-by: Reagan Bohan <xbjfk.github@gmail.com>
The meson build system is a build system with many advantages over others, and one I consider to be the best. It is one of the fastest build systems, easy to understand, and extensible (for example a target can be defined to automatically build docs). It supports all platforms the other soltutions do (Linux, Windows, FreeBSD) and is easy to use when cross compiling via a cross file (such as with MingW). It can also programatically generate the version, instead of needing to edit a header file every time. On my Linux computer, meson (configure) took 0.65s and ninja (build) took 16.62s, while the make-based build system took 30.22s. See https://mesonbuild.com/Overview.html and https://mesonbuild.com/Comparisons.html for me info on the meson build system. Meson requires all subprojects to be in the subprojects directory. It unfortunately does not support symlinks in the subprojects directory, so I updated existing submodules to be symlinks to submodules in the subprojects directory. See mesonbuild/meson#8827 for more info. Meson also natively suppors CMake subprojects (such as wingetopt). Meson also supports configurable options, such as whether TCG should be used or if the system's libc is musl. Existing build systems can still be used. [Seagate#2] Signed-off-by: Reagan Bohan <xbjfk.github@gmail.com>
The meson build system is a build system with many advantages over others, and one I consider to be the best. It is one of the fastest build systems, easy to understand, and extensible (for example a target can be defined to automatically build docs). It supports all platforms the other soltutions do (Linux, Windows, FreeBSD) and is easy to use when cross compiling via a cross file (such as with MingW). It can also programatically generate the version, instead of needing to edit a header file every time. On my Linux computer, meson (configure) took 0.65s and ninja (build) took 16.62s, while the make-based build system took 30.22s. See https://mesonbuild.com/Overview.html and https://mesonbuild.com/Comparisons.html for me info on the meson build system. Meson requires all subprojects to be in the subprojects directory. It unfortunately does not support symlinks in the subprojects directory, so I updated existing submodules to be symlinks to submodules in the subprojects directory. See mesonbuild/meson#8827 for more info. Meson also natively suppors CMake subprojects (such as wingetopt). Meson also supports configurable options, such as whether TCG should be used or if the system's libc is musl. Existing build systems can still be used. [Seagate#2] Signed-off-by: Reagan Bohan <xbjfk.github@gmail.com>
The meson build system is a build system with many advantages over others, and one I consider to be the best. It is one of the fastest build systems, easy to understand, and extensible (for example a target can be defined to automatically build docs). It supports all platforms the other soltutions do (Linux, Windows, FreeBSD) and is easy to use when cross compiling via a cross file (such as with MingW). It can also programatically generate the version, instead of needing to edit a header file every time. On my Linux computer, meson (configure) took 0.65s and ninja (build) took 16.62s, while the make-based build system took 30.22s. See https://mesonbuild.com/Overview.html and https://mesonbuild.com/Comparisons.html for me info on the meson build system. Meson requires all subprojects to be in the subprojects directory. It unfortunately does not support symlinks in the subprojects directory, so I updated existing submodules to be symlinks to submodules in the subprojects directory. See mesonbuild/meson#8827 for more info. Meson also natively suppors CMake subprojects (such as wingetopt). Meson also supports configurable options, such as whether TCG should be used or if the system's libc is musl. Existing build systems can still be used. [Seagate#2] Signed-off-by: Reagan Bohan <xbjfk.github@gmail.com>
The meson build system is a build system with many advantages over others, and one I consider to be the best. It is one of the fastest build systems, easy to understand, and extensible (for example a target can be defined to automatically build docs). It supports all platforms the other soltutions do (Linux, Windows, FreeBSD) and is easy to use when cross compiling via a cross file (such as with MingW). It can also programatically generate the version, instead of needing to edit a header file every time. On my Linux computer, meson (configure) took 0.65s and ninja (build) took 16.62s, while the make-based build system took 30.22s. See https://mesonbuild.com/Overview.html and https://mesonbuild.com/Comparisons.html for me info on the meson build system. Meson requires all subprojects to be in the subprojects directory. It unfortunately does not support symlinks in the subprojects directory, so I updated existing submodules to be symlinks to submodules in the subprojects directory. See mesonbuild/meson#8827 for more info. Meson also natively suppors CMake subprojects (such as wingetopt). Meson also supports configurable options, such as whether TCG should be used or if the system's libc is musl. Existing build systems can still be used. [Seagate#2] Signed-off-by: Reagan Bohan <xbjfk.github@gmail.com>
The meson build system is a build system with many advantages over others, and one I consider to be the best. It is one of the fastest build systems, easy to understand, and extensible (for example a target can be defined to automatically build docs). It supports all platforms the other soltutions do (Linux, Windows, FreeBSD) and is easy to use when cross compiling via a cross file (such as with MingW). It can also programatically generate the version, instead of needing to edit a header file every time. On my Linux computer, meson (configure) took 0.65s and ninja (build) took 16.62s, while the make-based build system took 30.22s. See https://mesonbuild.com/Overview.html and https://mesonbuild.com/Comparisons.html for me info on the meson build system. Meson requires all subprojects to be in the subprojects directory. It unfortunately does not support symlinks in the subprojects directory, so I updated existing submodules to be symlinks to submodules in the subprojects directory. See mesonbuild/meson#8827 for more info. Meson also natively suppors CMake subprojects (such as wingetopt). Meson also supports configurable options, such as whether TCG should be used or if the system's libc is musl. Existing build systems can still be used. [Seagate#2] Signed-off-by: Reagan Bohan <xbjfk.github@gmail.com>
The meson build system is a build system with many advantages over others, and one I consider to be the best. It is one of the fastest build systems, easy to understand, and extensible (for example a target can be defined to automatically build docs). It supports all platforms the other soltutions do (Linux, Windows, FreeBSD) and is easy to use when cross compiling via a cross file (such as with MingW). It can also programatically generate the version, instead of needing to edit a header file every time. On my Linux computer, meson (configure) took 0.65s and ninja (build) took 16.62s, while the make-based build system took 30.22s. See https://mesonbuild.com/Overview.html and https://mesonbuild.com/Comparisons.html for me info on the meson build system. Meson requires all subprojects to be in the subprojects directory. It unfortunately does not support symlinks in the subprojects directory, so I updated existing submodules to be symlinks to submodules in the subprojects directory. See mesonbuild/meson#8827 for more info. Meson also natively suppors CMake subprojects (such as wingetopt). Meson also supports configurable options, such as whether TCG should be used or if the system's libc is musl. Existing build systems can still be used. [Seagate#2] Signed-off-by: Reagan Bohan <xbjfk.github@gmail.com>
The meson build system is a build system with many advantages over others, and one I consider to be the best. It is one of the fastest build systems, easy to understand, and extensible (for example a target can be defined to automatically build docs). It supports all platforms the other soltutions do (Linux, Windows, FreeBSD) and is easy to use when cross compiling via a cross file (such as with MingW). It can also programatically generate the version, instead of needing to edit a header file every time. On my Linux computer, meson (configure) took 0.65s and ninja (build) took 16.62s, while the make-based build system took 30.22s. See https://mesonbuild.com/Overview.html and https://mesonbuild.com/Comparisons.html for me info on the meson build system. Meson requires all subprojects to be in the subprojects directory. It unfortunately does not support symlinks in the subprojects directory, so I updated existing submodules to be symlinks to submodules in the subprojects directory. See mesonbuild/meson#8827 for more info. Meson also natively suppors CMake subprojects (such as wingetopt). Meson also supports configurable options, such as whether TCG should be used or if the system's libc is musl. Existing build systems can still be used. [Seagate#2] Signed-off-by: Reagan Bohan <xbjfk.github@gmail.com>
The meson build system is a build system with many advantages over others, and one I consider to be the best. It is one of the fastest build systems, easy to understand, and extensible (for example a target can be defined to automatically build docs). It supports all platforms the other soltutions do (Linux, Windows, FreeBSD) and is easy to use when cross compiling via a cross file (such as with MingW). It can also programatically generate the version, instead of needing to edit a header file every time. On my Linux computer, meson (configure) took 0.65s and ninja (build) took 16.62s, while the make-based build system took 30.22s. See https://mesonbuild.com/Overview.html and https://mesonbuild.com/Comparisons.html for me info on the meson build system. Meson requires all subprojects to be in the subprojects directory. It unfortunately does not support symlinks in the subprojects directory, so I updated existing submodules to be symlinks to submodules in the subprojects directory. See mesonbuild/meson#8827 for more info. Meson also natively suppors CMake subprojects (such as wingetopt). Meson also supports configurable options, such as whether TCG should be used or if the system's libc is musl. Existing build systems can still be used. [Seagate#2] Signed-off-by: Reagan Bohan <xbjfk.github@gmail.com>
The meson build system is a build system with many advantages over others, and one I consider to be the best. It is one of the fastest build systems, easy to understand, and extensible (for example a target can be defined to automatically build docs). It supports all platforms the other soltutions do (Linux, Windows, FreeBSD) and is easy to use when cross compiling via a cross file (such as with MingW). It can also programatically generate the version, instead of needing to edit a header file every time. On my Linux computer, meson (configure) took 0.65s and ninja (build) took 16.62s, while the make-based build system took 30.22s. See https://mesonbuild.com/Overview.html and https://mesonbuild.com/Comparisons.html for me info on the meson build system. Meson requires all subprojects to be in the subprojects directory. It unfortunately does not support symlinks in the subprojects directory, so I updated existing submodules to be symlinks to submodules in the subprojects directory. See mesonbuild/meson#8827 for more info. Meson also natively suppors CMake subprojects (such as wingetopt). Meson also supports configurable options, such as whether TCG should be used or if the system's libc is musl. Existing build systems can still be used. [Seagate#2] Signed-off-by: Reagan Bohan <xbjfk.github@gmail.com>
The meson build system is a build system with many advantages over others, and one I consider to be the best. It is one of the fastest build systems, easy to understand, and extensible (for example a target can be defined to automatically build docs). It supports all platforms the other soltutions do (Linux, Windows, FreeBSD) and is easy to use when cross compiling via a cross file (such as with MingW). It can also programatically generate the version, instead of needing to edit a header file every time. On my Linux computer, meson (configure) took 0.65s and ninja (build) took 16.62s, while the make-based build system took 30.22s. See https://mesonbuild.com/Overview.html and https://mesonbuild.com/Comparisons.html for me info on the meson build system. Meson requires all subprojects to be in the subprojects directory. It unfortunately does not support symlinks in the subprojects directory, so I updated existing submodules to be symlinks to submodules in the subprojects directory. See mesonbuild/meson#8827 for more info. Meson also natively suppors CMake subprojects (such as wingetopt). Meson also supports configurable options, such as whether TCG should be used or if the system's libc is musl. Existing build systems can still be used. [Seagate#2] Signed-off-by: Reagan Bohan <xbjfk.github@gmail.com>
The meson build system is a build system with many advantages over others, and one I consider to be the best. It is one of the fastest build systems, easy to understand, and extensible (for example a target can be defined to automatically build docs). It supports all platforms the other soltutions do (Linux, Windows, FreeBSD) and is easy to use when cross compiling via a cross file (such as with MingW). It can also programatically generate the version, instead of needing to edit a header file every time. On my Linux computer, meson (configure) took 0.65s and ninja (build) took 16.62s, while the make-based build system took 30.22s. See https://mesonbuild.com/Overview.html and https://mesonbuild.com/Comparisons.html for me info on the meson build system. Meson requires all subprojects to be in the subprojects directory. It unfortunately does not support symlinks in the subprojects directory, so I updated existing submodules to be symlinks to submodules in the subprojects directory. See mesonbuild/meson#8827 for more info. Meson also natively suppors CMake subprojects (such as wingetopt). Meson also supports configurable options, such as whether TCG should be used or if the system's libc is musl. Existing build systems can still be used. [Seagate#2] Signed-off-by: Reagan Bohan <xbjfk.github@gmail.com>
The meson build system is a build system with many advantages over others, and one I consider to be the best. It is one of the fastest build systems, easy to understand, and extensible (for example a target can be defined to automatically build docs). It supports all platforms the other soltutions do (Linux, Windows, FreeBSD) and is easy to use when cross compiling via a cross file (such as with MingW). It can also programatically generate the version, instead of needing to edit a header file every time. On my Linux computer, meson (configure) took 0.65s and ninja (build) took 16.62s, while the make-based build system took 30.22s. See https://mesonbuild.com/Overview.html and https://mesonbuild.com/Comparisons.html for me info on the meson build system. Meson requires all subprojects to be in the subprojects directory. It unfortunately does not support symlinks in the subprojects directory, so I updated existing submodules to be symlinks to submodules in the subprojects directory. See mesonbuild/meson#8827 for more info. Meson also natively suppors CMake subprojects (such as wingetopt). Meson also supports configurable options, such as whether TCG should be used or if the system's libc is musl. Existing build systems can still be used. [Seagate#2] Signed-off-by: Reagan Bohan <xbjfk.github@gmail.com>
The meson build system is a build system with many advantages over others, and one I consider to be the best. It is one of the fastest build systems, easy to understand, and extensible (for example a target can be defined to automatically build docs). It supports all platforms the other soltutions do (Linux, Windows, FreeBSD) and is easy to use when cross compiling via a cross file (such as with MingW). It can also programatically generate the version, instead of needing to edit a header file every time. On my Linux computer, meson (configure) took 0.65s and ninja (build) took 16.62s, while the make-based build system took 30.22s. See https://mesonbuild.com/Overview.html and https://mesonbuild.com/Comparisons.html for me info on the meson build system. Meson requires all subprojects to be in the subprojects directory. It unfortunately does not support symlinks in the subprojects directory, so I updated existing submodules to be symlinks to submodules in the subprojects directory. See mesonbuild/meson#8827 for more info. Meson also natively suppors CMake subprojects (such as wingetopt). Meson also supports configurable options, such as whether TCG should be used or if the system's libc is musl. Existing build systems can still be used. [Seagate#2] Signed-off-by: Reagan Bohan <xbjfk.github@gmail.com>
The meson build system is a build system with many advantages over others, and one I consider to be the best. It is one of the fastest build systems, easy to understand, and extensible (for example a target can be defined to automatically build docs). It supports all platforms the other soltutions do (Linux, Windows, FreeBSD) and is easy to use when cross compiling via a cross file (such as with MingW). It can also programatically generate the version, instead of needing to edit a header file every time. On my Linux computer, meson (configure) took 0.65s and ninja (build) took 16.62s, while the make-based build system took 30.22s. See https://mesonbuild.com/Overview.html and https://mesonbuild.com/Comparisons.html for me info on the meson build system. Meson requires all subprojects to be in the subprojects directory. It unfortunately does not support symlinks in the subprojects directory, so I updated existing submodules to be symlinks to submodules in the subprojects directory. See mesonbuild/meson#8827 for more info. Meson also natively suppors CMake subprojects (such as wingetopt). Meson also supports configurable options, such as whether TCG should be used or if the system's libc is musl. Existing build systems can still be used. [Seagate#2] Signed-off-by: Reagan Bohan <xbjfk.github@gmail.com>
The meson build system is a build system with many advantages over others, and one I consider to be the best. It is one of the fastest build systems, easy to understand, and extensible (for example a target can be defined to automatically build docs). It supports all platforms the other soltutions do (Linux, Windows, FreeBSD) and is easy to use when cross compiling via a cross file (such as with MingW). It can also programatically generate the version, instead of needing to edit a header file every time. On my Linux computer, meson (configure) took 0.65s and ninja (build) took 16.62s, while the make-based build system took 30.22s. See https://mesonbuild.com/Overview.html and https://mesonbuild.com/Comparisons.html for me info on the meson build system. Meson requires all subprojects to be in the subprojects directory. It unfortunately does not support symlinks in the subprojects directory, so I updated existing submodules to be symlinks to submodules in the subprojects directory. See mesonbuild/meson#8827 for more info. Meson also natively suppors CMake subprojects (such as wingetopt). Meson also supports configurable options, such as whether TCG should be used or if the system's libc is musl. Existing build systems can still be used. [Seagate#2] Signed-off-by: Reagan Bohan <xbjfk.github@gmail.com>
The meson build system is a build system with many advantages over others, and one I consider to be the best. It is one of the fastest build systems, easy to understand, and extensible (for example a target can be defined to automatically build docs). It supports all platforms the other soltutions do (Linux, Windows, FreeBSD) and is easy to use when cross compiling via a cross file (such as with MingW). It can also programatically generate the version, instead of needing to edit a header file every time. On my Linux computer, meson (configure) took 0.65s and ninja (build) took 16.62s, while the make-based build system took 30.22s. See https://mesonbuild.com/Overview.html and https://mesonbuild.com/Comparisons.html for me info on the meson build system. Meson requires all subprojects to be in the subprojects directory. It unfortunately does not support symlinks in the subprojects directory, so I updated existing submodules to be symlinks to submodules in the subprojects directory. See mesonbuild/meson#8827 for more info. Meson also natively suppors CMake subprojects (such as wingetopt). Meson also supports configurable options, such as whether TCG should be used or if the system's libc is musl. Existing build systems can still be used. [Seagate/openSeaChest#2] Signed-off-by: Reagan Bohan <xbjfk.github@gmail.com>
The meson build system is a build system with many advantages over others, and one I consider to be the best. It is one of the fastest build systems, easy to understand, and extensible (for example a target can be defined to automatically build docs). It supports all platforms the other soltutions do (Linux, Windows, FreeBSD) and is easy to use when cross compiling via a cross file (such as with MingW). It can also programatically generate the version, instead of needing to edit a header file every time. On my Linux computer, meson (configure) took 0.65s and ninja (build) took 16.62s, while the make-based build system took 30.22s. See https://mesonbuild.com/Overview.html and https://mesonbuild.com/Comparisons.html for me info on the meson build system. Meson requires all subprojects to be in the subprojects directory. It unfortunately does not support symlinks in the subprojects directory, so I updated existing submodules to be symlinks to submodules in the subprojects directory. See mesonbuild/meson#8827 for more info. Meson also natively suppors CMake subprojects (such as wingetopt). Meson also supports configurable options, such as whether TCG should be used or if the system's libc is musl. Existing build systems can still be used. [Seagate#2] Signed-off-by: Reagan Bohan <xbjfk.github@gmail.com>
The meson build system is a build system with many advantages over others, and one I consider to be the best. It is one of the fastest build systems, has an easy to understand, and extensible syntax (for example a target can be defined to automatically build docs). It supports all platforms the other build systems do (Linux, Windows, FreeBSD) and is easy to use when cross compiling via a cross file (such as with MingW). It can also programmatically generate the version, instead of needing to edit a header file every time. On my Linux system, meson (configure) took 0.65s and ninja (build) took 16.62s, while the make-based build system took 30.22s. See https://mesonbuild.com/Overview.html and https://mesonbuild.com/Comparisons.html for me info on the meson build system. Meson requires all subprojects to be in the subprojects directory. It unfortunately does not support symlinks in the subprojects directory, so I updated existing submodules to be symlinks to submodules in the subprojects directory. See mesonbuild/meson#8827 for more info. Meson also natively supports CMake subprojects (such as wingetopt) and supports configurable options, such as whether TCG should be used or if the system's libc is musl. Note: existing build systems can still be used. [Seagate#2] Signed-off-by: Reagan Bohan <xbjfk.github@gmail.com>
he meson build system is a build system with many advantages over others, and one I consider to be the best. It is one of the fastest build systems, has an easy to understand, and extensible syntax (for example a target can be defined to automatically build docs). It supports all platforms the other build systems do (Linux, Windows, FreeBSD) and is easy to use when cross compiling via a cross file (such as with MinGW). It can also programmatically generate the version, instead of needing to edit a header file every time. Compiling openSeaChest on my Linux system, meson (configure) took 0.65s and ninja (build) took 16.62s, while the make-based build system took 30.22s. See https://mesonbuild.com/Overview.html and https://mesonbuild.com/Comparisons.html for me info on the meson build system. Meson requires all subprojects to be in the subprojects directory. It unfortunately does not support symlinks in the subprojects directory, so I updated existing submodules to be symlinks to submodules in the subprojects directory. See mesonbuild/meson#8827 for more info. Meson also natively supports CMake subprojects (such as wingetopt) and supports configurable options, such as whether TCG should be used or if the system's libc is musl. Note: existing build systems can still be used. [Seagate/openSeaChest#2] Signed-off-by: Reagan Bohan <xbjfk.github@gmail.com>
he meson build system is a build system with many advantages over others, and one I consider to be the best. It is one of the fastest build systems, has an easy to understand, and extensible syntax (for example a target can be defined to automatically build docs). It supports all platforms the other build systems do (Linux, Windows, FreeBSD) and is easy to use when cross compiling via a cross file (such as with MinGW). It can also programmatically generate the version, instead of needing to edit a header file every time. Compiling openSeaChest on my Linux system, meson (configure) took 0.65s and ninja (build) took 16.62s, while the make-based build system took 30.22s. See https://mesonbuild.com/Overview.html and https://mesonbuild.com/Comparisons.html for me info on the meson build system. Note: existing build systems can still be used. [Seagate/openSeaChest#2] Signed-off-by: Reagan Bohan <xbjfk.github@gmail.com>
he meson build system is a build system with many advantages over others, and one I consider to be the best. It is one of the fastest build systems, has an easy to understand, and extensible syntax (for example a target can be defined to automatically build docs). It supports all platforms the other build systems do (Linux, Windows, FreeBSD) and is easy to use when cross compiling via a cross file (such as with MinGW). It can also programmatically generate the version, instead of needing to edit a header file every time. Compiling openSeaChest on my Linux system, meson (configure) took 0.65s and ninja (build) took 16.62s, while the make-based build system took 30.22s. See https://mesonbuild.com/Overview.html and https://mesonbuild.com/Comparisons.html for me info on the meson build system. Note: existing build systems can still be used. [Seagate/openSeaChest#2] Signed-off-by: Reagan Bohan <xbjfk.github@gmail.com>
The meson build system is a build system with many advantages over others, and one I consider to be the best. It is one of the fastest build systems, has an easy to understand, and extensible syntax (for example a target can be defined to automatically build docs). It supports all platforms the other build systems do (Linux, Windows, FreeBSD) and is easy to use when cross compiling via a cross file (such as with MinGW). It can also programmatically generate the version, instead of needing to edit a header file every time. Compiling openSeaChest on my Linux system, meson (configure) took 0.65s and ninja (build) took 16.62s, while the make-based build system took 30.22s. See https://mesonbuild.com/Overview.html and https://mesonbuild.com/Comparisons.html for me info on the meson build system. Note: existing build systems can still be used. [Seagate/openSeaChest#2] Signed-off-by: Reagan Bohan <xbjfk.github@gmail.com>
The meson build system is a build system with many advantages over others, and one I consider to be the best. It is one of the fastest build systems, has an easy to understand, and extensible syntax (for example a target can be defined to automatically build docs). It supports all platforms the other build systems do (Linux, Windows, FreeBSD) and is easy to use when cross compiling via a cross file (such as with MinGW). It can also programmatically generate the version, instead of needing to edit a header file every time. Compiling openSeaChest on my Linux system, meson (configure) took 0.65s and ninja (build) took 16.62s, while the make-based build system took 30.22s. See https://mesonbuild.com/Overview.html and https://mesonbuild.com/Comparisons.html for me info on the meson build system. Note: existing build systems can still be used. [Seagate/openSeaChest#2] Signed-off-by: Reagan Bohan <xbjfk.github@gmail.com>
The meson build system is a build system with many advantages over others, and one I consider to be the best. It is one of the fastest build systems, has an easy to understand, and extensible syntax (for example a target can be defined to automatically build docs). It supports all platforms the other build systems do (Linux, Windows, FreeBSD) and is easy to use when cross compiling via a cross file (such as with MinGW). It can also programmatically generate the version, instead of needing to edit a header file every time. Compiling openSeaChest on my Linux system, meson (configure) took 0.65s and ninja (build) took 16.62s, while the make-based build system took 30.22s. See https://mesonbuild.com/Overview.html and https://mesonbuild.com/Comparisons.html for me info on the meson build system. Note: existing build systems can still be used. [Seagate/openSeaChest#2] Signed-off-by: Reagan Bohan <xbjfk.github@gmail.com>
The meson build system is a build system with many advantages over others, and one I consider to be the best. It is one of the fastest build systems, has an easy to understand, and extensible syntax (for example a target can be defined to automatically build docs). It supports all platforms the other build systems do (Linux, Windows, FreeBSD) and is easy to use when cross compiling via a cross file (such as with MinGW). It can also programmatically generate the version, instead of needing to edit a header file every time. Compiling openSeaChest on my Linux system, meson (configure) took 0.65s and ninja (build) took 16.62s, while the make-based build system took 30.22s. See https://mesonbuild.com/Overview.html and https://mesonbuild.com/Comparisons.html for more info on the meson build system. Note: existing build systems can still be used. [Seagate/openSeaChest#2] Signed-off-by: Reagan Bohan <xbjfk.github@gmail.com>
The meson build system is a build system with many advantages over others, and one I consider to be the best. It is one of the fastest build systems, has an easy to understand, and extensible syntax (for example a target can be defined to automatically build docs). It supports all platforms the other build systems do (Linux, Windows, FreeBSD) and is easy to use when cross compiling via a cross file (such as with MinGW). It can also programmatically generate the version, instead of needing to edit a header file every time. Compiling openSeaChest on my Linux system, meson (configure) took 0.65s and ninja (build) took 16.62s, while the make-based build system took 30.22s. See https://mesonbuild.com/Overview.html and https://mesonbuild.com/Comparisons.html for more info on the meson build system. Note: existing build systems can still be used. [Seagate/openSeaChest#2] Signed-off-by: Reagan Bohan <xbjfk.github@gmail.com>
The meson build system is a build system with many advantages over others, and one I consider to be the best. It is one of the fastest build systems, has an easy to understand, and extensible syntax (for example a target can be defined to automatically build docs). It supports all platforms the other build systems do (Linux, Windows, FreeBSD) and is easy to use when cross compiling via a cross file (such as with MinGW). It can also programmatically generate the version, instead of needing to edit a header file every time. Compiling openSeaChest on my Linux system, meson (configure) took 0.65s and ninja (build) took 16.62s, while the make-based build system took 30.22s. See https://mesonbuild.com/Overview.html and https://mesonbuild.com/Comparisons.html for more info on the meson build system. Note: existing build systems can still be used. [Seagate/openSeaChest#2] Signed-off-by: Reagan Bohan <xbjfk.github@gmail.com>
* Add ndm build base image Dockerfile and github workflows * Push ndm build base image to ghcr only * Build and push new ndm build base image for every new commit pushed to the develop branch or the release tags matching the expression - "Release-**" * Lock openSeaChest version used in ndm base image * Pull specific version of openSeaChest in the Dockerfile. Run workflows only if there are changes in `build/ndm-build-base/**`. Signed-off-by: Aditya Jain <aditya.jainadityajain.jain@gmail.com> Co-authored-by: Akhil Mohan <akhilerm@gmail.com>
I am closing this as we have accepted all the work from multiple pull requests for the meson build system which works very well and seems to be a good build system that satisfies the intent of this request. It works on Windows, Linux, FreeBSD, and Illumos. |
Especially for a "cross platform utility" support for cross compiling is an important issue. Pure makefiles aren't a good way to handle this.
Therefor this project should get support for GNU Autotools or CMake!
The text was updated successfully, but these errors were encountered: