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

configure: improve interpreter detection #5122

Closed

Conversation

rohieb
Copy link
Contributor

@rohieb rohieb commented Sep 25, 2017

Currently, when configure is called with --with-java or --with-java=, auto-detection is performed. When called with --without-java, HAVE_JAVA is still being defined. This is unfortunate when cross-compiling for embedded systems, we would end up with Java on the host being auto-detected (which is not what we have on the target), or with a wrong HAVE_JAVA define.

This implements a way to explicitely disable scripting support for all supported languages with ``without-java` (or the respective options for Perl, PHP and Python)

While we're at it, make the detection a bit more verbose, and do some cleanup.

After the respective AC_DEFINE_UNQUOTED(CUPS_PHP) call, assigning
anything to CUPS_PHP is a no-op. Remove it so the surrounding test looks
like the other tests in the file.

Signed-off-by: Roland Hieber <[email protected]>
Currently, when configure is called with --with-java or --with-java=,
auto-detection is performed. When called with --without-java, HAVE_JAVA
is still being defined. This is unfortunate when cross-compiling for
embedded systems, we would end up with Java on the host being
auto-detected (which is not what we have on the target), or with a wrong
HAVE_JAVA define. We need a way to explicitely disable scripting support
for all supported languages.

Signed-off-by: Roland Hieber <[email protected]>
@michaelrsweet
Copy link
Collaborator

Ultimately I think I want to eliminate all of the third-party scripting support - only Java "needs" special handing as the others support the #! interpreter mechanism...

@rohieb
Copy link
Contributor Author

rohieb commented Sep 27, 2017

Ah ok, yes, that seems reasonable. Feel free to only pick the Java part from this PR.

@michaelrsweet
Copy link
Collaborator

I pushed a slightly different change:

[master b889560] Fixed the script interpreter detection in the configure script (Issue #5122)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants