build: remove VxWorks platform support#34
Merged
Merged
Conversation
VxWorks (Wind River Tornado / Workbench) is an obsolete target for this project and the support carried a Tornado-specific build system, a dedicated OS porting layer, and conditional code paths throughout the engine. Remove it. Engine and OS layer: - Delete src/os_vxworks/ (the VxWorks OS porting layer). - Drop the HAVE_VXWORKS / HAVE_MUTEX_VXWORKS conditional code in db_iface.c, fop_util.c, os_handle.c, os_mkdir.c, os_pid.c, os_ctime.c, os_fsync.c, test_mutex.c, globals.h, env_globals.c, mutex.h, mutex_int.h, os.h, and db_int.in, keeping the POSIX path each guard fell through to. - Remove __db_getopt_reset from getopt.c; it existed only so VxWorks could re-run getopt across programs in a shared namespace and nothing else set it. Build system: - Delete the build_vxworks/ Tornado project tree and the dist VxWorks helpers (s_vxworks, validate/s_chk_vxworks, vx_setup/, vx_6/, vx_2.0/, vx_2.2/, vx_buildcd, vx_config.in). - Drop the vx/vxsmall/vx6 tags and build_vxworks entries from srcfiles.in, and the VxWorks steps from s_all, s_crypto, s_include, s_message_id, s_perm, s_symlink, s_validate, and the validate scripts. - Remove the HAVE_VXWORKS / HAVE_MUTEX_VXWORKS templates from config.m4 and mutex.m4 and from the static win/android config headers; regenerate configure and config.hin. Docs: - Delete the VxWorks installation pages and remove their chapter from the installation table of contents. Incidental historical mentions of VxWorks in reference prose (api_reference, a few source comments) and vendored third-party files (config.sub, libtool.m4, the SQLite amalgamation) are left untouched.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Remove VxWorks (Wind River Tornado / Workbench) platform support.
Why
VxWorks is an obsolete target for this project. Its support carried a
Tornado-specific build system, a dedicated OS porting layer, and conditional
code paths scattered through the engine, all of which add maintenance cost for
a platform that is no longer built or tested.
Changes
Engine and OS layer:
src/os_vxworks/.HAVE_VXWORKS/HAVE_MUTEX_VXWORKSconditional code indb_iface.c,fop_util.c,os_handle.c,os_mkdir.c,os_pid.c,os_ctime.c,os_fsync.c,test_mutex.c,globals.h,env_globals.c,mutex.h,mutex_int.h,os.h,db_int.in, keeping the POSIX path eachguard fell through to.
__db_getopt_resetfromgetopt.c; it existed only so VxWorks couldre-run getopt across programs in a shared namespace, and nothing else set it.
Build system:
build_vxworks/and the dist VxWorks helpers (s_vxworks,validate/s_chk_vxworks,vx_setup/,vx_6/,vx_2.0/,vx_2.2/,vx_buildcd,vx_config.in).vx/vxsmall/vx6tags andbuild_vxworksentries fromsrcfiles.in, and the VxWorks steps froms_all,s_crypto,s_include,s_message_id,s_perm,s_symlink,s_validate, and the validate scripts.HAVE_VXWORKS/HAVE_MUTEX_VXWORKStemplates fromconfig.m4,mutex.m4, and the static win/android config headers;configureandconfig.hinregenerated.Docs:
installation table of contents.
Scope
Incidental historical mentions of VxWorks in reference prose (
api_reference,a few source comments) and vendored third-party files (
config.sub,libtool.m4, the SQLite amalgamation) are left untouched.Verification
Builds clean with meson (macOS clang) after the removal; the portable paths the
guards fell through to are unchanged. CI covers the autoconf and meson matrices.