On 05/26/2014 07:10 PM, Kevin Chaves wrote:
I thought I read something about qbs being able to use inheritance but
I’m not sure if this is true. And I’m a little confused over the
difference between Project { references: } and Project { SubProject {}
}.
references is a shorter way of saying
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 because the generated file is included
from another
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
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
fileTags: cpp
}
This is what I have done but then the
Guys, can someone help me, please? :)
BR,
Denis
2014-05-26 12:48 GMT+04:00 Denis Shienkov denis.shien...@gmail.com:
Hi guys..
In my project I want linking with an third-party HASP libraries (as
example).
E.g. from the HASP I have an only one linking library (*.lib) and one
runtime
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
On 05/27/2014 12:03 PM, Denis Shienkov wrote:
Guys, can someone help me, please? :)
Sorry, this is so weird I don't even know where to start. The fact that
you add DLLs as source files takes me right out, for instance. Perhaps
you want cpp.dynamicLibraries? I can only guess.
Christian
Thanks for all the information. This helped clear up a lot of things I was
unsure of.
It looks like I might be able to do something like this in 1.3 where
sourceDirectory can be used with… moduleSearchPath I think it was.
No idea what sourceDirectory has to do with this.
I
mentioned
On 05/27/2014 04:19 PM, Kevin Chaves wrote:
I guess you could achieve something like that with a custom Rule or
Transformer, but you should be aware that that part of the build will be
opaque to qbs, so a bit of time will be wasted calling qmake/make when
building incrementally as qbs
Possibly. I guess it depends on what exactly you want to do.
One example is to build qwt and export the paths to the headers and .lib. After
this initial build we shouldn't have to worry about building it again in the
project tree. The applications that use it need to be configured to link to
On 05/27/2014 05:36 PM, Kevin Chaves wrote:
Possibly. I guess it depends on what exactly you want to do.
One example is to build qwt and export the paths to the headers and
.lib. After this initial build we shouldn't have to worry about building
it again in the project tree. The
Hi Kevin,
Regarding Qbs integration in QtCreator 3.1 we see the same issues. I know
there is QBS-17 and some more, but nobody seems to be working on these. So
some time ago I did a quick hack which at least allows us to add files to
Qbs projects in a convenient way. It's probably not the best
12 matches
Mail list logo
