From: Keith M. <kei...@to...> - 2005-11-02 09:24:27
|
Maxim Ulrich wrote: > With installing I meant that I have put the library and the > corresponding header files into my lib and include folders. > Keith has pointed out that nag c library for GNU needs a true > Linux environment. The minimal system of MinGW is not sufficient. That isn't strictly true, nor is it quite what I said. MinGW+MSYS brings a minimal Linux-like system to the Win32 platform. It's goal is to provide a framework for building Win32 versions of many Open Source applications, which are typically targetted at UNIX/Linux platforms, but its value actually transcends that. What I *did* say is that you cannot simply copy a Linux binary library to a Win32 box, and expect MinGW to link against it -- that simply will not work. However, if you can build, or obtain a ready built Win32 version of that library, preferably one built with MinGW itself, then you may be able to use it with MinGW. Since NAG C is a commercially distributed binary library, building it yourself, from source, is unlikely to be a viable option. However, NAG do offer prebuilt binary versions for Win32, either as static or as shared (DLL) libraries, with bindings for MS-Visual-C/C++, or for Borland-C/C++. Their web site suggests that the MS-Visual-C/C++ DLL can be used with CygWin, so it *may* also be possible to use it with MinGW; YMMV, depending on the function binding employed -- functions with a plain C binding may work, those with C++ binding are unlikely to do so. In any event, since NAG C is a commercially distributed product, this list is not the appropriate forum for supporting it. You've paid for it, so you can rightfully expect support from the vendor, or from NAG themselves. That is where you need to ask such questions. Regards, Keith. |