There is a somewhat clumsy manual option.
The modules subdirectory in the new structure is a drop-in place.
If you clone core (without --recursive) and then manually check out only
the submodules you want to build, the build does not need to be
re-configured: it will always build all checked-out submodules. You can
still develop, branch, merge in such a sparse source structure.
It's certainly not automatically by target, but you might be able to get
by with creating two workspaces: complete and classic. Each one would
have the appropriate target configurations: those that can build
everything or those that just support the minimal base.
Cheers,
~Ralph
On Wed, Nov 29, 2017 at 8:47 PM, Andrew Johnson <[email protected]
<mailto:[email protected]>> wrote:
On 11/29/2017 02:07 AM, Dirk Zimoch wrote:
>
> I will try to implement something. My first attempt failed for the
> reason Andrew outlined. It is not possible to simply skip the all PVA
> modules for a specific T_A because at that time T_A is not yet defined.
> A flag needs to be checked inside every module.
It's even more complicated than that though; once we get Base to only
build the PVA modules for some target architectures and not for others,
how are the Makefiles in downstream modules such as AreaDetector
supposed to be set up to only build things that depend on PVA for
targets that have PVA built?
After thinking this over last night I now think it would be much more
complex and invasive than the original idea appears. It certainly isn't
going to be possible in the 7.0.1 release.
If you want to use EPICS 7, I think you will have to upgrade your
devices to run on a fully supported OS; partial support like this is
likely to be too invasive to be cost-effective.
- Andrew
--
Arguing for surveillance because you have nothing to hide is no
different than making the claim, "I don't care about freedom of
speech because I have nothing to say." -- Edward Snowdon
