MacOSX & win32 alpha3 testing

mingw android mingw.android at gmail.com
Fri Oct 28 21:17:52 UTC 2011


On Oct 28, 2011 9:21 PM, "Maciej Kujalowicz" <maciej.kujalowicz at trismer.com>
wrote:
>
> Hi,
>
> Here is a short summary of our tests. Sorry that is not very detailed, but
I wanted to send feedback as soon as possible.

Great, any feedback is appreciated.
>
> Critical issues:
>
> - OSX: Maintenance tool crashes always (described in previous post)

Thanks. This is fixed for release. We didnt update the test repo though;
maintaining this test version isn't something you'd do.

> - OSX & WIN32 - It's impossible to deploy the application for the first
time. Qt creator prints on the output:
>
> ...
>  Can't find ''.
> Please make sure your appication   built successfully and is selected in
Appplication tab ('Run option')
> ...
>
> Necessitas in fact does not require any settings to be defined before
deploying. I just go to Run settings, close it and deploy again (without
changing anything in settings)

Ive seen this on all 3 platforms in the past. Newly created projects dont
set some value initially.

>
> Necessitas Qt Creator should be able to deploy the app with default
settings
>
> - WIN32
>
> Qt Creator launches qmake with target win32. Why ? I'd like to add some
platform specific parts to the .pro file for Android. With the previous
version of Necessitas I used:
>
> unix {
> }
>
> right now under windows, section win32 is used instead. Perhaps there
should be android-specific platform definition in project file

The 'platform' is android-g++, but I will investigate what else is set. I
pass -win32 to qmake when on windows and this is deprecated, so I should
change this. Personally I think qt hasn't historically provided a clean
unambiguous separation of build machine and target machine.

>
> - WIN32
>
> Qt creator is quite sensive of multiple instances of MAKE under win32. It
can be difficult to use Qt Creator next to other SDKs. The best advice is to
remove everything from the path (maybe except windows/system32) and then try
to test necessitas. Everything works fine then.

Yeah you're not the first to report this. I think the best thing will be to
have a nec-make.exe instead. On windows, there are many flavours of make
(cmd.exe, mingw, msys, cygwin) and they all have different issues.
>
> All for now. I tried to compile and run quite big application (QML,
mobility, maps). It didn't start for the first time, but after one hour with
the latest SDK, success!

Can you explain what you mean by this? Are you reporting a problem here? How
did it compare in this test with mac?
>
> Thanks, Maciej Kujalowicz
> Trismer Technologies
> _______________________________________________
> Necessitas-devel mailing list
> Necessitas-devel at kde.org
> https://mail.kde.org/mailman/listinfo/necessitas-devel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/necessitas-devel/attachments/20111028/8f68293d/attachment-0001.html>


More information about the Necessitas-devel mailing list