acril <[EMAIL PROTECTED]> writes: >> >> Hi! Can you be more specific, I can't seem to be able to verify that: >> > > Here's the output from grep: > > bin/libgnutls-config:3:prefix=/home/jas/gnutls4win/inst ...
Ah, right. There are three categories of files which includes these paths: 1) DLL's and EXE's. This is probably because of debugging symbols, and those are useful. Perhaps we could have two installers, one with debugging symbols and one without. Although that is more work for me. Having optional *.gdb files with the debugging symbols may be the proper solution, but I don't know how to do that, and whether it works under mingw32. Thoughts and help here appreciated. 2) The *-config scripts. These are shell-scripts, and they are deprecated. I've removed them from gnutls.nsi. Come to think of it, maybe we should finally remove them from the real package too... 3) The *.la files. These are generated by libtool. I'm not sure they are ever useful, especially on the installed machine where the installed prefix will differ from those encoded in libtool. However, they are only installed if 'Developer libraries' was selected in the installer. That happens to be the default, and perhaps that isn't necessary. Although right now, I suspect most people installing GnuTLS for Windows are developers. /Simon _______________________________________________ Help-gnutls mailing list [email protected] http://lists.gnu.org/mailman/listinfo/help-gnutls
