Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Browse files

mips: add configure options

  • Loading branch information...
commit a308ddf993872fad0b85aa1a8cf5a95a739178ee 1 parent 9e3a819
theuni authored
Showing with 11 additions and 0 deletions.
  1. +11 −0 configure.in
View
11 configure.in
@@ -502,6 +502,15 @@ case $host in
use_arch="arm"
AC_SUBST(ARCH_DEFINES, "-DTARGET_POSIX -DTARGET_LINUX -D_LINUX -D_ARMEL")
;;
+ mips-*-linux-gnu)
+ ARCH="mipsel-linux"
+ PYTHON_VERSION="2.6"

Do we really need to hard code the python version? Does the autoconf script fail?

@theuni Owner
theuni added a note

There is no good way of doing this. Python is almost impossible to build via cross. It's either this, or try to control it with an assortment of configure options and environment variables.

It's been a while on this one, I can certainly give it another go.

No No. I just asked. I didn't realize this was being cross-compiled. That explains why the autoconf macro can't be used. IMO it's not a big enough deal to spend more time on.

@theuni Owner
theuni added a note

Well it's far more than that. Python uses drumroll python as part of its build process. Furthermore, it uses python to determine how to run THAT build process. So without being able to run at build-time, even when building a host-python, it's a mess. See just above, ios does the same thing.

As I said, it was either this, or some crazy options. IMO it's better to leave it with something reasonable and let packagers patch configure if necessary.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
+ PYTHON_LDFLAGS="$LDFLAGS -lpython2.6"
+ PYTHON_NOVERSIONCHECK="no-check"
+ use_texturepacker_native=yes
+ AC_SUBST(ARCH_DEFINES, "-DTARGET_POSIX -DTARGET_LINUX -D_LINUX")
+ ;;
+
*)
AC_MSG_ERROR(unsupported host ($host))
esac
@@ -584,6 +593,8 @@ elif test "$use_arch" = "arm"; then
CXXFLAGS+=" -Wa,-march=armv7a -mcpu=cortex-a8 -mfpu=neon -mvectorize-with-neon-quad"
FFMPEG_EXTRACFLAGS+=" -mfpu=neon"
fi
+elif expr "X$host_cpu" : 'Xmips.*' > /dev/null; then
+ use_arch=mips
fi
# Checks for library functions.
@jimfcarroll

Do we really need to hard code the python version? Does the autoconf script fail?

@theuni

There is no good way of doing this. Python is almost impossible to build via cross. It's either this, or try to control it with an assortment of configure options and environment variables.

It's been a while on this one, I can certainly give it another go.

@jimfcarroll

No No. I just asked. I didn't realize this was being cross-compiled. That explains why the autoconf macro can't be used. IMO it's not a big enough deal to spend more time on.

@theuni

Well it's far more than that. Python uses drumroll python as part of its build process. Furthermore, it uses python to determine how to run THAT build process. So without being able to run at build-time, even when building a host-python, it's a mess. See just above, ios does the same thing.

As I said, it was either this, or some crazy options. IMO it's better to leave it with something reasonable and let packagers patch configure if necessary.

Please sign in to comment.
Something went wrong with that request. Please try again.