Re: build help

On Jan 31, 2005, at 10:40 PM, Mike Richardson wrote:

> 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
>

That got me a little closer -- at least all the 'installed' files were 
in one macx directory

> 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:
>

I'm just using the 2.3.2 tarball, as advised by the website


> /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.

For some reason, rkMacPak.py does not seem to be succeeding (maybe not 
even running...). I do not get the REKALL.app directory or its subs. I 
do get the macx folder with the app and all the dylibs at the same 
directory level.

I still get rekall looking for shared libraries in the hardcoded build 
directory location. I can fix that, at least temporarily by specifying 
DYLD_LIBRARY_PATH appropriately, but then rekall starts looking for the 
gui directory in rkconfig.prefix/data!! (not even 
rkconfig.prefix/macx/data...). I can kluge this one by copying the 
macx/data directory over to the prefix directory, and rekall will 
launch. But then it always says that "This is the first time you have 
used this version" so some other directory is hardcoded, too. The help 
system launches, but is empty, reporting that helpdir=(null) and 
helpkey=(null).

As you can probably tell, I'm in desperate need of the help system 
working...

I don't need the Mac package type installation. I really would like to 
see a standard unix style installation tree unless the full package 
approach is available.

Thanks for the help. I'll keep beating on this, as it is a motivated 
learning experience for me.

Dave
--
David Reiser
[email protected]