Re: [Octaviz-help] octaviz on Mac OS X

[Jonathan S. <jjs...@vc...>]

Thomas Weber wrote:
> Am Freitag, den 05.10.2007, 08:16 -0600 schrieb Jonathan Stickel:
>> Thomas Weber wrote:
>>> Am Donnerstag, den 04.10.2007, 07:55 -0600 schrieb Jonathan Stickel:
>>>> Dragan and Thomas
>>>>
>>>> OK, I finally managed to get octaviz installed on my Mac.  It required a
>>>> few hacks to make files _post cmake_.  I detail the issues below so
>>>> that we can try to resolve them at the cmake step.  For the record, I 
>>>> installed octave and VTK via Fink.
>>>>
>>>> Are you subscribed to the octaviz-help mailing list?  If so, I will not 
>>>> cc you in future emails about this.
>>> I did subscribe now. I wasn't aware there's a help mailing list.
>>>
>>> First question: did you use current CVS for building?
>> Yes.  Since I had the some of the issues with the modified build system 
>> that you sent me, I decided to work with what is currently in CVS.
> 
> 
>> OK.  If we get the others resolved, maybe we can do something like "if 
>> mac os x, exclude building the problem libraries" in CMakeLists.txt. 
>> The only one that might be missed is TIFFwriter.
> Might be an option.
> 
> 
>>>> Problem 2:
>>>> Linking of libraries does not work automatically.  As a workaround, I added
>>>>
>>>> -L/sw/lib/octave-2.9.14 -loctinterp -loctave -lcruft -lvtkCommon
>>> Can you post the mkoctfile script? 
>>>
>> Do you mean the link.txt file?  It is attached.
> 
> No, the mkoctfile script that ships with Octave. It should be a normal
> shell script.
> 

OK, it is attached.

> 
>>>> to Common/CMakeFiles/octaviz.dir/link.txt.  I notice that the equivalent 
>>>> flags are not included or needed when compiling in Linux.  Nonetheless, 
>>>> it shouldn't hurt to add them universally.  Can you help me make changes 
>>>> to the appropriate CMakeLists.txt file to add these?
>>> What does 
>>> 	$ objdump -p /usr/bin/octave-2.9.14
>>> say? This will only give meaningful results if the file is a binary.
>>> Under Linux, the binary is compiled with an rpath that points
>>> to /usr/lib/octave-2.9.14, so the octave binary 'knows' where its
>>> symbols are.
>>>
>> I don't seem to have the objdump command.  What package is it typically 
>> included with?
> 
> binutils
> Though it might be linux-specific. 
> 

I only get this for output:

   $ objdump -p /sw/bin/octave-2.9.14

/sw/bin/octave-2.9.14:     file format mach-o-le


> 
> I'm short on time right now, though I'll check my e-mails over the
> weekend.
> 

No problem.  I do have octaviz working at the moment.  We can take our
time resolving these issues so that others can build on Mac.

Thanks,
Jonathan