On 10/7/2018 10:32 AM, Martin Storsjö wrote: > On Sun, 7 Oct 2018, Jacek Caban wrote: >> On 05/10/2018 23:02, Martin Storsjö wrote: >> >> It seems tempting to use just standard --includedir here, but >> I couldn't find a way to change its default value (we'd need >> to default to $prefix/$host/include instead of >> $prefix/include). Unless someone knowing autoconf better >> knows how to achieve that, I'm fine with >> --with-widl-includedir. > > That's tempting, although it semantically is different. In a full > canadian cross with distinct build/host/target, the normal --includedir > is for headers that belong to the tool/library currently being built, > for host, not target. As widl doesn't install headers, it's unused, so > reusing it wouldn't be that bad.
Sorry but I disagree strongly so just had to intervene here. The misuse of a long standing switch is *bad*. Someone would come along expecting it to work as it does everywhere else. Please let this be the last consideration of the misuse of `--includedir`. -- Earnie _______________________________________________ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
