Re: build help

On Friday 28 January 2005 21:23, David Reiser wrote:
> I've been trying to build 2.3.2 against a fink installed Qt3.3.3 on my
> mac. I did get make to run, but make install was a disaster at first.
> Now rekall is looking for its first shared library in 'ports/qt3/xxx'.
> Ack.

"make install" on the mac won't do what you think it will!

It only does a "pretend" install: if you do

DESTDIR=`pwd`/ make install

then it should (plus-or-minus CVS being the latest - can't commit at the 
moment, i'm in the middle of a major hack :) then you'll get a tree under
a directory 'macx' which looks like a MAC package tree. You can then run it:

/Users/....../Rekall/Rekall.app/Contents/MacOS/rekall

and it should find the libraries and what-not, but there is no support to 
actually build a mac package.

Mike

>
> I'm guessing that I didn't get something specified quite right. Fink
> studiously avoids installing anything in /usr, so it uses /sw as its
> base. I figured I'd try to keep from fouling up /sw by using
> prefix=/opt.  Something is clearly not working correctly. I'm pretty
> sure I didn't "get this right" when attempting to enter:
>
> KDEDIR=/xxx make config
>
> My default shell is tcsh, which didn't like any form of that command I
> could think of, and since I was building a QT version, and QTDIR
> already existed in my enviroment list, I just did "make config". Now
> that I've learned a bit more about tcsh and bash, I tried switching to
> bash and entering KDEDIR=/opt make config. It runs, but I can see
> absolutely no difference in the rkConfig.py file, so I'm concerned that
> something is still amiss. Should it be KDEDIR=/opt (where I'm expecting
> make install to put the rekall files) or should it be KDEDIR=/sw (where
> all the QT related files are)? Or should it be something else?
>
> Is it normal to have all the intermediate compile files put in the
> source directories? Is there a simple recursive rm I can use to clean
> out the source tree before I try another 'make'?
>
> I'd really like to see rekall be available as a fink maintained source
> distribution. After all, no matter how much you make it look like a
> normal Mac app in the Finder, once it's launched, what you see is Qt's
> interface. I think the only difference between most fink installed
> sources and the Linux versions is having to force the dynamic library
> generation. There are always some details, but even gnucash (with a
> huge dependency list and a gnome 1.4 interface) works well after a fink
> install. You can even create a Finder icon that will launch X and then
> gnucash -- I never use it because I want to see any messages that get
> sent to the X console, but plenty of folks just treat that icon as the
> gnucash app. Gnucash does some of the mac specific library generation
> forcing in it's config file, but the gnucash.info (fink distribution
> element) also edits libtool on the fly to tweak the files in the Linux
> tarball.
>
> I did change several things in the rkBuilder.py file to eliminate
> errors from both make and make install. My goal at the moment is to
> mimic a Linux /opt installation. I got at least as far as getting make
> to run and make install to put all the files where I'm expecting them
> in /opt/lib opt/bin opt/share etc. But rekall still looks for
> libkbase_kde.dylib in 'ports/qt3/'.
>
> My first make install used the rkBuilder.py default of instDir='macx'
> -- the disaster being that I had 20+ macx directories spread all over
> the source tree because rkBuilder effective told the system to ignore
> rkConfig.prefix.
>
> So far I've only run one completed make. The rest of my efforts have
> been at getting install to target the right directories. The targeting
> seems to be working, but I must have a build issue.
>
> Any suggestions?
>
> Thanks.
>
> Dave
> --
> David Reiser
> [email protected]
>
> _______________________________________________
> Rekall-devel mailing list
> [email protected]
> http://www.mailman.a-i-s.co.uk/cgi-bin/mailman/listinfo/rekall-devel