"Hoyt, David" hoyt6@llnl.gov writes:
I'm unsure what the general solution for Windows is. But executables that are built that rely on the shared libraries cannot run if the dll's aren't either in the system path or in the same directory as the executable.
I guess the solution closest to the gnu conventions would be to install the dll (and the dll.a?) in the "system path".
It might make some sense to install it in the same directory as the few nettle executables, but that won't solve everything. E.g., with regards to gnutls, you'd need the nettle dll located in the same directory as the gnutls executable, which nettle doesn't know about; it may or may not be the same directory as nettle's $bindir. So you'd probably need to copy it around anyway.
A related question is how to run the testsuite using the4 shared libraries; do you need to copy the dlls into the subdirectories with executables which are run by the testsuite, or is there anything analogous to LD_LIBRARY_PATH (which is used for running the testsuite with ELF shared libraries).
Can you run autoconf natively?
Yeah, I can run it natively.
Ok, that makes hacking on configure.ac a lot easier.
I use activestate perl (for now). When the msys guys come out w/ a newer build of perl, I'll try that out, though. But I haven't ever tried to build autoconf itself w/ msys.
When I tried it, autoconf seemed to not be included in the msys installation. But I don't remember much of the details.
Regards, /Niels