From thomas.epting at stryker.com Wed Jan 11 09:18:16 2017 From: thomas.epting at stryker.com (Epting, Thomas) Date: Wed, 11 Jan 2017 03:18:16 -0500 Subject: [Qbs] Suggested way to add non-default build variants Message-ID: <854A47713007BC4096CB1E36057406E137972FF92D@SYKMAIL9.strykercorp.com> Hi all, What is the suggest way to add non-default build variants in Qbs? Example: In addition to debug and release, we want to support a build variant releaseWithDebugInfo. The documentation (language-introduction.html) states "By default, "debug" and "release" are valid values but the user can add more in a project file.", but there is no information how this can actually be done. Thanks, Thomas -------------- next part -------------- An HTML attachment was scrubbed... URL: From dorian.jicquel at mana-sys.fr Wed Jan 11 12:01:46 2017 From: dorian.jicquel at mana-sys.fr (Jicquel Dorian) Date: Wed, 11 Jan 2017 12:01:46 +0100 Subject: [Qbs] Network paths for files Message-ID: <0ff387ec-0afa-79e0-e188-0dc40589ef48@mana-sys.fr> Hi, Network paths ( Ex : //network_path/file.txt ) doesn't work anymore , i think it's a regression because i tried the same thing with QtCreator 4.0.3 ( qbs 1.5.2 ) and it works well. When using it it says that file doesn't exists , tried it in a *Group *item and with the *File *service and same result. Regards, Dorian. -------------- next part -------------- An HTML attachment was scrubbed... URL: From christian.kandeler at qt.io Wed Jan 11 12:16:14 2017 From: christian.kandeler at qt.io (Christian Kandeler) Date: Wed, 11 Jan 2017 12:16:14 +0100 Subject: [Qbs] Network paths for files In-Reply-To: <0ff387ec-0afa-79e0-e188-0dc40589ef48@mana-sys.fr> References: <0ff387ec-0afa-79e0-e188-0dc40589ef48@mana-sys.fr> Message-ID: On 01/11/2017 12:01 PM, Jicquel Dorian wrote: > Network paths ( Ex : //network_path/file.txt ) doesn't work anymore , i > think it's a regression because i tried the same thing with QtCreator > 4.0.3 ( qbs 1.5.2 ) and it works well. Please file a bug report at bugreports.qt.io. As part of that, could you check whether the problem goes away if you revert https://codereview.qt-project.org/#/c/178893 ? Christian From thomas.epting at stryker.com Fri Jan 13 12:09:19 2017 From: thomas.epting at stryker.com (Epting, Thomas) Date: Fri, 13 Jan 2017 06:09:19 -0500 Subject: [Qbs] Suggested way to add non-default build variants In-Reply-To: <854A47713007BC4096CB1E36057406E137972FF92D@SYKMAIL9.strykercorp.com> References: <854A47713007BC4096CB1E36057406E137972FF92D@SYKMAIL9.strykercorp.com> Message-ID: <854A47713007BC4096CB1E36057406E137972FFA0C@SYKMAIL9.strykercorp.com> > What is the suggested way to add non-default build variants in Qbs? > > Example: In addition to debug and release, we want to support a > build variant releaseWithDebugInfo. > > The documentation (language-introduction.html) states "By default, > "debug" and "release" are valid values but the user can add more in > a project file.", but there is no information how this can actually be > done. Maybe there is any more documentation? Some examples? Thanks, Thomas From christian.kandeler at qt.io Fri Jan 13 13:18:06 2017 From: christian.kandeler at qt.io (Christian Kandeler) Date: Fri, 13 Jan 2017 13:18:06 +0100 Subject: [Qbs] Suggested way to add non-default build variants In-Reply-To: <854A47713007BC4096CB1E36057406E137972FF92D@SYKMAIL9.strykercorp.com> References: <854A47713007BC4096CB1E36057406E137972FF92D@SYKMAIL9.strykercorp.com> Message-ID: <83b57419-55ab-5b97-1843-cdedaa411f7b@qt.io> On 01/11/2017 09:18 AM, Epting, Thomas wrote: > What is the suggest way to add non-default build variants in Qbs? > > Example: In addition to debug and release, we want to support a build variant releaseWithDebugInfo. > > The documentation (language-introduction.html) states "By default, "debug" and "release" are valid values but the user can add more in a project file.", but there is no information how this can actually be done. I don't think this is actually true. In particular, if have no idea what "add more in a project file" means. The buildVariant property is used for two things: 1) A number of other properties derive their default values from it, e.g. cpp.optimization. These can of course be overwritten, so in effect you have a custom build variant then. 2) There are several places where we assume one of "debug" and "release", for instance when deciding which variant of the Qt libraries to link against. Therefore, I think you need to go with one of the two predefined values. Christian From thomas.epting at stryker.com Fri Jan 13 13:54:18 2017 From: thomas.epting at stryker.com (Epting, Thomas) Date: Fri, 13 Jan 2017 07:54:18 -0500 Subject: [Qbs] Suggested way to add non-default build variants In-Reply-To: <83b57419-55ab-5b97-1843-cdedaa411f7b@qt.io> References: <854A47713007BC4096CB1E36057406E137972FF92D@SYKMAIL9.strykercorp.com> <83b57419-55ab-5b97-1843-cdedaa411f7b@qt.io> Message-ID: <854A47713007BC4096CB1E36057406E137972FFA1F@SYKMAIL9.strykercorp.com> > > What is the suggest way to add non-default build variants in Qbs? > > Example: In addition to debug and release, we want to support a build variant releaseWithDebugInfo. > > I don't think this is actually true. In particular, if have no idea what "add more in a project file" means. > The buildVariant property is used for two things: > 1) A number of other properties derive their default values from it, e.g. cpp.optimization. These can > of course be overwritten, so in effect you have a custom build variant then. > 2) There are several places where we assume one of "debug" and "release", for instance when > deciding which variant of the Qt libraries to link against. Therefore, I think you need to go with one > of the two predefined values. Thanks. I also found QBS-88 which seems to address what we need. Thomas From dizygotheca at ntlworld.com Sun Jan 15 02:42:36 2017 From: dizygotheca at ntlworld.com (dizygotheca) Date: Sun, 15 Jan 2017 01:42:36 +0000 Subject: [Qbs] Linking static lib with PkgConfig and --as-needed Message-ID: I'm struggling to link a static lib that depends on an external library. Using Qbs 1.7.0 with Gcc 5.4.0 on Linux. It seems to me that PkgConfigProbe should strip "-l" out of the libs so that cpp.staticLibraries can be used. Disabling the as-needed shouldn't be necessary. Or am I missing something ? example.qbs: import qbs import qbs.Probes as Probes Project { minimumQbsVersion: "1.6" CppApplication { files: "main.cpp" Depends {name: "static"} cpp.linkerFlags: "-v" } StaticLibrary { name: "static" Depends {name: "cpp"} files: "lib.*" Probes.PkgConfigProbe {id: ext; name: "libudev" } Export { // Q: How to export external link library dependancy ? Depends {name: "cpp"} // 1. Fails: Cannot find -l-ludev // cpp.staticLibraries: ext.libs // 2. Fails: linkerFlags appear before input artifacts // so as-needed flag discards -ludev // cpp.linkerFlags: ext.libs // 3. Success, but only if we know lib name // cpp.staticLibraries: ext.found ? "udev" : original // 4. Success: work-around for wrong Qbs ordering cpp.linkerFlags: ["--no-as-needed"].concat(ext.libs) } } } main.cpp: #include "lib.h" int main(int argc, char *argv[]) { open(); } lib.h: void open(); lib.cpp: #include "lib.h" #include void open() { struct udev *udev = udev_new(); } From christian.kandeler at qt.io Mon Jan 16 11:54:55 2017 From: christian.kandeler at qt.io (Christian Kandeler) Date: Mon, 16 Jan 2017 11:54:55 +0100 Subject: [Qbs] Linking static lib with PkgConfig and --as-needed In-Reply-To: References: Message-ID: <4e925460-a315-3de7-7ab9-7df558cc7c1c@qt.io> On 01/15/2017 02:42 AM, dizygotheca wrote: > I'm struggling to link a static lib that depends on an external library. > > Using Qbs 1.7.0 with Gcc 5.4.0 on Linux. > > It seems to me that PkgConfigProbe should strip "-l" out of the libs so > that cpp.staticLibraries can be used. Disabling the as-needed shouldn't > be necessary. As you have noticed, PkgConfigProbe.libs simply stores the raw entries of the --libs output. I agree that it seems to make sense to provide higher-level output as well. Can you please file a bug report? Christian From hkarel at yandex.ru Mon Jan 16 16:51:04 2017 From: hkarel at yandex.ru (=?UTF-8?B?0JrQsNGA0LXQu9C40L0g0J/QsNCy0LXQuw==?=) Date: Mon, 16 Jan 2017 18:51:04 +0300 Subject: [Qbs] WARNING: Suspicious use of qbs.TextFile during property evaluation. Message-ID: <11e14f21-2901-87c8-61a5-f86869d9deae@yandex.ru> Hello, Today I went to QBS version 1.7.1 (previously 1.6.1) When I build the project I began to receive the following message: WARNING: Suspicious use of qbs.TextFile during property evaluation. Should this call be in a Probe instead? at getVersions(filePath = '/home/hkarel/CProjects/27FacesRetail/VERSION') in /home/hkarel/CProjects/27FacesRetail/qbs/imports/QbsUtl/qbsutl.js at () in /home/hkarel/CProjects/27FacesRetail/27fbase.qbs:9 at () in /home/hkarel/CProjects/27FacesRetail/27fbase.qbs:39 ... How can I remove/hide this warning? In this case, I am quite consciously call qbs.TextFile to calculate the value of the property. I could use a 'probe', but at the 'project' level it can not be done. -- BR, Pavel Karelin -------------- next part -------------- An HTML attachment was scrubbed... URL: From christian.kandeler at qt.io Mon Jan 16 17:04:33 2017 From: christian.kandeler at qt.io (Christian Kandeler) Date: Mon, 16 Jan 2017 17:04:33 +0100 Subject: [Qbs] WARNING: Suspicious use of qbs.TextFile during property evaluation. In-Reply-To: <11e14f21-2901-87c8-61a5-f86869d9deae@yandex.ru> References: <11e14f21-2901-87c8-61a5-f86869d9deae@yandex.ru> Message-ID: <2b879e54-0b76-a7d4-502d-e3b8f35f8259@qt.io> Hi Pavel, > Today I went to QBS version 1.7.1 (previously 1.6.1) > When I build the project I began to receive the following message: > > WARNING: Suspicious use of qbs.TextFile during property evaluation. > > How can I remove/hide this warning? there is no way to switch off this particular warning, so you'd need to suppress all non-error messages via the "-qq" (or by disabling "show warnings" in the Qt Creator issues pane). > In this case, I am quite > consciously call qbs.TextFile to calculate the value of the property. I > could use a 'probe', but at the 'project' level it can not be done. Project-level Probes will be possible in 1.8. Until then, you'll have to live with the warning, unless you can move the respective property to a module or product instead. Christian From hkarel at yandex.ru Mon Jan 16 17:21:49 2017 From: hkarel at yandex.ru (=?UTF-8?B?0JrQsNGA0LXQu9C40L0g0J/QsNCy0LXQuw==?=) Date: Mon, 16 Jan 2017 19:21:49 +0300 Subject: [Qbs] WARNING: Suspicious use of qbs.TextFile during property evaluation. In-Reply-To: <2b879e54-0b76-a7d4-502d-e3b8f35f8259@qt.io> References: <11e14f21-2901-87c8-61a5-f86869d9deae@yandex.ru> <2b879e54-0b76-a7d4-502d-e3b8f35f8259@qt.io> Message-ID: <77f29144-2a6c-f5e7-0797-716147068997@yandex.ru> 16.01.2017 19:04, Christian Kandeler пишет: > Hi Pavel, > >> Today I went to QBS version 1.7.1 (previously 1.6.1) >> When I build the project I began to receive the following message: >> >> WARNING: Suspicious use of qbs.TextFile during property evaluation. >> >> How can I remove/hide this warning? > there is no way to switch off this particular warning, so you'd need to > suppress all non-error messages via the "-qq" (or by disabling "show > warnings" in the Qt Creator issues pane). This is not a good idea. How I then see compilation warnings? > >> In this case, I am quite >> consciously call qbs.TextFile to calculate the value of the property. I >> could use a 'probe', but at the 'project' level it can not be done. > Project-level Probes will be possible in 1.8. Until then, you'll have to > live with the warning, unless you can move the respective property to a > module or product instead. Well I will wait. Perhaps, I come back to version 1.6.1 > Christian > _______________________________________________ > Qbs mailing list > Qbs at qt-project.org > http://lists.qt-project.org/mailman/listinfo/qbs Pavel. -------------- next part -------------- An HTML attachment was scrubbed... URL: From b.terrier at gmail.com Wed Jan 18 16:43:40 2017 From: b.terrier at gmail.com (Benjamin TERRIER) Date: Wed, 18 Jan 2017 16:43:40 +0100 Subject: [Qbs] How to specify remote directory in Qt Creator using qbs Message-ID: Hi, Is there a way to tell Qt Creator to deploy the exe in a particular folder of a remote Linux device when using qbs? When using qmake this can be done by setting "target.path = /foo/bar". Thanks. BR Benjamin Terrier From Jake.Petroules at qt.io Wed Jan 18 19:03:38 2017 From: Jake.Petroules at qt.io (Jake Petroules) Date: Wed, 18 Jan 2017 18:03:38 +0000 Subject: [Qbs] How to specify remote directory in Qt Creator using qbs In-Reply-To: References: Message-ID: Group { fileTagsFilter: product.type // equivalent to fileTagsFilter: ["application"] qbs.installDir: "/foo/bar" } > On Jan 18, 2017, at 7:43 AM, Benjamin TERRIER wrote: > > Hi, > > Is there a way to tell Qt Creator to deploy the exe in a particular folder > of a remote Linux device when using qbs? > > When using qmake this can be done by setting "target.path = /foo/bar". > > Thanks. > > BR > > Benjamin Terrier > _______________________________________________ > Qbs mailing list > Qbs at qt-project.org > http://lists.qt-project.org/mailman/listinfo/qbs -- Jake Petroules - jake.petroules at qt.io The Qt Company - Silicon Valley Qbs build tool evangelist - qbs.io From b.terrier at gmail.com Thu Jan 19 09:13:40 2017 From: b.terrier at gmail.com (Benjamin TERRIER) Date: Thu, 19 Jan 2017 09:13:40 +0100 Subject: [Qbs] How to specify remote directory in Qt Creator using qbs In-Reply-To: References: Message-ID: 2017-01-18 19:03 GMT+01:00 Jake Petroules : > Group { > fileTagsFilter: product.type // equivalent to fileTagsFilter: ["application"] > qbs.installDir: "/foo/bar" > } > This does not seems to work. Qt Creator still copies the binary to "/" on the remote device. From Jake.Petroules at qt.io Thu Jan 19 09:21:18 2017 From: Jake.Petroules at qt.io (Jake Petroules) Date: Thu, 19 Jan 2017 08:21:18 +0000 Subject: [Qbs] How to specify remote directory in Qt Creator using qbs In-Reply-To: References: Message-ID: <0A318B84-3380-4B79-BB47-5AB6095A7B90@qt.io> Sorry, I forgot to say you also need qbs.install: true in the Group. So: Group { fileTagsFilter: product.type // equivalent to fileTagsFilter: ["application"] qbs.install: true qbs.installDir: "/foo/bar" } > On Jan 19, 2017, at 12:13 AM, Benjamin TERRIER wrote: > > 2017-01-18 19:03 GMT+01:00 Jake Petroules : >> Group { >> fileTagsFilter: product.type // equivalent to fileTagsFilter: ["application"] >> qbs.installDir: "/foo/bar" >> } >> > > This does not seems to work. Qt Creator still copies the binary to "/" > on the remote device. -- Jake Petroules - jake.petroules at qt.io The Qt Company - Silicon Valley Qbs build tool evangelist - qbs.io From b.terrier at gmail.com Thu Jan 19 09:35:09 2017 From: b.terrier at gmail.com (Benjamin TERRIER) Date: Thu, 19 Jan 2017 09:35:09 +0100 Subject: [Qbs] How to specify remote directory in Qt Creator using qbs In-Reply-To: <0A318B84-3380-4B79-BB47-5AB6095A7B90@qt.io> References: <0A318B84-3380-4B79-BB47-5AB6095A7B90@qt.io> Message-ID: It is already set. I had already Group { fileTagsFilter: product.type qbs.install: true } from Qt Creator project creation wizard. Also I am using qbs 1.6.0 and Qt Creator 4.1.0 2017-01-19 9:21 GMT+01:00 Jake Petroules : > Sorry, I forgot to say you also need qbs.install: true in the Group. So: > > Group { > fileTagsFilter: product.type // equivalent to fileTagsFilter: ["application"] > qbs.install: true > qbs.installDir: "/foo/bar" > } > >> On Jan 19, 2017, at 12:13 AM, Benjamin TERRIER wrote: >> >> 2017-01-18 19:03 GMT+01:00 Jake Petroules : >>> Group { >>> fileTagsFilter: product.type // equivalent to fileTagsFilter: ["application"] >>> qbs.installDir: "/foo/bar" >>> } >>> >> >> This does not seems to work. Qt Creator still copies the binary to "/" >> on the remote device. > > -- > Jake Petroules - jake.petroules at qt.io > The Qt Company - Silicon Valley > Qbs build tool evangelist - qbs.io > From christian.kandeler at qt.io Tue Jan 24 13:01:52 2017 From: christian.kandeler at qt.io (Christian Kandeler) Date: Tue, 24 Jan 2017 13:01:52 +0100 Subject: [Qbs] Qbs 1.7.1 released Message-ID: <9da0916e-7234-4d9e-ea36-360e50c84681@qt.io> Hello, I'd like to announce the release of Qbs 1.7.1, fixing a number of issues uncovered in version 1.7.0. Source and binary packages as well as a change log can be found at https://download.qt.io/official_releases/qbs/1.7.1/. This release of Qbs is also shipped as part of Qt Creator 4.2.1. Best regards, -- Christian Kandeler Senior Software Engineer The Qt Company GmbH, Rudower Chaussee 13, D-12489 Berlin Geschäftsführer: Mika Pälsi, Juha Varelius, Mika Harjuaho. Sitz der Gesellschaft: Berlin, Registergericht: Amtsgericht Charlottenburg, HRB 144331 B