Re: [Development] QtCS: Javascript backend session
Did anyone attend the session? From: development-bounces+aurindam.jana=nokia@qt-project.org [development-bounces+aurindam.jana=nokia@qt-project.org] on behalf of ext Donald Carr [sirsp...@gmail.com] Sent: Friday, June 29, 2012 3:38 PM To: development@qt-project.org Subject: [Development] QtCS: Javascript backend session Did anyone manage to grab notes from this session? -- --- °v° Donald Carr /(_)\ Vaguely Professional Penguin lover ^ ^ Cave canem, te necet lingendo Chasing my own tail; hate to see me leave, love to watch me go Feeding the trolls is only marginally more rewarding than feeding the pigeons, and carries the same consequences ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] cmake files for qt5 problems with Qt5Quick/Qt5Qml modules on Mac OS X
On Friday, June 29, 2012 20:44:13 Nils Jeisecke wrote: Hi, I'm using cmake for building my stuff so the new cmake support directly in Qt5 is really appreciated. Thanks Stephen and KDAB! Thanks for trying it out :) There's a problem with the Qt5Quick and Qt5Qml modules though. The generated configuration files don't work and I had to make some adjustments to let things build. Just to be clear - it works with the modules in qtbase, but not with the ones that depend on qtbase? qtbase is on 4182a3afac5321b21496ae276446e3ba46d29fd4. My platform is - Mac OS X - in source tree build - no install This is the problem, I expect. Can you say more? Are you building qtbase on its own (and not installing it) and then qtdeclarative on its own (and not installing that either)? Or are you using qt5.git? What is your Qt configure line? Do you use -frameworks? Do you set CMAKE_PREFIX_PATH? To what? What are the relevant paths for your repos/install dirs/etc? What happens if you install? Does it work then? I'm attempting to get the CI system to run the CMake module unit tests, but they're awaiting review for the moment. Maybe we'll get some answers next week, but I'd be interested in your answers too. Thanks, -- Stephen Kelly stephen.ke...@kdab.com | Software Engineer KDAB (Deutschland) GmbH Co.KG, a KDAB Group Company www.kdab.com || Germany +49-30-521325470 || Sweden (HQ) +46-563-540090 KDAB - Qt Experts - Platform-Independent Software Solutions ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] QtCS: Javascript backend session
Two people did - myself and another guy whose name i unfortunately have forgotten. So, we sat and had a chat about Gluon's use of QtScript, and how we may be able to work with the V8 based QJS system, when we eventually we switch to Qt 5. But, really, not all that much stuff was being talked about there i'm afraid. On Saturday 30 June 2012 12:47:37 aurindam.j...@nokia.com wrote: Did anyone attend the session? From: development-bounces+aurindam.jana=nokia@qt-project.org [development-bounces+aurindam.jana=nokia@qt-project.org] on behalf of ext Donald Carr [sirsp...@gmail.com] Sent: Friday, June 29, 2012 3:38 PM To: development@qt-project.org Subject: [Development] QtCS: Javascript backend session Did anyone manage to grab notes from this session? -- --- °v° Donald Carr /(_)\ Vaguely Professional Penguin lover ^ ^ Cave canem, te necet lingendo Chasing my own tail; hate to see me leave, love to watch me go Feeding the trolls is only marginally more rewarding than feeding the pigeons, and carries the same consequences ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development -- ..Dan // Leinir.. http://leinir.dk/ Co- existence or no existence - Piet Hein ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
[Development] Policy for creating new mailing lists
Hi, What is the policy for creating mailing lists? I have just realized this mailing list after a little bit of talk over here at aKademy: http://lists.qt-project.org/mailman/listinfo/qt-components I had the impression previously, those requests should be going through the approval on this mailing list, like it happened back then with the raspberry mailing list. I would really appreciate either that way or an announcement. Not because of making those people's life more difficult, but getting informed to not lose important things ongoing. Essentially similarly like with other new introduces, like playground project and so forth. Best Regards, Laszlo Papp ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] buildsystem branches (about to be) integrated
I can cross build use wingw-w64 now, but still have a problem. the: lrelease.exe lupdate.exe and xmlpatterns.exe 's host platform should be Linux, not Windows. Just like jom and qmake, It's should be: lrelease lupdate and xmlpatterns Thanks! great work!! 2012/6/19 Oswald Buddenhagen oswald.buddenha...@nokia.com moin, the buildsystem branch of qtbase is currently being integrated. this is ~120 commits worth of qmake project file fixes and cleanups. there are some changes to how modularization (in particular configure tests) is handled, and cross-building should be supported without hacks finally. the immediate impact: - lots of build scripts which employ various hacks will instantly break. don't panic and (mostly) just delete some code from them. use configure -xplatform spec -sysroot root make as you would intuitively expect. don't play tricks with funny qmake and make invocations. - the other modules will spit out lots of warnings now. *DON'T* do anything about them for now. i have patches prepared for all modules already. i will explicitly add the module owners to the reviews. *don't* stage anything yourself. once my patches are through, there will be still some warnings left. you'll be invited to fix them at this point. - some build configurations will work even worse than before until everything is integrated. the only variants which are expected to be safe are developer builds without -prefix and module-by-module builds with -prefix. catch me on IRC if something breaks for you and no obvious solution seems to help. but remember that not every breakage is due to this branch being integrated. ;) ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development -- Please don't ask where I come from, It's a shame! Best Regards Yuchen ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
