> 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
Hi again :-)
Whether one prepares macOS bundles, AppImage files of MSI installers,
one has to go through the dependency collection step, which is largely
similar for all platforms. To be more explicit, I'm referring to the
kind of job that on macOS is performed by the macdeployqt tool, and that
Hi Richard,
On 28/11/19 01:17, Richard Weickelt wrote:
> Ideally, I think, the user would just invoke some tool and use a prebuilt
> binary and not need to build the run-time from source. If building from
> source is required, let the user install AppImageKit somewhere and just
> point Qbs to the
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
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: [
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
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?
___
