[Bf-committers] Os X platform managing

Jasper Mine bf-committers@blender.org
Wed, 5 May 2004 09:56:45 -0400

Not to be an ass, but I think it would be nice if all the required=20
libraries could be moved into fink.  But I also see the benefit of=20
having them static/unchanged/and included.

Also I think its a bad idea to have users mess with the X11R6, this=20
directory could very well change next October when OSX Tiger is=20
released.  And the make system somehow finds the correct ttl font from=20=

somewhere in blender source, ditch the scons.

On May 5, 2004, at 9:48 AM, Christian Plessl wrote:

> On 04.05.2004, at 21:20 Uhr, Jean-Luc Peuri=E8re wrote:
>> I speak of the libs which must be separately installed in /sw or=20
>> /usr/x11R6.
>> When building the release, I had the problem of having one (freetype)=20=

>> correctly named but of the wrong version in X11R6. This resulted in=20=

>> drawing bug. Having one set of correct libs available as separate=20
>> download would insure that even the not too experienced but curious=20=

>> could build from source.
>> Then when finally installing the good one (from another location on=20=

>> the disk), the angry god of paths lib make sure that gcc pick up=20
>> another wrong one.
>> I solved this by putting all external libs (or a link) in the lib=20
>> tree and reducing the path lib to only that and system. As the libs=20=

>> go in a separate tree in CVS, there is no drawback for the=20
>> experienced coders.
> My vote goes also for including all libs that blender uses and that=20
> are not part of a default OS X installation should go into the lib=20
> tree in CVS in precompiled form.
> IMHO it should be able to to build blender without any additional=20
> installation of libraries via fink/darwinports etc.
> Regards,
>  Christian
> _______________________________________________
> Bf-committers mailing list
> Bf-committers@blender.org
> http://www.blender.org/mailman/listinfo/bf-committers