4 ms·
> It’s also less ergonomic: a developer can’t go into a specific sub folder and build ONLY that sub folder and its dependencies I'm not a fan of qmake but thi
by jcelerier 7y ago
> It’s also less ergonomic: a developer can’t go into a specific sub folder and build ONLY that sub folder and its dependencies
I'm not a fan of qmake but this works just fine with it.
- wwright 7y agoThe dependencies is the trick. Given I have this layout: bin/bin.pro # specify bin/bar/ as subfolder bin/bar/bar.c bin/bar/bah.h bin/bar/bar.pro lib/lib.pro # specify lib/foo/ as subfolder lib/foo/foo.c lib/foo/foo.h lib/foo/foo.pro project.pro # specify bin/ and lib/ as subfolders And I have a fresh checkout, how do I compile "bin/bar" and all of its dependencies automatically? I want to run ONLY "bin/bar". I don't want to compile the entire repo. I don't want to have to investigate "bin/bar" and learn all of its transitive dependencies. I just want to run "bin/bar". Honest to god, I have wanted this for over a year and it does not seem possible.