[Ffts-develop] Re: libCommon
Status: Planning
Brought to you by:
mghiggins
|
From: Mark H. <mgh...@ya...> - 2001-05-18 03:40:18
|
> I've had some problems making 0.5. One I fixed, the other I > need help > > 1. MakeVars refers to a libCommon ( -lCommon ) which gave me > series of ld > errors because it wasn't in my tarball. That I fixed by > removing it from > MakeVars. This is the source of problem (2), I'm afraid - you need to have libCommon in there. How are you building the FFTS? libCommon should get built before you need it for anything. You should do the following, in this order: 1) Extract the FFTS code into some directory. I'll call it /home/FFTS, but it can be whatever you want. 2) Set the environment variable FFTS_DEV_DIR to the directory you extracted the FFTS code, like export FFTS_DEV_DIR=/home/FFTS in bash. 3) Change to $FFTS_DEV_DIR and do the following: source FFTS_Setup ./MakeAll This should build a bunch of projects, and eventually build the "common" project. Poke around in the MakeAll script to see what it's doing (it's just command-line bash). Really, it should use the standard configure / make / make install, but I haven't set it up yet, so it's a bit non-standard. You shouldn't have to remove anything from MakeVars; in fact, if you do, you'll just run into linking problems, since a lot of the projects are needed for the applications (ReportBlotter was the one you had in your example, I think). ===== ------------------------------------------------------- Mark Higgins, mgh...@ya... http://www.molala.net Opinions expressed herein do not reflect my own views; I haven't had free will since last year when aliens ate my brain. __________________________________________________ Do You Yahoo!? Yahoo! Auctions - buy the things you want at great prices http://auctions.yahoo.com/ |