Re: [Playerstage-developers] /opt/local

[Brian G. <br...@ge...>]

On Jan 26, 2009, at 5:32 PM, gbiggs wrote:

> If everyone on OS X will have to set it, then it's vital (at least  
> until
> MacPorts and/or CMake sort themselves out). I'll add it to the scripts
> as a default path under OS X today. I don't have an OS X computer so I
> can't test it myself, though.

Oh, I was suggesting that it's out of scope for our build system, and  
rather that we should be assuming that the user has already set those  
variables accordingly.

	brian.

> Brian Gerkey wrote:
>> On Jan 26, 2009, at 5:12 PM, gbiggs wrote:
>>
>>> Scattered entries for this path recently appeared in a few of the
>>> CMakeLists.txt files. I gather it's for OSX, but what  
>>> specifically? If
>>> it's not vital for OSX (e.g. it's for a library installed from  
>>> source
>>> rather than the usual method) it should be set in the
>>> PLAYER_EXTRA_INCLUDE_DIRS and PLAYER_EXTRA_LIB_DIRS advanced
>>> options. If
>>> it's vital for OSX (or other platforms), there are more portable
>>> ways to
>>> set it that I can add, if someone lets me know where it's necessary.
>>
>> On OS X, MacPorts installs things into /opt/local.  But I would argue
>> that a proper MacPorts installation has CPATH, LIBRARY_PATH,
>> DYLD_LIBRARY_PATH, PKG_CONFIG_PATH, and friends modified to point
>> into /opt/local, so that nobody need ever refer to it directly.
>>
>> 	brian.
>
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by:
> SourcForge Community
> SourceForge wants to tell your story.
> http://p.sf.net/sfu/sf-spreadtheword
> _______________________________________________
> Playerstage-developers mailing list
> Pla...@li...
> https://lists.sourceforge.net/lists/listinfo/playerstage-developers