Re: [OctDev] passing -R to mkoctfile

[Paul K. <pki...@us...>]

On Sep 10, 2004, at 12:41 AM, dan...@mc... wrote:

>
>
>> On Sep 9, 2004, at 8:03 PM, dan...@mc... wrote:
>>
>>> I'm wondering if the mkoctfile script should be extended to allow
>>> -Rpath or maybe
>>> -Wl,-Rpath to be passed on to the compiler?  I was working on
>>> something which
>>> links to a shared lib which may or may not be installed in a place
>>> where shared
>>> libs are searched for.  Without mkoctfile accepting -Rpath I end up
>>> having to
>>> set LD_LIBRARY_PATH.
>>>
>>> Basically, the -[lL] line in mkoctfile could be changed to -[lLR].
>>>
>>> Thoughts?
>>>
>>> -Dan
>>
>>
>
> On Fri, Sep 10, 2004 at 12:15:07AM -0400, Paul Kienzle wrote:
>> You should also be able to do something like:
>>
>> 	RLD_FLAG="-Rpath" mkoctfile ...
>>
>> or if you already have some rpath,
>>
>> 	RLD_FLAG="`mkoctfile -p RLD_FLAG`:path" mkoctfile ...
>>
>> - Paul
>>
>
> RLD_FLAG is only used if --link-stand-alone is specified (at least in 
> octave-2.1.57
> which is what I have installed).

So it is.  How about the same trick with DL_LDFLAGS then?

I agree with your earlier point, though, that it would be nice to be 
able
to pass flags directly to the compiler.  How about if mkoctfile blindly
gathers all flags it doesn't otherwise understand and passes them
through to the compiler?  That should be easy enough to write.

- Paul