[PD-dev] path issues (was: Re: [import] doesn't seem to add pathes)

Hans-Christoph Steiner hans at eds.org
Tue Mar 18 20:06:31 CET 2008


It was coded that way.  You can see the code in question here, look  
for INSTALL_PREFIX:

http://pure-data.svn.sourceforge.net/viewvc/pure-data/trunk/pd/src/ 
s_main.c

I am sure that if someone wrote a patch, it would be accepted.

.hc

On Mar 18, 2008, at 6:59 AM, Roman Haefeli wrote:

> yo.. actually my bug report was bogus, because it was not related to
> [import], but to how pd works on linux. it seems, that this bug was
> closed in the tracker, but some 'unpleasant aftertaste' remains.
>
> why are all pathes hard-coded into pd on linux, while they aren't on
> windows? correct me, if this is wrong, but i made this conclusion by
> using [import] and [declare], when running pd from a non-standard  
> (i.e.
> not the location where pd was compiled for) location on linux. using
> [declare -sdtpath] in a patch opened in a pd-extended install, which i
> extracted to my home directory, added a path from
>
> /usr/local/lib/pd/ (the standard pd install path)
>
>  and not from
>
> /home/roman/pd-extended/usr/local/lib/pd/
>
> as i would have expected, because i installed it there (extracted from
> a .deb-package to this place, because i wanted to avoid conflicts with
> my existing pd installation)
>
> on windows the situation is totally different: i can extract pd or
> pd-extended, i can put it to any location and [declare -stdpath] seems
> to always work the same way and adds pathes from
>
> <current_location_of_pd>/
>
> why this difference? why are pathes in pd for windows relative to the
> current location of pd and in linux hardcoded to the prefix used
> at ./configure time? why doesn't pd on linux use relative pathes as
> well?
>
> the way it is handled on windows is much more flexible in my  
> opinion and
> allows to create packages, that can be put anywhere and just run.
>
> roman
>
> On Mon, 2008-03-17 at 15:22 -0700, SourceForge.net wrote:
>> Bugs item #1912314, was opened at 2008-03-11 20:24
>> Message generated for change (Comment added) made by eighthave
>> You can respond by visiting:
>> https://sourceforge.net/tracker/? 
>> func=detail&atid=478070&aid=1912314&group_id=55736
>>
>> Please note that this message will contain a full copy of the  
>> comment thread,
>> including the initial issue submission, for this request,
>> not just the latest update.
>> Category: pd-extended
>> Group: None
>>> Status: Closed
>>> Resolution: Invalid
>> Priority: 5
>> Private: No
>> Submitted By: Roman Haefeli (reduzent)
>> Assigned to: Hans-Christoph Steiner (eighthave)
>> Summary: [import] doesn't seem to add pathes
>>
>> Initial Comment:
>> tested with:
>> Pd version 0.40.3-extended-20080308
>>
>> which is installed in:
>> /home/roman/pd-extended-0.40/usr/local/bin/pd
>> (don't know if this infor useful. i think i should mention it,  
>> because usually it is installed in /usr/local/bin/pd)
>>
>> [import iemmatrix] prints:
>> [import] loaded library: iemmatrix
>>
>>
>> however, when i load this patch:
>> ----
>> [import iemmatrix]
>>
>> [matrix]
>> -----
>> [matrix] doesn't get instantiated, but outputs the error:
>>
>> matrix
>> ... couldn't create
>>
>> instantiating [iemmatrix/matrix] works fine, though.
>>
>>
>> also this patch loads fine:
>> -------
>> [declare -stdpath extra/iemmatrix]
>>
>> [matrix]
>> -------
>>
>> i tested the same with 'tof' and [destroysend] from the library  
>> 'tof' and got similar results.
>>
>>
>>
>>
>>
>> --------------------------------------------------------------------- 
>> -
>>
>>> Comment By: Hans-Christoph Steiner (eighthave)
>> Date: 2008-03-17 18:22
>>
>> Message:
>> Logged In: YES
>> user_id=27104
>> Originator: NO
>>
>> caused by custom install location on GNU/Linux
>>
>> --------------------------------------------------------------------- 
>> -
>>
>> Comment By: Roman Haefeli (reduzent)
>> Date: 2008-03-11 21:38
>>
>> Message:
>> Logged In: YES
>> user_id=1895440
>> Originator: YES
>>
>> it turned out, that this behaviour is indeed related to the non- 
>> standard
>> install location. it also turned out, that on linux several things  
>> in pd
>> won't work as expexted, if pd is _not_ installed in the directory,  
>> where it
>> was compiled for (unlike windows, where pd can be put to an  
>> arbitrary place
>> while still everything works fine).
>>
>> sorry for the noise and bogus bug report
>>
>>
>>
>> --------------------------------------------------------------------- 
>> -
>>
>> You can respond by visiting:
>> https://sourceforge.net/tracker/? 
>> func=detail&atid=478070&aid=1912314&group_id=55736
>>
>> _______________________________________________
>> PD-dev mailing list
>> PD-dev at iem.at
>> http://lists.puredata.info/listinfo/pd-dev
>
>
> 	
> 		
> ___________________________________________________________
> Der frühe Vogel fängt den Wurm. Hier gelangen Sie zum neuen Yahoo!  
> Mail: http://mail.yahoo.de
>
>
> _______________________________________________
> PD-dev mailing list
> PD-dev at iem.at
> http://lists.puredata.info/listinfo/pd-dev



------------------------------------------------------------------------ 
----

As we enjoy great advantages from inventions of others, we should be  
glad of an opportunity to serve others by any invention of ours; and  
this we should do freely and generously.         - Benjamin Franklin






More information about the Pd-dev mailing list