Hi,
finally is ok!
N.
> if (output.isNull() && !*qmakeIsExecutable) { -- whoops! sorry.. ya i looked
> at the wrong if statement. You are correct
>
> ________________________________________
> From: Jana Aurindam [[email protected]]
> Sent: Tuesday, December 11, 2012 8:41 PM
> To: [email protected]
> Subject: RE: [mer-general] failed to add Qt version
>
> Sorry for top posting. I am using Outlook webmail.
>
> MerKitManager is pointing to the right qmake. There should be a qmake at
> that location
> /home/nicola/.config/QtProject/mer-dev-tools/nemo_n9_min/qmake . This qmake
> is a wrapper around the actual qmake call which happens inside the VM.
>
>
>
> ~Auri
> ________________________________________
> From: [email protected] [[email protected]]
> Sent: Tuesday, December 11, 2012 9:09 AM
> To: [email protected]
> Subject: RE: [mer-general] failed to add Qt version
>
> Hi,
> yes i have last qtcreator (i done pull yesterday).
> I done this analisis:
>
> 1) connection to mersdk is ok
>
> 2) in function void MerKitManager::addQtVersion() if i print
> qmake.toString() i have:
>
> /home/nicola/.config/QtProject/mer-dev-tools/nemo_n9_min/qmake
>
>
> if i force Utils::FileName qmake to
> "/srv/mer/targets/nemo_n9_min/usr/bin/" i have
>
> Cannot start '/srv/mer/targets/nemo_n9_min/usr/bin/qmake': Formato
> eseguibile non valido (wrong exec format)
> because qtcretor (host) execute qmake (arm).
>
>
> 3) then i think that in queryQMakeVariables (line 9 below) there is a bug,
> i think it should be
>
> if (output.isNull() && !*qmakeIsExecutable) {
>
> and not :
>
>
> 1 bool BaseQtVersion::queryQMakeVariables(const Utils::FileName &binary,
> QHash<QString, QString> *versionInfo,
> bool *qmakeIsExecutable)
> 2 {
> 3 const QFileInfo qmake = binary.toFileInfo();
> 4 *qmakeIsExecutable = qmake.exists() && qmake.isExecutable() &&
> !qmake.isDir();
> 5 if (!*qmakeIsExecutable)
> 6 return false;
>
> 7 QByteArray output;
> 8 output = runQmakeQuery(binary,
> Utils::Environment::systemEnvironment(), qmakeIsExecutable);
>
> 9 if (output.isNull() && !qmakeIsExecutable) {
>
>
> Thanks for help
>
> > Do you have the latest QtCreator ?
> >
> > Can you try out if you can connect to mer VM from commandline using
> >
> > $ ssh -p 2222 mersdk@localhost
> >
> > ~Auri
> > ________________________________________
> > From: [email protected] [[email protected]]
> > Sent: Monday, December 10, 2012 1:00 PM
> > To: [email protected]
> > Subject: Re: [mer-general] failed to add Qt version
> >
> > Hi,
> > i connecting to mersdk without password... I' don't know what's happen.
> > I'm seeing qt-creator code to resolve...
> > Lbt told me that might to be qt-creator problem.
> >
> > BR
> >
> > Nicola. (niqt)
> >>
> >> Hello Nicola,
> >>
> >> Ensure you can do passwordless `ssh -p2222 mersdk@localhost`,
> >> instructions
> >> are at:
> >> https://wiki.merproject.org/wiki/Platform_SDK_on_VirtualBox#Running_the_S
> >> DK_VM
> >>
> >>
> >> Cheers,
> >> Simonas (sledges)
> >>
> >>
> >> On 8 December 2012 23:06, Nicola De Filippo
> >>
> >> <[email protected]>wrote:
> >>> **
> >>>
> >>> Hi,
> >>>
> >>> i'm installing mer-sdk with virtual-box (
> >>> https://wiki.merproject.org/wiki/Platform_SDK_on_VirtualBox) but
> >>>
> >>> as i add the targert (nemo_n9_min in /srv/mer/targets) in qtcreator-mer
> >>> i
> >>> have this error "failed to add Qt version".
> >>>
> >>>
> >>>
> >>> have you any suggestions?
> >>>
> >>> Thanks
> >>>
> >>> Nicola
