Andy Wingo writes: >> (arguments `(#:configure-flags >> (list (string-append "LDFLAGS=-Wl,-rpath -Wl," >> (assoc-ref %build-inputs "ncurses") >> - "/lib") >> + ,(if (mingw-target?) "/bin" "/lib")) > > Is there a reason for MinGW ncurses to put its library in /bin on a > MinGW system? Better if it put it in /lib like everything else...
Yes...ncurses does not create any .la-files; only .dll-files. Sadly those must go in bin. Maybe we could add a workaround in ncurses, adding symlinks of those dlls in lib... This bothered me too and the real solution here is to (cross) build ncurses using libtool. The good news is that ncurses can optionally be built with libtool. The bad news is that because the ncurses build system takes an installed version of libtool instead of generating one during configuring as usual, cross building ncurses with libtool needs an installed pre-build cross version of libtool. WDYT? Greetings, Jan -- Jan Nieuwenhuizen <jann...@gnu.org> | GNU LilyPond http://lilypond.org Freelance IT http://JoyofSource.com | Avatar® http://AvatarAcademy.nl
