Am Fri, 19 Nov 2010 13:31:31 +0100 schrieb Frank Schönheit <frank.schoenh...@oracle.com>:
> Hi, > > just noticed (well, have been told) that in the new GNU make build > system (oh, before I start any ranting: <disclaimer>Great Stuff (TM), > really!</disclaimer>) it is expected that header files which are to be > exported from a module reside in <module>/inc/<module>. And also, but > my understanding might be wrong here: Files are exported *if and only > if* they reside there. > > While it is great to clean up this "which files are delivered from > where" mess we currently have, the above also implies that files from > <module>/inc/<module>/* are not exported anymore, i.e. it is not > possible to organize header files below the second <module> level. > Instead, they all need to be thrown on a big fat header file pile. > > Is this understanding correct? No. Currently Headers are explicitly declared to be delivered and can come from anywhere. Nonewithstanding this, it still makes a lot of sense to have a good structure for the headers. > > If so, I think this is not a good idea at all: Consider modules such > as toolkit, svtools and svx, where there is a more or less complex > (well, let's say: well-arranged and -readable) folder structure below > the module's include folder. Putting all those files into the flat > <module>/inc/<module> folder will certainly not contribute to the > readability of the source tree. Why would you want to put them into a _flat_ structure? Also note that from the named modules toolkit and svtools are already migrated to the new builds system. Just have a look at cws gnumake2. Best, Bjoern --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@openoffice.org For additional commands, e-mail: dev-h...@openoffice.org
