On 08/23/2010 05:45 PM, Jonathan MERCIER wrote:
The only reason why i use _d_libdir si for ldc scan d library (only)
But we can put all D lib in libdir
see:
_________________________________________________________________________________
$ cat /etc/ldc.conf
// This configuration file uses libconfig.
// See
http://www.hyperrealm.com/libconfig/ for syntax details.
// Special macros:
// %%ldcbinarypath%%
// - is replaced with the path to the directory holding the ldc
executable
// The default group is required
default:
{
// 'switches' holds array of string that are appends to the command
line
// arguments before they are parsed.
switches = [
"-I /usr/include/d/",
"-I /usr/include/d/tango",
"-I /usr/include/d/tango/core/vendor",
"-L-L/usr/lib64/d",
"-d-version=Tango",
"-defaultlib=tango",
"-debuglib=tango"
];
};
Seems pretty pointless. How painful would it be to have it simply put
the libraries in %{_libdir} and never pass any -L?
Will all D packages need to be patched to support this? Are they
hardcoded to expect /usr/lib64/d ?
~spot