-
Notifications
You must be signed in to change notification settings - Fork 80
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
config: enable auto detection by default #80
Conversation
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.
The problem with making auto automatic, that people may misconfigure the engine unintentionally.
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.
Maybe the steps could be the following:
#if !(ANY_ARCH_OR_AUTO_DEFINED_AND_SET)
#if AUTO_DEFINED_AND_DISABLED
#error "An arch must be selected"
#else
define auto
#endif
#endif
The last variant is still incorrect. You can define these with the value of 0, and that is the same thing as being not defined. I have proposed a variant above, that should not have this weakness. |
1f6bfa6
to
1abc0ec
Compare
7234680
to
d19da41
Compare
instead of requiring -DSLJIT_CONFIG_AUTO to enable, do autodetection unless a specific definition was used or auto detection was explicitly disabled by using -DSLJIT_CONFIG_AUTO=0
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.
LGTM
config: enable auto detection by default (zherczeg#80)
instead of needing -DSLJIT_CONFIG_AUTO or some other definition, do auto detection unless a specific definition was passed or it was explicitly disabled by -DSLJIT_CONFIG_AUTO=0
in platforms (ex: armel or armhf) where there might be multiple possible targets to chose (ex: thumb2, v5 or v7) allows reconfiguring the build without having to edit the makefile, for example:
additionally, this allows to generate code for a different (but compatible) ABI (ex: ARM EABI 5 application generating Thumb2 code in an arm64 CPU/OS)