Re:C++ unit testing with Qt Test, part 2: advanced testing
by rasjani on Wednesday November 29, 2017 @10:30AM
(#15807497)
Qt creator integration relies
[ Parent
| on HN ]
Re:C++ unit testing with Qt Test, part 2: advanced testing
by rasjani on Wednesday November 29, 2017 @10:32AM
(#15807514)
Heavily on the directory structure and how one sets up the the qmake's pro files. This is very cumbersome for mono repos with multiple build targets.
Re:C++ unit testing with Qt Test, part 2: advanced testing
by hhmc on Wednesday November 29, 2017 @11:00AM
(#15807781)
qtcreator works well with mono repo+multiple targets if you use cmake (which is well supported).
Re:C++ unit testing with Qt Test, part 2: advanced testing
by rasjani on Wednesday November 29, 2017 @01:18PM
(#15809317)
I know :( just wanted to point that out and emphasize that it's partly due to qmake and how it's handled within qt creator.
Re:C++ unit testing with Qt Test, part 2: advanced testing
by oblio on Wednesday November 29, 2017 @10:42AM
(#15807616)
You can edit your previous comment.
Re:C++ unit testing with Qt Test, part 2: advanced testing
by loup-vaillant on Wednesday November 29, 2017 @10:49AM
(#15807677)
I think it was on purpose, nested comments being an illustration of a (small) directory structure. Some comments about Lisp achieve a similar effect by littering themselves with parentheses.
Re:C++ unit testing with Qt Test, part 2: advanced testing
by rasjani on Wednesday November 29, 2017 @11:31AM
(#15808070)
No it wasn't intentional - and iOS client I currently have installed does not have edit and account password is something I don't remember without password manager so I couldn't just switch to web :(
Sorry
Re:C++ unit testing with Qt Test, part 2: advanced testing
by blattimwind on Wednesday November 29, 2017 @11:49AM
(#15808282)
When someone suggests that something you did was smart, don't go ahead and tell them they're wrong ;)