> No, that's why I've copied the files in the package/ directory.
Yes, but in the README you instruct users to copy these files from the NSIS installer
whereas it isn't part of that installer and is already provided by valide sources itself.
> It's possible, but how to know the dependencies installation path?
Doesn't waf provide some functionality to find these out? Using pkg-config for instance?
> I did a quick overview of the different systems, but only waf supports vala and
> offers the clear syntax of python.
CMake is fairly easy to extend. IMHO, waf isn't mature just yet. Usually you just get
some incomprehensible, 20+ lines stacktrace pointing to a 'string' as the source of
the problem in case of an error.
> No, that's why I've copied the files in the package/ directory.
Yes, but in the README you instruct users to copy these files from the NSIS installer
whereas it isn't part of that installer and is already provided by valide sources itself.
> It's possible, but how to know the dependencies installation path?
Doesn't waf provide some functionality to find these out? Using pkg-config for instance?
> I did a quick overview of the different systems, but only waf supports vala and
> offers the clear syntax of python.
CMake is fairly easy to extend. IMHO, waf isn't mature just yet. Usually you just get
some incomprehensible, 20+ lines stacktrace pointing to a 'string' as the source of
the problem in case of an error.