Hi All,
Qt is the best multi platform library I have never used (compared to
WxWidget, GTK, SDL...) always evolving to the right direction, with
efficiency and robustness. The only point that was always looking like
an old non evolving component was qmake. So when Qbs became a serious
Hi,
I upgraded to last QCreator version 3.5.0 from previous 3.4.2 and some
of my projects no more compile.
I found the issue:
In some static libraries, I used to export cpp.includepath like that:
Export{
cpp.includePaths:[buildDirectory+"/GeneratedFiles"]
}
So that all application
Hi,
I would like, in a rule of a product (application), apply some
modification on the target files of another product (dynamic library) on
which the application depends.
I tried using inputsFromDependencies as following but is does not works.
Product {
type:['dynamicLibrary','mylib']
Hi Christian,
Le 03/09/2015 17:14, Christian Kandeler a écrit :
> On 09/03/2015 05:00 PM, olivier musse wrote:
>> I would like, in a rule of a product (application), apply some
>> modification on the target files of another product (dynamic library) on
>> which the applicatio
See this link
https://bugreports.qt.io/browse/QBS/?selectedTab=com.atlassian.jira.jira-projects-plugin:summary-panel
1.5 and 1.6 have release date.
Le 09/07/2015 10:09, Christian Kandeler a écrit :
On 07/09/2015 10:02 AM, olivier musse wrote:
1.5 seems to be planned on September, this is not so
. These
are small projects so qmake is ok.
Thanks
Olivier
Le 09/07/2015 09:48, Christian Kandeler a écrit :
On 07/08/2015 07:12 PM, olivier musse wrote:
Many thanks for these details so now we know why it does not work. We
have migrated from qmake to qbs for all our project for desktop
(windows,mac, linux
Hi Joerg,
Thanks a lot for this work. We will test it as soon as possible dans
give you a feedback on it.
BR
Olivier
**
Le 19/02/2015 12:52, Joerg Bornemann a écrit :
On 13-Feb-15 15:01, olivier musse wrote:
Thanks, it seems you know Qt Quick Compiler better than I ;o)
So when do you
Hi Joerg,
Thanks, it seems you know Qt Quick Compiler better than I ;o)
So when do you think the magic part can be added to QBS ?
Regards
*Olivier MUSSE*
*/Mana-Sys SARL/*
fixe : +33(0)2.90.89.43.10
mob : +33(0)6.84.14.20.33
Le 13/02/2015 14:21, Joerg Bornemann a écrit :
On 13-Feb-15
Hi Joerg,
We will now build with prefix and install for sure. I just would like
to clarify this point for users like us which compile on windows using
default configure options and who will fight like us with this issue.
I've built Qt 5.3.2 with the following options here on Windows with
with default settings (so don't install)
we can not used the compiled version of Qt with QBS.
Perhaps there is something to do on that with qbs.
Regards
Olivier
Le 28/11/2014 09:51, olivier musse a écrit :
Hi Christian,
After testing different cases we found the bug.
https://bugreports.qt
/05/2014 01:57 PM, olivier musse wrote:
Finally the response on bug
https://bugreports.qt-project.org/browse/QTBUG-42959
says that we must not run an install on a Qt compiled without a prefix
(which is the default on windows).
So if we just configure and compile Qt with default settings (so
) is that there is
no issue at all to work with qmake on windows without installing and it
does not work with QBS.
Regards
Le 05/12/2014 14:24, Christian Kandeler a écrit :
On 12/05/2014 02:14 PM, olivier musse wrote:
If we do not install : qbs is not working : we got the Module
Qt/designer-private could
/2014 12:21 PM, olivier musse wrote:
It's a big issue on our side since we have many different versions of Qt
we have compiled and not having the .prl files well filed in.
At this point, after our last QBS upgrade, we can no more compile and so
distribute any new version of our products to our
that so many times, with nmake or jom and finally found
(looking in all version we compiled in the past) that .prl files are
always empty. This is really strange.
Thanks for you efficient and quick help.
Olivier
On 10/16/2014 03:18 PM, olivier musse wrote:
We got an issue with QBS last
Le 06/09/2014 00:45, Jake Petroules a écrit :
On 2014-09-05, at 04:18 AM, olivier musse olivier.mu...@sfr.fr wrote:
Hi,
Thanks for these informations, they are precious.
In fact we are already using the cpp.rpaths property and the
cpp.installNamePrefix property is not documented.
Whatever
Le 27/05/2014 09:26, Christian Kandeler a écrit :
On 05/27/2014 12:40 AM, olivier musse wrote:
I have implemented Rules for qlalr and flex in qbs but i'm facing an issue.
My qlarl rule is well working since the generated cpp file is a file
that is compiled.
But my flex rule is not working
HI Christian,
Many thanks, it is working
Regards
On 05/27/2014 11:19 AM, olivier musse wrote:
2) If you want your generated file to be considered a C++ source file,
you need to tell qbs that by giving it the cpp file tag:
Artifact {
fileName:ruleslexer.cpp
Hi,
I have implemented Rules for qlalr and flex in qbs but i'm facing an issue.
My qlarl rule is well working since the generated cpp file is a file
that is compiled.
But my flex rule is not working because the generated file is included
from another cpp file so is excluded from the files
Hi,
Sorry if it is not the place to do that.
I was looking at Qbs story for about a year, hoping one day to migrate
all my projects from qmake to QBS.
Two weeks ago I started a migration on a single project and finally
decide to migrate our 16 active projects (40 .pro files and 60.pri files)
On 05/22/2014 04:19 PM, olivier musse wrote:
Property inheritance is really nice and simple. Thanks for this
important information.
I have succeed to verify it, but then have another question : How can
I detect in the sub project if the property is already set at an higher
level project
I agree, no need for specific config, but perhaps simply add information
to the Qbs quick reference page in the same section as CONFIG+=console
http://qt-project.org/wiki/Qbs-Quick-Reference
BR
Olivier
On 22-May-14 23:47, olivier musse wrote:
It looks like I found myself the solution :
Only
Hi,
Once again an issue while trying to get properties in a Rule, I found
the following is not working and ask myself if it is a bug or not.
This should really nice if it works then enabling to add to any product
a set of properties and use them in associated rules.
See my example below
Christian,
The bug I was talking about (project prefix) is in a Rule artifact.
I do something like (separated in multiple files but the same hierarchy)
Project{
property string myProp:val
Project{
Product{
Rule{
inputs:['myinputs']
Artifact {
Hi,
I would like to compile a designer plugin with qbs.
Is that possible?
If yes wake are the qmake equivalent to CONFIG+= plugin designer.
Many thanks for help
Regards
Olivier
___
QBS mailing list
QBS@qt-project.org
to
defines group of files that can be precompiled in a simpler and more
efficient way.
Regards
Olivier
On 05/21/2014 12:08 AM, olivier musse wrote:
Hi,
I want to create a module to automatically create and compile a pre
compile header file in my project
For that I create the following module
Why
Hi,
I'm back on that point after working on it this night trying to find a
solution without success. Perhaps I'm missing something, it should be
possible to do that with qbs.
Hereafter is a sample more close to what is finally my case.
Imagine I'm developing two applications app1 and app2
Hi,
I want to create a module to automatically create and compile a pre
compile header file in my project
For that I create the following module
- generatePCH.qbs
importqbs
import qbs.TextFile
import qbs.FileInfo
Module {
Rule {
inputs: ['pch']
multiplex:true
]
}
app2_project.qbs
Project {
references:[static.qbs, app2.qbs]
}
global.qbs
Project {
references:[static.qbs, app1.qbs, app2.qbs]
}
This should solve your problem.
Regards,
Thomas
2014-05-18 19:00 GMT+02:00 olivier musse olivier.mu...@sfr.fr
mailto:olivier.mu...@sfr.fr
Hi,
I have an issue while trying to create a project made of multiple
subprojects.
I have a project made of multiple application where each application use
a common static library. I want each application to be able to compile
as a standalone application but want also a global project to
Hi,
What is the best way to share source files and functionality among
different projects.
1) imaging I have some source files I want to share among multiple
projects. What is the best way to include these files using QBS?
With Qmake we use to do something like that
common_source.pri :
, olivier musse wrote:
What is the best way to share source files and functionality among
different projects.
If you don't the source compiled built with different build settings,
then I recommend creating a static library, like you did.
Source file collections (like .pri files
Hi,
I'm trying to print information in qbs (qbs QCreator plugin) but do no
succeed to make it work.
Application{
name: {
print( now evaluating the product name);
return MyProductName;
}
}
Does such a code must print something, somewhere in
to ask for information on qbs. I've answered your questions inline.
On 2014-05-12, at 05:56 PM, olivier musse olivier.mu...@sfr.fr wrote:
Hi everybody,
First sorry if this is not the right place for getting informations but
after many hours looking on Internet I did not found what I need.
Working
.
Regards
Olivier
Hi Olivier,
This mailing list and #qt-qbs on Freenode (IRC) are indeed the right places
to ask for information on qbs. I've answered your questions inline.
On 2014-05-12, at 05:56 PM, olivier musse olivier.mu...@sfr.fr wrote:
Hi everybody,
First sorry
34 matches
Mail list logo
