[closed] Problem building Qt for Android on Mac (again)
-
Sorry to keep coming up with these...
So I'm trying to build QT 5.2.1 (for android) on Mac OS 10.8.5.
I started with an empty directory this time, and cloned a new copy of qt5 from the repository.
My configure command-line looks like:
@./configure -sdk macosx10.8 -prefix /projects/qt5.2.1-android -debug -opensource -confirm-license -xplatform android-g++ -nomake tests -nomake examples -android-ndk /Volumes/Projects/android-ndk-r9c -android-sdk /Volumes/Projects/android-sdk-macosx -android-ndk-host darwin-x86_64 -android-toolchain-version 4.8 -skip qttranslations -skip qtwebkit -skip qtserialport -skip qtwebkit-examples -no-warnings-are-errors@
The configure runs fine, but when I <code>make</code>, I get an error when building the <code>qtbase/src/gui</code> directory:
@make[3]: *** No rule to make target.obj/moc_qaccessible.o', needed by
../../lib/libQt5Gui.so.5.2.2'. Stop.@
After the compile command:
@/Volumes/Projects/qt5.2.1-android/qt5/qtbase/bin/moc -DQT_NO_MTDEV -DQT_NO_LIBUDEV -DQT_NO_XCB -DQT_NO_XKBCOMMON -DQT_NO_USING_NAMESPACE -DQT_BUILD_GUI_LIB -DQT_BUILDING_QT -DQT_NO_CAST_TO_ASCII -DQT_ASCII_CAST_WARNINGS -DQT_MOC_COMPAT -DQT_USE_QSTRINGBUILDER -DQT_DEPRECATED_WARNINGS -DQT_DISABLE_DEPRECATED_BEFORE=0x050000 -DQT_USE_BUNDLED_LIBPNG -DQT_NO_EXCEPTIONS -DQT_CORE_LIB -I../../mkspecs/android-g++ -I. -I../../include -I../../include/QtGui -I../../include/QtGui/5.2.2 -I../../include/QtGui/5.2.2/QtGui -Iimage -I../3rdparty/libpng -I../../include/QtCore/5.2.2 -I../../include/QtCore/5.2.2/QtCore -I../../include/QtCore -I.moc -I/Volumes/Projects/android-ndk-r9c/sources/cxx-stl/gnu-libstdc++/4.8/include -I/Volumes/Projects/android-ndk-r9c/sources/cxx-stl/gnu-libstdc++/4.8/libs/armeabi-v7a/include -I/Volumes/Projects/android-ndk-r9c/platforms/android-9/arch-arm/usr/include -I/Volumes/Projects/android-ndk-r9c/toolchains/arm-linux-androideabi-4.8/prebuilt/darwin-x86_64/lib/gcc/arm-linux-androideabi/4.8/include -I/Volumes/Projects/android-ndk-r9c/toolchains/arm-linux-androideabi-4.8/prebuilt/darwin-x86_64/lib/gcc/arm-linux-androideabi/4.8/include-fixed -I/Volumes/Projects/android-ndk-r9c/platforms/android-9/arch-arm/usr/include itemmodels/qstandarditemmodel.h -o .moc/moc_qstandarditemmodel.cpp@which seems to complete correctly.
I did a quick search of the <code>Makefile</code> (a mere 130083 lines) and found <code>.obj/moc_qaccessible.o</code> occurs once in the <code>Makefile</code> assigned to the <code>OBJECTS</code> variable.
I see a reference to <code>$(OBJECTS)</code> here: <code>../../lib/$(TARGET): $(OBJECTS) $(SUBLIBS) $(OBJCOMP) </code>
That's probably where the error is coming from. I don't see <code>$(OBJECTS)</code> on the left hand side of any dependencies. There are lots of <code>.o</code> files in the <code>.obj</code> directory but haven't figured out how they're getting built. I'm no expert on <code>Makefiles</code>.
One odd thing (it's 1:30am, so everything is a little odd right now) is that, in the <code>.moc</code> directory, there's no <code>moc_qaccessible.cpp</code>, though there are some other files there:
@[155] qtbase/src/gui% ls -l .moc
total 240
-rw-r--r-- 1 eric eric 7403 Jan 30 00:24 moc_qabstracttextdocumentlayout.cpp
-rw-r--r-- 1 eric eric 11052 Jan 30 00:22 moc_qguiapplication.cpp
-rw-r--r-- 1 eric eric 9918 Jan 30 00:22 moc_qinputmethod.cpp
-rw-r--r-- 1 eric eric 10437 Jan 30 00:23 moc_qmovie.cpp
-rw-r--r-- 1 eric eric 7221 Jan 30 00:25 moc_qopengldebug.cpp
-rw-r--r-- 1 eric eric 3540 Jan 30 00:25 moc_qopenglvertexarrayobject.cpp
-rw-r--r-- 1 eric eric 4834 Jan 30 00:23 moc_qplatformsystemtrayicon.cpp
-rw-r--r-- 1 eric eric 5781 Jan 30 00:25 moc_qstandarditemmodel.cpp
-rw-r--r-- 1 eric eric 4275 Jan 30 00:24 moc_qsyntaxhighlighter.cpp
-rw-r--r-- 1 eric eric 4281 Jan 30 00:24 moc_qtextdocumentlayout_p.cpp
-rw-r--r-- 1 eric eric 24251 Jan 30 00:22 moc_qwindow.cpp
-rw-r--r-- 1 eric eric 3516 Jan 30 00:25 qdesktopservices.moc
-rw-r--r-- 1 eric eric 2690 Jan 30 00:23 qpixmapcache.moc
[156] qtbase/src/gui%
@I hope that's enough information for someone to figure out what's going on.
Can anyone provide some insight(s)?
Thanks!
-
I'm giving up on this one, because after starting fresh with a clean clone, I'm having a very different problem, which I'll post in another new thread.