Re: [MiNT] AHCC V4.11

[Paul Wratt <paul.wratt@gmail.com>]

I have commented on this issue in the past too.. (about 2-3 years ago now)

the same issue happen when compiling a project, where the includes are
not found, due to FS. In that particular case the solution is simple:
1) check include literal
2) check include lowercase
3) check include uppercase
4) only fail if all of the above fail

As for the Fileselector issue, can it not be easily solved by
providing a default external fileselector (if one is not found
installed), as MyAES does..

Paul

On Sat, Jun 2, 2012 at 8:59 AM, Jo Even Skarstein <joska@online.no> wrote:
> On Fri, 2012-06-01 at 00:12 +0200, Henk Robbers wrote:
>
>> It might be interesting to know that AHCC makes extensive use of Dpathconf.
>> But of course only when the location of a target is determined.
>> Which is not the case when a user uses a fileselector to find
>> a file with a certain extension.
>
> You are of course completely right. Basically this is an unsolvable
> problem with today's fileselectors.
>
> Jo Even
>
>
>