Re: Next for newlib?
"Craig Small" <[email protected]> ("csmall") Thu, 25 Aug 2022 07:22:56 +1000
| Newsgroups | gmane.linux.procps.devel |
|---|---|
| Message-ID | <CALy8Cw52PZSRu97pibjzANp0J3+aUpP6Drrfxw9Euo14991OQQ@mail.gmail.com> |
On Wed, 24 Aug 2022 at 06:28, Jim Warner <[email protected]> wrote: > Instead of just proc-2 as the name, I think we should name the installed > include directory libproc-2 or maybe libproc2 without the dash (or even > just libproc). That's similar to some other library approaches. > So that would mean for install we would have: /usr/include/libproc2/*.h /usr/lib/<triplet>/libproc-2.so > I don't think it's very important what we name it under our development > tree. However, our tree is a bit of a mess even beyond the include > directory inconsistencies. > Currently we have this setup: . some source for binaries and build system, some project documents contrib/ Um, a minimal ps, what is this? doc/ Library man pages Documentation/ Project documentation in markup style include/ Local includes headers for binaries and library lib/ Utility functions for library and binaries, test programs for binaries misc/ script to generate the git version number proc/ Library source and headers, plus test programs ps/ source for ps testsuite/ test scripts top/ top source code My suggestion: doc/ Project documentation except for the items that should be in root man/ Includes all manpages local/ Contains the headers and utility sources, what was in include/ and lib/ src/ Source for binaries, there can be a ps and top subdirectory or not. src/tests source for test programs for binaries. proclib/ source for library. Not too sure about this, could be libsrc or srclib or something else. Could even still be proc/ proclib/libproc2 headers for library. The "libproc2" part should be the same as the install directory is e.g if we decide /usr/include/rainyday/*.h is the directory, this one would be called proclib/rainyday proclib/tests test programs for library testsuite/ Remains the same, test scripts only This would mean . -> remain, src/ and doc/ contrib/ Let's see if we can remove this, does anyone use any of this? doc -> man/ Documentation -> doc include -> local lib -> local and src/tests misc -> move this one file to root proc -> proclib and proclib/tests ps -> src/ps testsuite -> testsuite top -> src/top