Demos
-
Hi jksh, I'm a bit confused. I have Qt 5.2.1 for windows installed (based on MSVC2010). Am I right in thinking that Qt can compile to Android or to Windows based on the kits you have installed and that the difference between Qt for Android and Qt for Windows is just there for convenience in having the main kits you're interested already setup? Since I am interested in Android and not Windows, maybe I should uninstall the one I have...
-
[quote]Am I right in thinking that Qt can compile to Android or to Windows based on the kits you have installed and that the difference between Qt for Android and Qt for Windows is just there for convenience in having the main kits you’re interested already setup?[/quote]No.
To create programs, you need to use a compiler.
- MSVC 2012 contains a compiler to create programs for Windows.
- MSVC 2010 contains a different compiler to create programs for Windows.
- The Android NDK contains a compiler to create programs for Android.
Qt is a library. The files you downloaded are a "partial program", which have already been pre-compiled:
- "Qt 5.2.1 for Android" contains Qt libraries compiled using the Android NDK compiler.
- "Qt 5.2.1 for Windows 32-bit (VS 2010, 518 MB)" contains Qt libraries compiled using the MSVC 2010 compiler.
To create a program, you need compile (or build) your code into an executable file. Then, you link your executable to the pre-compiled Qt libraries. You need to make sure that the compiler you used to build your code is compatible with the compiler used to build Qt.
A "kit" simply groups a compiler with a version of the precompiled Qt libraries. You need to download your own compiler, and then download a version of Qt that is compatible with that compiler.
-
Now I'm having a very tough time recording something with the audio recorder example above. I have the app running on my phone and after I record something I say into the microphone, I can't find the file anywhere - I don't think it gets saved. Any idea why?
Thanks,
Mike -
Please post your file saving code; we can't tell what's wrong otherwise.
-
I haven't modified the sample - I am thinking that this code from the sample sets the location of the file:
void AudioRecorder::setOutputLocation()
{
QString fileName = QFileDialog::getSaveFileName();
audioRecorder->setOutputLocation(QUrl::fromLocalFile(fileName));
outputLocationSet = true;
}and when you record, this file is written to?
-
Ah, I see.
I haven't tried that example on Android before, but I believe you need to click "Output..." to set your save location. Then, record your sound.
-
It works! I didn't know where the files were going. Not sure why I admitted that. Although in my defense, it could have been a bit more obvious... :)
And I'm pushing it now (again), but I can't seem to get an AVD going. I see I'm always on target API of 19 (which seems high, but that's something to look into). And ABI has 4 choices [armeabi-v7a, armeabi, x86, and mips]. I notice that I have the error message, "Qt version for architecture mips is missing". All Chinese. I'm just a guy that knows there are many different types of processors that have different instruction sets... But which one I should choose and why? Is it because Qt is compiled to each one and packaged in some mega zip that allows whichever device to get appropriate files? I know that almost as much as I know Chinese. (Or Korean - whatever looks more cryptic to you. Unless you know both already. In that case, how about Japanese)?
In all seriousness, I'm running on Windows 7 pro, I've got an S4... What is it I want to do to get a little app on the market? (actually, I'm not asking about that procedure) - I'm really asking, what are my main areas of focus in order to get that going to develop well on Windows (debug) and what ratio of debugging would you feel reasonably safe with debugging on AVDs and actual devices? And should I try all devices possible or are they generally all very equally supported when doing things like audio?
Tough questions! Maybe not for you. Any more help is very greatly appreciated. Please let me know if I should repost this as a new topic.
Thanks again,
Mike -
I agree that the example could be improved. I only knew the answer because I was wrestling with the same example myself a few months ago.
I haven't done any Android development myself though, so I can't help you with your latest questions. But since it's deviating from your original question now, I recommend starting a new thread with a new title -- people with Android experience will be more likely to spot it then.
Good luck!
