Re: [Qbs] (no subject)

On 4/6/21 10:58 AM, Dan Pat wrote: Hello. A bunch of Products must be built using a certain set of "cpp" flags. I created a special Module (later referred to as "CppFlags"") containing those flags and had these Products depend upon CppFlags. There are other Modules that the Products depend on,

[Qbs] (no subject)

Hello. A bunch of Products must be built using a certain set of "cpp" flags. I created a special Module (later referred to as "CppFlags"") containing those flags and had these Products depend upon CppFlags. There are other Modules that the Products depend on, and some of these Modules contain

Re: [Qbs] (no subject)

Thanks, that seems to work. On Mon, 11 Jan 2021 at 14:56, Christian Kandeler wrote: > On 1/11/21 9:23 AM, Dan Pat wrote: > > Hi. I have a question about making third-party libraries > available/visible > > when running programs from qtcreator. We have a number of prebuilt > > libraries in the

Re: [Qbs] (no subject)

On 1/11/21 9:23 AM, Dan Pat wrote: Hi. I have a question about making third-party libraries available/visible when running programs from qtcreator. We have a number of prebuilt libraries in the source tree which are currently wrapped in Modules. The modules contain include/library paths, so any

[Qbs] (no subject)

Hi. I have a question about making third-party libraries available/visible when running programs from qtcreator. We have a number of prebuilt libraries in the source tree which are currently wrapped in Modules. The modules contain include/library paths, so any depending products build fine, but

Re: [Qbs] (no subject)

Hi, Ivan. The work is incomplete and I have insufficient knowledge to go on without investing time which I don't have right now, sorry. Maybe, I could reach you over a private channel to share my work and the issues I am up against. What do you think? вт, 15 дек. 2020 г. в 15:41, Иван

Re: [Qbs] (no subject)

Hello, Dan! Any chance you publish your solution? I am interested in wasm support as well Ivan > > The goal is to get qbs projects compiled to WebAssembly using the emscripten > toolchain (and Qt WebAssembly). As for upstreaming: I have managed to come up > with a working but hacky solution

Re: [Qbs] (no subject)

> > You can provide your own cpp implementation by overriding the search > path, but I don't see how you would be able to refer to the contents of > the original directory. Note that the files there are implementation > details and their presence and names cannot be relied upon. It's not a >

[Qbs] (no subject)

Hi, I have created a Module that inherits GenericGcc and hence is loaded as a "cpp" module when certain conditions are met. During development the module file was located in the module directory of the QtCreator installation. But I would like to move it to the qbs module directory inside our

Re: [Qbs] (no subject)

Hi! > Is qbs supposed to work with Qt WebAssembly (I cannot get it to work)? No, at the moment Qbs does not provide support for WebAssembly. However, since you can do anything with Qbs, it should be possible to get it to work as well. __ In the end, it boils down to writing a Module that

[Qbs] (no subject)

Is qbs supposed to work with Qt WebAssembly (I cannot get it to work)? If not, are there plans to add support? ___ Qbs mailing list Qbs@qt-project.org https://lists.qt-project.org/listinfo/qbs

Re: [Qbs] (no subject)

https://bugreports.qt.io/browse/QBS-1522 > 29 нояб. 2019 г., в 08:03, Dan Pat написал(а): > > > Who imposes that requirement and why? > Ok. Here's the thing. The project I am working on is based on Qt library and > consists of a bunch of libraries and executables with dependencies between >

Re: [Qbs] (no subject)

Ok, I'll give it a try. Thank you! пн, 2 дек. 2019 г., 22:27 Иван Комиссаров : > Hello, Dan! > > It’s very sad to hear that QtC crashes for you. > > There’s one known issue in qbs which will be fixed with QtC 4.11 release. > Can you please try release candidate if it works better or not? >

Re: [Qbs] (no subject)

Hello, Dan! It’s very sad to hear that QtC crashes for you. There’s one known issue in qbs which will be fixed with QtC 4.11 release. Can you please try release candidate if it works better or not? https://download.qt.io/development_releases/qtcreator/4.11/4.11.0-rc1/ If release candidate

[Qbs] (no subject)

Hello, my qtcreator keeps crashing during reparsing of qbs projects (windows 10) - like twice or thrice a day. I'd really like to provide something along the lines of a log or a backtrace. Does such a log exist? AFAIK, to get a meaningfull backtrace for release builds under windows some sort of a

Re: [Qbs] (no subject)

> Who imposes that requirement and why? Ok. Here's the thing. The project I am working on is based on Qt library and consists of a bunch of libraries and executables with dependencies between them expressed via a "Depends" language item. Plus there a number of pre-built third-party libraries

Re: [Qbs] (no subject)

It’s worth mentioning, that compiling with verbose flag can give some insight on what libraries/options clang-cl passes to the linker: clang-cl -v -fsanitize=address main.cpp Иван Комиссаров > 28 нояб. 2019 г., в 17:23, Иван Комиссаров написал(а): > > I did a small research and was able to

Re: [Qbs] (no subject)

I did a small research and was able to compile a small example with clang-cl and asan. Here are the flags I had to set manually: cpp.optimization: "none" cpp.cxxFlags: [ "/MT", "-fsanitize=address", ] cpp.linkerFlags: [

Re: [Qbs] (no subject)

On Thu, 28 Nov 2019 18:58:54 +0500 Dan Pat wrote: > Hello. I am trying to use Asan in my project (windows 10, clang-cl). > There's a requirement for the Asan import library to appear first in the > linker's list of import libraries. Who imposes that requirement and why? > I cannot seem to

[Qbs] (no subject)

Hello. I am trying to use Asan in my project (windows 10, clang-cl). There's a requirement for the Asan import library to appear first in the linker's list of import libraries. I cannot seem to find a way to achieve this with qbs. Any suggestions? ___

[Qbs] (no subject)

On 14 December 2016 at 22:51, Christian Kandeler wrote: > On 12/13/2016 11:44 PM, Ch'Gans wrote: >> On 13 December 2016 at 10:22, Ch'Gans wrote: >>> On 13 December 2016 at 07:32, Jake Petroules wrote: Also fails on MinGW :)

Re: [QBS] (no subject)

On 15/05/2013 18:28, Kakadu wrote: Now qbs take source file and generates result in build folder. I have compiler which takes source files and places result always in the same folder. Is it possible to hack qbs to copy source file to build directory and built it there? How difficult is

Re: [QBS] (no subject)

Oh, I didn't expect that prepare can return many commands. thanks. -- Best wishes, Kakadu 16.05.2013, 12:14, Joerg Bornemann joerg.bornem...@digia.com: On 15/05/2013 18:28, Kakadu wrote:  Now qbs take source file and generates result in  build folder. I have compiler which takes source