This is the mail archive of the ecos-discuss@sourceware.org mailing list for the eCos project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
Hi,
is there any possibility / script / work in progress to synthetise the ecos.db file from several sources?
We are developing for several customers who are getting sources, but they generally should not see what else we are working on. It is no problem to only export part of the source tree, but the ecos.db makes a problem here.
Is there actually any information in "package" entries that can't be synthetised from the .cdl files in the tree? Redundant information is often a recipe for problems...
And is there any special reason to keep "target" entries together with the package information?
Is there at least a way to specify an ecos.db file to be used by the ecosconfig / configtool?
Look (far) back in the list archives - I'm sure that Bart mentioned something about this many years ago.
-- ------------------------------------------------------------ Gary Thomas | Consulting for the MLB Associates | Embedded world ------------------------------------------------------------
-- Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |