Skip to content
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

Add lutro.featureflags table, for use in determining lutro build capabilities #266

Merged
merged 1 commit into from
Jan 25, 2025

Conversation

jstine35
Copy link
Collaborator

@jstine35 jstine35 commented Jan 23, 2025

This is primarily intended for use in internal dev and unit test development. A practical application is that it can be used (soon) to detect whether the lutro build supports the transform rendering feature, and then alter lua graphics test behavior accordingly.

This change was inspired by work done in PR #215 which adds Transform and Scaling features.

I've selected the name lutro.featureflags instead of lutro.config used in PR #215 to improve clarity and avoid ambiguity with various other types of configurations (namely ones coming from data-driven or runtime sources such as ini files, for which the term 'config' is probably more readily associated).

test output

Running the unit tests produces this output:

$ ./runtest.sh test/unit/main.lua
lutro.featureflags.HAVE_COMPOSITION = false
lutro.featureflags.HAVE_JIT = false
lutro.featureflags.HAVE_INOTIFY = false
lutro.featureflags.HAVE_TRANSFORM = false
lutro.featureflags.HAVE_LUASOCKET = false
Lutro unit test run complete

…bilities

This is primarily intended for use in internal dev and unit test development. A practical application is that it can be used (soon) to detect whether the lutro build supports the transform rendering feature, and then alter lua graphics test behavior accordingly.
@jstine35 jstine35 requested a review from kivutar January 23, 2025 05:49
@jstine35 jstine35 merged commit 1051fcc into libretro:master Jan 25, 2025
10 checks passed
@jstine35 jstine35 deleted the feature-report branch January 25, 2025 01:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants