Date: prev next · Thread: first prev next last
2013 Archives by date, by thread · List index


With the need for dmake and build.pl almost gone, I assume that we will want to dump */prj/build.lst files and expressing inter-module dependencies via them, too. That leaves the question how we want to be able to track inter-module dependencies in the future. Specifically, what I am looking for is a command (e.g., make target) to show all the modules that some given module depends on, to help me decide into which module to put newly developed functionality. (Even if this information were no longer relevant for gbuild---what is the future story of "make <module>.all"?---we will IMO nevertheless want to keep module dependencies from turning into a cyclic ball.)

(Btw, top-level "make help" advertises "showdeliverables" and "showmodules" targets, the latter of which looks relevant here, but neither of them works.)

Stephan

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.