Denis, I am very interested in your work. If you happen to create a patch, please add me as a reviewer. I might be able to help here and there.
Supporting IAR could potentially help me to sell Qbs in my company. IAR is proprietary *** but it even provides a Linux command line version these days. Nevertheless it requires a license server which makes public automated regression tests impossible. If it ever comes to a patch, I can try to leverage my company's infrastructure for automated regression testing. Richard On Thursday, 13 December 2018, Denis Shienkov wrote: > Hmm.. > > > > The compiler is looked up in the PATH if the respective property is not > set. > > I'm don't understand a bit.. What if my PATH contains two compilers? > > > if the respective property is not set. > > About what of property does you mean? > > > In the case of Qt Creator, all the relevant information comes from the > Kits (which are turned into qbs profiles), so the Probe is not used for > look-up. > > Hmm.. but how then QBS knows about the assempler, linker names? > > PS: I try co create an own module for "IAR" toolchain and use it together > with QtC. And I see that a Probes > from my module gets called. Although, I have added a new 'IAR' kit to > QtC... So, it is unclear for me. > > > > чт, 13 дек. 2018 г. в 12:38, Christian Kandeler <[email protected]>: > > > On Thu, 13 Dec 2018 12:16:52 +0300 > > Denis Shienkov <[email protected]> wrote: > > > > > How does it work? Why we need in this Probes at all? > > > > The compiler is looked up in the PATH if the respective property is not > > set. In the case of Qt Creator, all the relevant information comes from the > > Kits (which are turned into qbs profiles), so the Probe is not used for > > look-up. > > > > > > Christian > > _______________________________________________ > > Qbs mailing list > > [email protected] > > https://lists.qt-project.org/listinfo/qbs > > > _______________________________________________ Qbs mailing list [email protected] https://lists.qt-project.org/listinfo/qbs
