Re: [Lapackpp-devel] lapack++ for msys/windows xp
Status: Beta
Brought to you by:
cstim
From: Christian S. <sti...@tu...> - 2006-04-09 10:27:34
|
Hi, Am Sonntag, 9. April 2006 04:38 schrieb Andrew Oh: > Hey, I'm new to UNIX so I apologize in advance if my questions seem stupid. no problem. That's what this mailing list is for. > I installed the windows lapack++ file "lapackpp-2.4.7-setup.exe" into > C:\msys\1.0\lib\lapackpp. I copy and pasted all the header files as > well as the "liblapack32.dll" (the shared library) into > C:\msys\1.0\mingw\include\lapackpp > > To compile my program, I type in: > >>g++ program.cpp -IC:/msys/1.0\mingw/include/lapackpp > >>-LC:/msys/1.0\mingw/include/lapackpp -llapackpp > > The first argument with -I is for the header file location, the second > argument with -L is for the location of "liblapackpp.dll", and the > third argument with -l is for lapackpp. Right. Correct so far. > The program doesn't compile and I don't know what is wrong. I get > > >>C:\msys\1.0\mingw\bin\..\lib\gcc-lib\mingw32\3.2.3\..\..\..\..\mingw32\bi > >>n\ld.exe: > > cannot >>find -llapackpp Oh, sorry. My directions in the README were not completely correct. > I believe that I installed the header files correctly Yes. If that were a problem, you would have gotten error messages like "lapackpp.h: file not found". > but I'm not sure if I handled the "liblapackpp.dll" correctly. Yes. Sorry, my directions were incorrect; if the DLL is called liblapackpp32.dll, you need to write "-llapackpp32" in the compiler command i.e. the file name of the DLL without the leading "lib" and without the trailing ".dll" but everything in between. > Also, I do not know > anything about the "library itself"... namely lapackpp. I have no yet > encountered a "lapackpp.lib" or anything of that sort. The compiler "gcc" doesn't need a ".lib" library anymore. For gcc, it is sufficient to only have the ".dll" file available. The ".lib" is something which was needed for MSVC. (By the way, the source package "lapackpp-2.4.7.tar.gz" also includes a project file if you want to build the library on your own in MSVC; we cannot distribute a pre-compiled DLL for MSVC due to licensing restrictions.) > Also, one last thing I'm worried about is your README for the windows > installation. It mentions entering into the UNIX command line > > ./configure --prefix=/directory/ > make > make install > > Do I really need to worry about this? No. That is applicable only if you want to compile lapackpp32.dll yourself. > Or is just executing > 'lapackpp-2.4.7-setup.exe' enough to set everything up? Yes. Regards, Christian |