> I'll have a similar Group item containing assembly
Hi, seems, you need to use Properties item instead of Group item to use
cpp.assemblerName .
BR, Denis
14.12.2017 23:01, Ola Røer Thorsen пишет:
2017-12-14 18:02 GMT+01:00 Christian Kandeler
mailto:christian.kande...@qt.io>>:
On Thu,
2017-12-14 18:02 GMT+01:00 Christian Kandeler :
> On Thu, 14 Dec 2017 17:46:56 +0100
> Ola Røer Thorsen wrote:
>
> > It's running when I tag the files with "asm", but using the assembler
> "as"
> > instead of "nasm". Any way to override that here for this particular
> group
> > of files? The sour
Hi Damien,
Out of curiosity, which IDE are you integrating Qbs into? We've actually done
some prior work on Qbs IDE integration; you might want to look into the
src/plugins/generator directory of the Qbs sources where you can find a Visual
Studio integration.
There's also the Qbs Qt Creator pl
Thanks for the answer !
I'm currently working on integrating Qbs into another IDE. In this IDE, I
let the user point to the Qbs executable, optionally select a settings
folder and various other options.
Then through the IDE, I let the user select his profile and configuration,
and finally I let hi
On Thu, 14 Dec 2017 17:46:56 +0100
Ola Røer Thorsen wrote:
> It's running when I tag the files with "asm", but using the assembler "as"
> instead of "nasm". Any way to override that here for this particular group
> of files? The source files are not compatible with "as".
You need to set cpp.asse
2017-12-14 17:27 GMT+01:00 Christian Kandeler :
> Have you tagged them properly? The .asm extension is not auto-tagged on
> Linux; you will need to do that "manually" via a Group or a FileTagger
> item.
> See https://doc.qt.io/qbs/cpp-module.html#relevant-file-tags for the
> assembler-related fil
On Thu, 14 Dec 2017 16:21:42 +0100
Damien Courtois wrote:
> I'm not sure if this is a bug or me not understanding the documentation,
> but when I use `qbs run [...] --dry-run profile:foo debug` my project is
> still started.
> Isn't this option supposed to suppress the actual command executions ?
On Thu, 14 Dec 2017 15:52:03 +0100
Ola Røer Thorsen wrote:
> I'm trying to build a project that has some assembly files as well as C++
> code. I'm building from QtCreator using the latest Qt 5.10 release kit
> (Linux x86_64) on KDE Neon.
>
> The assembly files are added to the files property alo
Hi,
I'm not sure if this is a bug or me not understanding the documentation,
but when I use `qbs run [...] --dry-run profile:foo debug` my project is
still started.
Isn't this option supposed to suppress the actual command executions ?
As a side note, I'm doing this to get the full path to the ex
I'm trying to build a project that has some assembly files as well as C++
code. I'm building from QtCreator using the latest Qt 5.10 release kit
(Linux x86_64) on KDE Neon.
The assembly files are added to the files property along with the rest, and
end with .asm. While building qbs seems to just i
2017-12-13 17:36 GMT+01:00 Christian Kandeler :
>
> That happens automatically if the product has a dependency on the Qt.core
> module.
> Note: The correct file tag for headers is "hpp" (not "h", as I wrote in my
> first reply.)
>
>
Yes using "hpp" fixed it, thanks :-)
11 matches
Mail list logo