-
-
Notifications
You must be signed in to change notification settings - Fork 8.1k
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
UI,libobs,obs-outputs: Remove HAVE_OBSCONFIG_H ifdefs #11472
base: master
Are you sure you want to change the base?
Conversation
I'm sorry that there is no module name |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please change the commit prefix to UI,libobs,obs-outputs:
(as long as commit title overall is <72 characters)
43dc79e
to
9d21189
Compare
Done. |
9d21189
to
95b3d51
Compare
With the removal of all legacy code paths, obsconfig.h always exists and the compile definition always gets set. As such, it's no longer necessary to check for it. As removing the definition itself could be seen as a breaking change, this simply adds a comment to it to, marking it for removal in the next major version.
95b3d51
to
b810d3f
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Has this been tested when building just liboos
for plugin development?
@@ -280,6 +280,7 @@ target_include_directories( | |||
PUBLIC "$<BUILD_INTERFACE:${CMAKE_BINARY_DIR}/config>" "$<BUILD_INTERFACE:${CMAKE_CURRENT_SOURCE_DIR}>" | |||
) | |||
|
|||
# TODO: Remove for 32.0 | |||
target_compile_definitions(libobs PUBLIC HAVE_OBSCONFIG_H) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why only remove it with v32?
Description
Removes
HAVE_OBSCONFIG_H
ifdef-checks and marks the definition for removal in 32.0 (as removing it could be considered a breaking change, in case there are any third-party plugins checking for it).Motivation and Context
With the removal of all legacy code paths,
obsconfig.h
always exists and theHAVE_OBSCONFIG_H
compile definition always gets set. As such, it's no longer necessary to check for it.How Has This Been Tested?
Tested with CI that all builds still compile.
Tested with
git grep
that the definition line in cmake is now the only instance remaining ofHAVE_OBSCONFIG_H
.Types of changes
Checklist: