[Bf-committers] library installation issues (was irix..)

[Ton Roosendaal]

Hi,

As far as I understand this discussion, we have to pin down a few  
requirements for how Blender runs, and how you can code for it. This  
can be put in a table, describing the situation for each OS version.

As functional (general) requirements I propose:

--------BLENDER USERS
- Users only have to unpack the download file, and should be able to  
run immediately without root access to a system. We provide a simple  
checklist for them to detect the minimum requirements of their system.
- installation files for Blender - whether libs or data - always reside  
either in the installation directory, or in $HOME/.blender/. Unless the  
OS itself has other conventions for it.
- an additional (optional) installer only takes care of  
upacking/removing Blender and integration with a desktop system, like  
icons and filetype assignments. Installers do not overwrite libraries!

--------BLENDER DEVELOPERS
- Blender coders can be assumed to have root access to their system,  
but required installation of system tools will be restricted to 'make',  
gcc, etc. A shortlist for that - including minimum versions - will be  
provided.
- A distinction is made between 'system' libraries, and 'external  
Blender' libraries. The first catagory is libc etc. but also includes  
OpenGL, the second is part of the CVS lib checkout; including python,  
freetype, openal, etc etc.
- manually, a developer can force linking to 'external Blender' libs at  
other locations.
- for a release, 'system' libraries will be linked dynamically,  
'external Blender' libraries static. Unless the OS doesn't provide  
that...

Please comment, or add to it!
I want to update the blender/doc/building_blender.html text with this  
info.


-Ton-


On Sunday, May 11, 2003, at 23:09 Europe/Amsterdam, John K. Walton  
wrote:

>
> yeah, i know but....
>
> "The -r option may also be used to install software somewhere other
> than the default location.  However, by changing the effective root
> directory, the normal installation history database in /var/inst
> will not be used, and inst may not be able to to correctly resolve
> prerequisite conflicts.  Therefore when attempting to manage disk
> space, it is usually preferable to avoid using the -r option, and
> instead create a symbolic link from the system disk to an option
> drive before running inst or Software Manager."
>
> it sucks :-)
> thanks!
>
>>
>> inst can be used as a regular user to do local installations
>> too with the -r (target) flag, e.g.,
>>
>> inst -r /usr/people/cwant/upyoursboss
>>
>> will install everything in that subdirectory
>> (creating tmp, usr, var subdirectories as needed).
>>
>> For dynamic lib resolution, the user would want
>> to do something like this:
>>
>> setenv LD_LIBRARYN32_PATH  
>> /usr/people/cwant/upyoursboss/usr/freeware/lib32
>>
>> Chris
>>
>> _______________________________________________
>> Bf-committers mailing list
>> Bf-committers@blender.org
>> http://www.blender.org/mailman/listinfo/bf-committers
>>
>
> _______________________________________________
> Bf-committers mailing list
> Bf-committers@blender.org
> http://www.blender.org/mailman/listinfo/bf-committers
>
>
------------------------------------------------------------------------ 
--
Ton Roosendaal  Blender Foundation ton@blender.org