Closed rlebeau closed 5 years ago
Have to admit it's a bit hidden at the end of the page but:
Info: For all elements of search_pathes, browsing_pathes, source_folders, raw_folders, projects and experts, the properties compiler_min, compiler_max (to specify a range, see info.json) and compiler (to specify a specific version) are supported. These allow you to specify specific compilers for each element which results in skipping of an element if the compiler version does not fit.
Ah, yes, I didn't see that earlier. Thanks
I'm thinking of adding Indy to Delphinus, however Indy does not yet utilize the
{$LIBSUFFIX}
directive in its packages (that is coming in a future release), so it still has compiler-specific projects, each with different.dproj
and.groupproj
filenames for individual Delphi compiler versions (ie,Indy160.groupproj
,Indy250.groupproj
, etc).I see how the
Delphinus.Info.json
file can specify a range of supported Delphi compiler versions for filtering purposes, but I see no way for theDelphinus.Install.json
file to specify installation instructions for individual compiler versions. For instance, in theprojects
array, let eachproject
optionally specify a supportedcompiler
, eg:If a
project
does not specify acompiler
, assume it supports all compilers.When Delphinus is building projects, have it ignore any
project
that has acompiler
that does not match the host IDE/compiler.In a future release, Indy's folder structure will change to organize projects into version-specific folders, so being able to specify a specific
compiler
perproject
would still likely be needed, eg: