Re: [lmi] Directory structure for multiple-architecture builds

[Greg Chicares]

On 2017-05-23 14:29, Vadim Zeitlin wrote:
[...]
>  I've just realized that I don't actually know how is the end user
> distribution created. Does it use the same structure with "bin"
> subdirectory? This would be somewhat unusual (although not exactly unique)
> for a MSW application...

We copy everything into a single flat directory, much like this:

file_list0 := \
  $(wildcard $(prefix)/local/bin/*$(SHREXT)) \
  $(wildcard $(prefix)/local/lib/*$(SHREXT)) \
  $(wildcard $(bindir)/product_files$(EXEEXT))
all_file_lists := file_list0 file_list1 [...more file lists...]
$(CP) --preserve $(all_file_lists) .

and make a tarball. The 'fardel' target in 'workhorse.make' does it all.

End users extract that to a particular directory, e.g. 'lmi-20170532T1635Z',
which might be usable (without the secret password) throughout 2017-June.
(The next month, they get another.) To uninstall an old version, they just
delete that single directory.