On 13-Aug-14 14:34, Alexandre Cossette-Pacheco wrote:
> So, project "company.product.some_module.submodule" is
> - Located in the "company/product/some_module/submodule" folder
> - With
> "company/product/some_module/submodule/company.product.some_module.submodule.qbs"
> as the full path to the qb
>
> I currently do not see a nice way how to magically determine whether a
>> dot in a name means "hierarchy separator" or "it's just a dot".
>>
>
> And after an office discussion we suddenly see a way on the horizon how
> this can be fixed. Keep track of QBS-665 and QBS-666.
>
That's nice, I'll k
On 13-Aug-14 11:36, Joerg Bornemann wrote:
> I currently do not see a nice way how to magically determine whether a
> dot in a name means "hierarchy separator" or "it's just a dot".
And after an office discussion we suddenly see a way on the horizon how
this can be fixed. Keep track of QBS-665 a
On 12-Aug-14 15:07, Alexandre Cossette-Pacheco wrote:
[...]
> However, project names have stayed awkward to this day; both with Qmake
> and Qbs (our current build system is Qmake, but we maintain scripts that
> parse our .pro files and generate .qbs so we can track progress on Qbs).
> The best we'
On 09-Aug-14 23:12, Erik Schilling wrote:
> Currently qbs does not allow DynamicLibraries with more than one ".".
That's not quite right. Creating dynamic libs with more than one "." in
their targetName is definitely possible.
> Now what is the suggested way to build a structure like:
>
>
