Anyway, I still don’t see the problem - QBS can emulate the build process for
that an IDE normally does, placing the artifacts in the exact places where IDE
would place them. At least, that’s how (unfinished) Xcode generator works - it
builds the app to a generic folder and then creates
> One can argue the other way round, too: Why would A have to take care
of "native" export to B when B does not care for importing A?
Because - 'A' is an universal cross-platform tool, aka QBS. And 'B' - it
is usually a narrowly specialized vendor-specific tool.
And a tool 'B' does not known
On Sun, Feb 17, 2019 at 09:10:32PM +0300, Denis Shienkov wrote:
> > For c++ - yes. Imagine a pure javascript rule that doesn’t invoke any
> «compiler» (like cl or javac) but converts some input to output using qbs
> itself. How that custom rule would like?
>
> But we speak about c/c++ :)
>
> >
