Re: [Interest] QMake
On 08/05/17 21:38, Till Oliver Knoll wrote: Am 08.05.2017 um 04:12 schrieb Hamish Moffatt mailto:ham...@risingsoftware.com>>: On 08/05/17 17:07, Igor Mironchik wrote: Hi, Is it possible to set in qmake project file to put executable right in "." directory and don't use "debug" and "release" subdirs? Which platform? It does that on linux. Maybe you can use the DESTDIR variable to control where it's output. (I had trouble with that on Windows or Mac, I can't remember which.) The inconsistencies between platforms are annoying. There are no inconsistencies. Qmake puts all command line executables in ".", unless otherwise specified by DESTDIR, as correctly observed. No it doesn't, which is what Igor posted about in the first place. On Windows it puts them in Debug and Release subdirectories. André pointed out that the difference is that debug_and_release is on by default on Windows. You can enable it on Mac, which moves where the object files go, but the .app is still written to the main output directory instead. Except if you use "-spec macx-xcode" and build with xcodebuild, then the .app goes into Release/ instead. On Linux, where the output is written to the main directory even with debug_and_release. The debug and release binaries overwrite each other. That's no "inconsistency", but "expected platform-specific behaviour". Your platform-specific behaviour is my inconsistency :-) It's not even consistent between generators/makespecs on the same platform, or even between Qt versions in the past. Hamish ___ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
Re: [Interest] Generating Xcode project file for clang_64
You have to add "-spec macx-xcode" to your qmake arguments, otherwise it will use "macx-clang" and just generate a Makefile. Cheers, Christoph On 08.05.17 18:42, Nuno Santos wrote: Hi, I’m very used to generate the xcode project for Qt iOS projects. Today I was trying to generate the Xcode project for a clang_64 Qt project. How is that achieved? It is not generating the Xcode project. Any special trick? Regards, Nuno ___ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest ___ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
Re: [Interest] [Qt3D] Mirrored textures aspects
Ok, thanks for clarify this! ___ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
Re: [Interest] [Qt3D] Mirrored textures aspects
On 08/05/2017 18:39, Oleg Evseev wrote: Sean or Paul, Could you please explain aspects related to mirrored textures https://bugreports.qt.io/browse/QTBUG-54881 I didn't understand why when building against qt-5.8 I don't need to mirror textures image and SceneLoader load 3d models fine, but in qt-5.9 (like in qt-5.7 before) I need to mirror them, or they're shown flipped for loaded 3d objects. I though working with those issues was done before qt-5.8 rc and qt-5.9 shouldn't differ from 5.8 in this aspect. Thanks in advance! Hi, we took the call to stop flipping textures as default behaviour because often it is wasted CPU cycles, usually at application startup when you're trying to get things on screen as quickly as possible. In 5.9 though there is now the mirrored property on QTextureLoader that allows getting the old behaviour. Of course, if the data is baked, then it's better to mirror the textures on disk as a build time or design time step. Even better is to use a compressed texture format such as one of those supported by dds or similar to avoid the CPU load of decompressing jpg/png images. Iirc the issue form 5.7->5.8 was the obj loader flipping the texture coordinates which ended up screwing the normal mapped materials due to a change of sign in the calculation of the tangent vectors. Cheers, Sean --- With regards, Oleg ___ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest -- Dr Sean Harmer | sean.har...@kdab.com | Managing Director UK KDAB (UK) Ltd, a KDAB Group company Tel. +44 (0)1625 809908; Sweden (HQ) +46-563-540090 Mobile: +44 (0)7545 140604 KDAB - Qt Experts ___ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
[Interest] [Qt3D] Mirrored textures aspects
Sean or Paul, Could you please explain aspects related to mirrored textures https://bugreports.qt.io/browse/QTBUG-54881 I didn't understand why when building against qt-5.8 I don't need to mirror textures image and SceneLoader load 3d models fine, but in qt-5.9 (like in qt-5.7 before) I need to mirror them, or they're shown flipped for loaded 3d objects. I though working with those issues was done before qt-5.8 rc and qt-5.9 shouldn't differ from 5.8 in this aspect. Thanks in advance! --- With regards, Oleg ___ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
[Interest] Generating Xcode project file for clang_64
Hi, I’m very used to generate the xcode project for Qt iOS projects. Today I was trying to generate the Xcode project for a clang_64 Qt project. How is that achieved? It is not generating the Xcode project. Any special trick? Regards, Nuno ___ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
Re: [Interest] Args
> Am 08.05.2017 um 08:26 schrieb Till Oliver Knoll > : > > > > Am 08.05.2017 um 07:16 schrieb Philippe : > There is probably a reason why completely new languages like Swift come completely without exception handling >> >> Quote from Apple doc: >> >> "Swift provides first-class support for throwing, catching, propagating, >> and manipulating recoverable errors at runtime." >> >> https://developer.apple.com/library/content/documentation/Swift/Conceptual/Swift_Programming_Language/ErrorHandling.html >> > > Interesting. That must be a "recent addition to Swift (3.0?)", as that > clearly wasn't there from the very beginning (hence the outcry in the former > ObjC community). Since Swift 2.0 actually: https://www.hackingwithswift.com/new-syntax-swift-2-error-handling-try-catch Thanks, Oliver___ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
Re: [Interest] Args
> Am 08.05.2017 um 08:26 schrieb Till Oliver Knoll > > This sums up my previous point pretty nicely: > > "Java exceptions ceased to be exceptional at all, they became commonplace. > They are used from everything from the benign to the catastrophic, > differentiating between the severity of exceptions falls to the caller of the > function." And this: "For example in C++ you might throw an exception when you can’t convert from an enum to its string equivalent, or in Java when parsing a date from a string. In an internet connected world, where every input from a network must be considered hostile, is the failure to parse a string into a date really exceptional? Of course not." [https://dave.cheney.net/2012/01/18/why-go-gets-exceptions-right] Cheers, Oliver ___ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
Re: [Interest] QMake
> Am 08.05.2017 um 04:12 schrieb Hamish Moffatt : > >> On 08/05/17 17:07, Igor Mironchik wrote: >> Hi, >> >> Is it possible to set in qmake project file to put executable right in "." >> directory and don't use "debug" and "release" subdirs? > > Which platform? It does that on linux. > > Maybe you can use the DESTDIR variable to control where it's output. (I had > trouble with that on Windows or Mac, I can't remember which.) > > The inconsistencies between platforms are annoying. There are no inconsistencies. Qmake puts all command line executables in ".", unless otherwise specified by DESTDIR, as correctly observed. When compiling "within Qt Creator" those settings are usually overruled by the (local, per user) project settings, which are initialised the first time you open (or create) a *.pro project file. Furthermore, when compiling a "normal" application on macOS the executable is - by default - placed in an "app bundle" (which by itself is placed in DESTDIR). That's no "inconsistency", but "expected platform-specific behaviour". Refer to http://doc.qt.io/qt-5/osx-deployment.html for more details. Cheers, Oliver___ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
[Interest] QtIFW Problem Translating ControlScript
Hello. I ran into another Problem. This Time I have some serious Trouble translating the Strings in the ControlScript. All modified Strings have the "qsTr()" Macro, the "de.qm" is splitted up = 1 TS File in the Package Folder for the Dynamic Pages (which works, also the localized License File get displayed) and 1 TS File in the config Folder specifically for the ControlScript. Strings are marked as done and the de.qm has been compiled fine. In the config.xml I added the de.qm to activate the usage of the German Language File. I also tried calling the de.qm File from a Resource File - wont get loaded at all. Well, with the above configuration, the Installer starts in German, but the Strings in the ConfigScript (which are written in english) stay in english. Another Strange Symptom is: QtIFW's own de.qm File is complete, but some Pages are partly in english or completely in english (like the StarMenuDirectoryPage). Tested OS: Windows 10 Creators Update, Windows 7 SP1 Tested QtIFW Version: * 2.0.5-1 Binary from download.qt.io * 2.0 Branch from Git * 3.0 Branch from Git * Master Branch from Git Does anyone else have this Problem? Is this a known Bug? Thank You! Oliver signature.asc Description: OpenPGP digital signature ___ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
Re: [Interest] Args
Am 08.05.2017 um 07:16 schrieb Philippe : >>> There is probably a reason why completely new languages like Swift come >>> completely without exception handling > > Quote from Apple doc: > > "Swift provides first-class support for throwing, catching, propagating, > and manipulating recoverable errors at runtime." > > https://developer.apple.com/library/content/documentation/Swift/Conceptual/Swift_Programming_Language/ErrorHandling.html > Interesting. That must be a "recent addition to Swift (3.0?)", as that clearly wasn't there from the very beginning (hence the outcry in the former ObjC community). This sticks out for me: "Note: Error handling in Swift resembles exception handling in other languages, with the use of the try, catch and throw keywords. Unlike exception handling in many languages—including Objective-C—error handling in Swift does not involve unwinding the call stack, a process that can be computationally expensive. As such, the performance characteristics of a throwstatement are comparable to those of a returnstatement." But yes, for all practical matters that means that Swift has exception handling now :) But then there's another new language Go which also "got rid" of exceptions (because it can "afford to": it doesn't have a huge legacy API like Cocoa/ObjC to satisfy) from the very beginning: https://dave.cheney.net/2012/01/18/why-go-gets-exceptions-right That's a nice read btw which I just found. This sums up my previous point pretty nicely: "Java exceptions ceased to be exceptional at all, they became commonplace. They are used from everything from the benign to the catastrophic, differentiating between the severity of exceptions falls to the caller of the function." ;) Cheers, Oliver___ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
Re: [Interest] Args
>>There is probably a reason why completely new languages like Swift come >>completely without exception handling Quote from Apple doc: "Swift provides first-class support for throwing, catching, propagating, and manipulating recoverable errors at runtime." https://developer.apple.com/library/content/documentation/Swift/Conceptual/Swift_Programming_Language/ErrorHandling.html Philippe On Mon, 8 May 2017 07:11:22 -0300 Till Oliver Knoll wrote: > > > Am 08.05.2017 um 01:48 schrieb Igor Mironchik : > > > > Hi, > Using exceptions in arguments parser is something that just cannot be > justified. > > >>> Why not? > >> Even in the danger of starting a huge debate about "exceptions vs return > >> error code" here are my thoughts about it: > >> > >> Exceptions should just be used for... well, /exceptional/ cases. > >> > >> So what would be an "exceptional case" for a command line parser then? > >> Certainly not wrongly provided arguments. Humans tend to misspell words > >> all the time, so that's "the norm": business as usual for a command line > >> parser to validate the input and inform the user appropriately (with a > >> usage help, similar spelled commands etc.). Nothing which cries > >> "exception!" here IMHO. > >> > >> The only thing I could think of in a 10 second brainstorming which could > >> be considered "exceptional" is when e.g. "stdin" (or some socket even from > >> which to read commands, but even this would be a bordercase, as it could > >> be considered "normal" that a socket cannot be opened) cannot be opened > >> for reading (which is somewhat a constructed example, as arguments are > >> usually passed as input parameters to main() anyway - but you get the > >> idea). > >> > >> The internet is full of articles - and opinions - about when to use > >> exceptions, and when not (and we haven't even touched the topic of > >> "unchecked vs checked exceptions" - at least in the Java camp that's all > >> the rage ;)). > > > > I will not start that holly war about what you said :) I just say that > > I will think about more and more user friendly messages on wrong user input. > > Hold on: the one (exceptions vs return error codes) has /nothing/ to do with > the other (user-friendly error messages). Just to be on the same page here... > > > I wanted to simplify a life of a developer and a user of console > > application. But developer will be informed about "errors" through the > > exceptions. > > Yes, your intentions were clear. But did you just read what I wrote about > /when/ to use exceptions? > > In fact, you're not - necessarily - simplifying "the life of a developer" by > using exceptions. Au contraire, you force them to use patterns like RAII > (which is mostly a good thing by itself), think about whether their code is > "exception-safe" etc. > > There is probably a reason why completely new languages like Swift come > completely without exception handling - which raises interesting questions > (pun intended), as the main "GUI framework" (Cocoa/ObjC based) still uses - > and throws - exceptions then and when... but that's yet another story ;) > > Cheers, > Oliver > ___ > Interest mailing list > Interest@qt-project.org > http://lists.qt-project.org/mailman/listinfo/interest ___ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
Re: [Interest] Args
> Am 08.05.2017 um 01:48 schrieb Igor Mironchik : > > Hi, Using exceptions in arguments parser is something that just cannot be justified. >>> Why not? >> Even in the danger of starting a huge debate about "exceptions vs return >> error code" here are my thoughts about it: >> >> Exceptions should just be used for... well, /exceptional/ cases. >> >> So what would be an "exceptional case" for a command line parser then? >> Certainly not wrongly provided arguments. Humans tend to misspell words all >> the time, so that's "the norm": business as usual for a command line parser >> to validate the input and inform the user appropriately (with a usage help, >> similar spelled commands etc.). Nothing which cries "exception!" here IMHO. >> >> The only thing I could think of in a 10 second brainstorming which could be >> considered "exceptional" is when e.g. "stdin" (or some socket even from >> which to read commands, but even this would be a bordercase, as it could be >> considered "normal" that a socket cannot be opened) cannot be opened for >> reading (which is somewhat a constructed example, as arguments are usually >> passed as input parameters to main() anyway - but you get the idea). >> >> The internet is full of articles - and opinions - about when to use >> exceptions, and when not (and we haven't even touched the topic of >> "unchecked vs checked exceptions" - at least in the Java camp that's all the >> rage ;)). > > I will not start that holly war about what you said :) I just say that I > will think about more and more user friendly messages on wrong user input. Hold on: the one (exceptions vs return error codes) has /nothing/ to do with the other (user-friendly error messages). Just to be on the same page here... > I wanted to simplify a life of a developer and a user of console application. > But developer will be informed about "errors" through the exceptions. Yes, your intentions were clear. But did you just read what I wrote about /when/ to use exceptions? In fact, you're not - necessarily - simplifying "the life of a developer" by using exceptions. Au contraire, you force them to use patterns like RAII (which is mostly a good thing by itself), think about whether their code is "exception-safe" etc. There is probably a reason why completely new languages like Swift come completely without exception handling - which raises interesting questions (pun intended), as the main "GUI framework" (Cocoa/ObjC based) still uses - and throws - exceptions then and when... but that's yet another story ;) Cheers, Oliver ___ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
Re: [Interest] QMake
Hi Igor, the trick is CONFIG-=debug_and_release BUT BE WARNED: This option is set by default, because on Windows debug and release object CANNOT be mixed. If you disable it, your'e on your own. Please see https://bugreports.qt.io/browse/QTBUG-52347 for more information on this. Best regards, André Am 08.05.2017 um 10:01 schrieb Igor Mironchik: 2017-05-08 10:12, Hamish Moffatt пишет: On 08/05/17 17:07, Igor Mironchik wrote: Hi, Is it possible to set in qmake project file to put executable right in "." directory and don't use "debug" and "release" subdirs? Which platform? It does that on linux. I'm on Windows. Maybe you can use the DESTDIR variable to control where it's output. (I had trouble with that on Windows or Mac, I can't remember which.) I use DESTDIR = . But executable places in "debug" or "release" subfolder. The inconsistencies between platforms are annoying. Hamish ___ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest --- This email has been checked for viruses by AVG. http://www.avg.com ___ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest ___ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
Re: [Interest] QMake
2017-05-08 10:12, Hamish Moffatt пишет: On 08/05/17 17:07, Igor Mironchik wrote: Hi, Is it possible to set in qmake project file to put executable right in "." directory and don't use "debug" and "release" subdirs? Which platform? It does that on linux. I'm on Windows. Maybe you can use the DESTDIR variable to control where it's output. (I had trouble with that on Windows or Mac, I can't remember which.) I use DESTDIR = . But executable places in "debug" or "release" subfolder. The inconsistencies between platforms are annoying. Hamish ___ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest --- This email has been checked for viruses by AVG. http://www.avg.com ___ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
Re: [Interest] QMake
On 08/05/17 17:07, Igor Mironchik wrote: Hi, Is it possible to set in qmake project file to put executable right in "." directory and don't use "debug" and "release" subdirs? Which platform? It does that on linux. Maybe you can use the DESTDIR variable to control where it's output. (I had trouble with that on Windows or Mac, I can't remember which.) The inconsistencies between platforms are annoying. Hamish ___ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
[Interest] QMake
Hi, Is it possible to set in qmake project file to put executable right in "." directory and don't use "debug" and "release" subdirs? Thank you. --- This email has been checked for viruses by AVG. http://www.avg.com ___ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
