search

Leont / extutils-hascompiler

Check for the presence of a compiler
5 stars 3 forks source link

Missing functional requirements? #4

Open Leont opened 9 years ago

Leont commented 9 years ago

As split from here

It's not only more reliable - it's more helpful when debugging or admins/packagers/... want to override something without going down the deep of hacking a EU::HC extension overriding the Config handling.

I'm not sure what you're trying to say here.

AFAICT EU::HC satisfies all those requirements

Let's check:

I'm missing the intermediate steps here. Saying "not true" is not terribly helpful, could you tell me what you are missing.

have a sane (and complete) test whether XS and dynamically loading is supported (and permitted by user - mind PUREPERL_ONLY or -pm) by the perl we're running on (keeping cross-compiling and distributed package builds in mind)

Not (yet) true, but I can see the opportunities given by EU::HC

Much of this isn't really the task of this module. The argument handling bits really belong in the install tool, and loading cross-compilated modules may be an unsolved problem but it's hardly a show-stopper.

have the ability to solve all issues at customers with familiar approached (CC=..., CFLAGS=..., ac_cv_have_stdint_h=yes, ...)

Not true

How so? It handles the environmental flags just fine. It doesn't do the ac_* thing, but that's hardly relevant to this matter checking if a compiler works (and frankly, I don't think it's a familiar approach to most people).

have a complete picture when something fails, what fails and why (config.log!)

Not true

I'm not sure what you want, but I opened #2 about it.

must be extensible for the case additional information are needed (sizeof(IV), IV_MAX vs. LONG_LONG_MAX, API availability where ppport.h provides empty placeholder, ...)

Not true

I didn't say it was, but I opened #3 about it. Basic support shouldn't be too hard, but I'm not sure it is really desirable.

Is there anything else missing. You mentioned "a sane, structured cache" (I assume related to #3), but I'm not sure what you really want to achieve there.

ribasushi commented 9 years ago

Is there anything else missing.

@rehsack do you have anything to add/clarify? EU::HC is getting to a point where multiple low-level dependencies* will soon start to bundle it into inc/ (hard bundling, without using inc::latest or similar contortions, so future CPAN updates of EU::HC will intentionally remain invisible to the end-user). I would really like your input as an end-user whether EU::HC as it currently is on CPAN is missing anything critical.

* A non-exhaustive list of what is almost certainly going to switch to this mode of using EU::HC sooner rather than later (it's almost impossible that you do not package code relying on these, which is why we really need your input):