| Re: [pde-build-dev] A question about map files |
Jeff McAffer wrote:
Yes. Buckminster will direct component requests to 'search paths' consisting of 'providers' that are tried in sequence until either a perfect match is found or the list is exhausted. At that time the best match is chosen based on a set of criteria. The source versus binary preference is one criterion that can be added to the query.one way to look at this is that all the map file entries should be fetched as built things if you can (i.e., if they are already built) and as source if not. in the case of the base.* they will always only be in binary/biult form. In your quest can you interpret the map file in that form and arrange your repos and fetch technology to suit?
The functionality now added that involves reading a PDE-style map directory was implemented as a special purpose provider. It is able to resolve the components that are listed in the map directory and will materialize differently depending on what it finds (.jar's are "imported" into the workspace).
Another provider can be configured in the same search path in order to find pre-built binaries for all components should they exist. The question arises; where should it look for binaries? Do you envision a local (on your machine) cache, a common ftp/http site of some sort, or perhaps an update site?
Regards, Thomas Hallgren