On 25 November 2013 08:55, Ziller Eike <[email protected]> wrote: > On Nov 23, 2013, at 5:22 PM, Mateusz Loskot <[email protected]> wrote: >> On 23 November 2013 16:20, Mateusz Loskot <[email protected]> wrote: >>> On 23 November 2013 14:54, Tobias Hunger <[email protected]> wrote: >>>> On 23 Nov 2013 00:27, "Mateusz Loskot" >>>> >>>>> Regardless, I'm always getting this file created >>>>> >>>>> $HOME/.config/QtProject/qbs.conf >>>>> >>>>> I can manually remove $HOME/.config/QtProject, >>>>> launch QtC as above, open a .qbs project and the file is back there. >>>>> >>>>> Shouldn't it respect the -settingspath? >>>> >>>> I don't think it should. >>>> >>>> While I do see that people will see qbs and At Creator as more closely >>>> related than let's say QtC and cake, I do not think we should treat and >>>> differently. >>>> >>>> Qbs is a separate application, similar to cmake, autotools and gdb. Nobody >>>> expects those to respect Qt Creators settingspath either. >>> >>> That makes perfect sense to me. >>> >>> The >> >> (Sorry, sent prematurely) >> >> I meant, the misunderstanding was that I thought qbs.conf file >> was created by the Qbs plugin itself, not the Qbs an application. > > Well, it is created by the qbs *library* that the Qbs plugin links to and > uses, so the distinction is not that black&white ;)
I see. > But still, the settings that are created are the ones that are also used by > the qbs command line tool, so the separation is indeed there. Yes, it makes sense to me. Thanks for the updated explanation. Best regards, -- Mateusz Loskot, http://mateusz.loskot.net _______________________________________________ Qt-creator mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/qt-creator
