oops, of course,
property string gnuToolsDir: MyFunctions.findGnuToolsDir();
instead of
property string gnuToolsDir: YourFunctions.findGnuToolsDir();
BR,
Denis
2014-05-15 15:39 GMT+04:00 Denis Shienkov :
> E.g. IMHO, in your case should be like this:
>
>
> = myproject/myproject.qbs =
>
> imp
E.g. IMHO, in your case should be like this:
= myproject/myproject.qbs =
import qbs 1.0
Project {
qbsSearchPaths: "qbs"
references: [
"app/app.qbs",
]
}
= myproject/qbs/imports/MyFunctions/functions.js =
function findGnuToolsDir()
{
...
}
= myproject/app/app.qbs =
imp
Is there no way to do this in two files instead of three? It doesn't seem
like I can put the `import YourFunctions` before the `Project`, so I need a
separate file for the Project and Product, and then a third for the
javascript. Is that right?
Cheers,
Tim
On 15 May 2014 10:37, Denis Shienkov
> It makes no sense to distribute this information as the location of the
toolchain is dependent on the host system.
True, but I'd like to be able to distribute a build file which is a little
bit intelligent about finding the tool chain. For example on Windows, the
default install directory is
C:
On 05/15/2014 11:53 AM, Denis Shienkov wrote:
> > Well I guess it is fairly special - I'm compiling stuff for a
> microcontroller using gcc for arm embedded.
>
> As I know, you can create a custom *.config file in which to specify
> paths to your toolchain, and then pass to qbs this your config fi
On 05/15/2014 11:44 AM, Tim Hutt wrote:
> Well I guess it is fairly special - I'm compiling stuff for a
> microcontroller using gcc for arm embedded. It needs specific flags and
> linker scripts and so on.
See http://qt-project.org/doc/qbs-1.2/cpp-module.html for information on
the cpp module.
>
> Well I guess it is fairly special - I'm compiling stuff for a
microcontroller using gcc for arm embedded.
As I know, you can create a custom *.config file in which to specify paths
to your toolchain, and then pass to qbs this your config file. Then qbs
will take your profile as default profile..
Well I guess it is fairly special - I'm compiling stuff for a
microcontroller using gcc for arm embedded. It needs specific flags and
linker scripts and so on. Is there any documentation on profiles? The only
thing I could find was on listing them with the qbs binary which I don't
have (since I'm u
Hi,
1. Your function shall be in the functions.js file , e.g. in:
/yourproject/qbs/imports/YourFunctions/functions.js
2. Also your Project should have an option:
Project {
...
qbsSearchPaths: "qbs"
...
}
3. Your Product's file should contains:
...
import YourFunctions
...
...
property string gn
On 05/15/2014 10:30 AM, Tim Hutt wrote:
> I have a QBS script that depends on using the GNU Arm toolchain, and I
> want it to automatically find them (on Windows for now).
Are you sure that's really what you want? Toolchain information
typically comes from the "outside" via a profile, and then it
Hi,
I have a QBS script that depends on using the GNU Arm toolchain, and I want
it to automatically find them (on Windows for now). In my QBS I have this
line:
property string gnuToolsDir: "C:/Program Files/GNU Tools ARM
Embedded/4.8 2014q1"
And then I use that elsewhere. I want to set
11 matches
Mail list logo
