On 04/30/2015 06:03 AM, Christian Gagneraud wrote:
> I think I got confused by how Qtc is doing it:
I'll comment on the Linux-specific parts as an example.
> QtcLibrary.qbs:
> cpp.rpaths: qbs.targetOS.contains("osx")
> ? ["@loader_path/..", "@executable_path/.."]
>
I've build Qt5 from sources like wiki page suggests.
In my .qbs project I define dependencies as follows:
QtGuiApplication {
Depends { name: "Qt"; submodules: [ "gui", "qml", "quick" ] }
Depends { name: "cpp" }
}
This leads to the following parameters to clang:
-I/.../qt5_dev/qtbase/lib
As you probably guessed by that "framework" part I am on OS X Yosemite.
On Fri, May 1, 2015 at 1:29 AM, Dmitry Volosnykh wrote:
> I've build Qt5 from sources like wiki page suggests.
>
> In my .qbs project I define dependencies as follows:
>
> QtGuiApplication {
> Depends { name: "Qt"; submo
The same project, but qmake-based, builds like a charm.
On Fri, May 1, 2015 at 1:36 AM, Dmitry Volosnykh wrote:
> As you probably guessed by that "framework" part I am on OS X Yosemite.
>
> On Fri, May 1, 2015 at 1:29 AM, Dmitry Volosnykh <
> dmitry.volosn...@gmail.com> wrote:
>
>> I've build Qt
Hi,
I recently installed QBS from sources, and to my (bad) surprise i got it
installed in /, instead of the more usual /usr/install (speaking about
Linux obviously). The reason for this is that I didn't configure/use any
prefix and/or destdir (autoconf semantic). Is it a QBS feature or is it
a
On 01/05/15 10:29, Dmitry Volosnykh wrote:
> I've build Qt5 from sources like wiki page suggests.
>
> In my .qbs project I define dependencies as follows:
>
> QtGuiApplication {
> Depends { name: "Qt"; submodules: [ "gui", "qml", "quick" ] }
> Depends { name: "cpp" }
> }
>
> This leads to
