On Thursday 27 February 2014 15:54:46 Joerg Bornemann wrote:
> > This property could be useful to generate paths to such tools; but it
> > might be better to
> >
> > have variables like cpp.objcopyPath declared by qbs.
>
> The objcopy tool isn't used ATM by qbs. That's why there's no such
> property. If we're going to introduce such properties, where do we draw
> the border? Do we provide a path for every program in binutils?
CMake, for example, provides paths for ar, ranlib, strip, ld, nm, objdump and
objcopy [1].
Again, path for "size" tool does not exist :/
It might be better to have a single function to get these paths.
e.g. cpp.binaryUtilPath("size") returns path to toolchain's size tool.
[1]
http://cmake.org/gitweb?p=cmake.git;a=blob;f=Modules/CMakeFindBinUtils.cmake;h=829b6ffd443afc4adca76765763f24df441171a4;hb=HEAD
_______________________________________________
QBS mailing list
QBS@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qbs
