On 28-May-14 23:46, Kevin Chaves wrote:
The other odd thing I noticed is that the working directory for a
command isn't created...
I don't think it's a good idea to let the command create its working
directory. A mistake in the working dir property could create strange,
unintended directory
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 solution at all, but it's working for us. I've added the patch
against 3.1 sources to this posting.
Hack or not, I suggest you put this on
On 05/28/2014 04:13 PM, Kevin Chaves wrote:
That is certainly unexpected. If you can reproduce, please file a bug
with a minimal example and the steps to trigger it. It does not happen
for me.
I'll see if i can reproduce it on a smaller scale. There is a very large
stack of subprojects.
I
project dir/qbs/imports/MyItem.qbs:
import qbs
So would project dir br a relative path?
___
QBS mailing list
QBS@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qbs
On 05/28/2014 05:49 PM, kmchaves wrote:
project dir/qbs/imports/MyItem.qbs:
import qbs
So would project dir br a relative path?
I don't think I understand. This is just an example directory layout.
Christian
___
QBS mailing list
Figured it out,
Thanks again everyone, I'm beginning to think that maybe my Qt creator or
ubuntu 14.04 are causing issues. If i make modifications to project i still
have to close and reopen the project, thats including adding files to the
files: [] section of a product. I attached the
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
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
I should have waited another 5 mins before sending that last email…
I changed
function commonCxxFlags{
var flags = “-std=c++0x”
return flags
}
to
property stringList commonCxxFlags:{
var flags = []
flags.push( “-std=c++0x” )
return flags
}
And now it
13 matches
Mail list logo
