[Bf-committers] Os X platform managing

[Jasper Mine]

I have tried compiling them myself.  When compiling blender it=20
sometimes likes them, sometimes not.  Which leads me to believe the=20
pre-compiled libs were blenderized in some way.  It would be nice if=20
the source was present for these libs, like they are with solid etc. =20
Then only having to edit a few make file for individual systems.  Of=20
course this requires humans, and I am without time to do that for osx.

On May 5, 2004, at 10:13 AM, Martin Poirier wrote:

> Distributing precompiled libs doesn't disable people
> from compiling it themselves you know.
>
> --- Jasper Mine <jaspermine@earthlink.net> wrote:
>> In addition, what about those people testing
>> optimization for different
>> powerpc CPUs, pre-compiled would not be nice for
>> these.
>>
>>
>> On May 5, 2004, at 9:56 AM, Jasper Mine wrote:
>>
>>> Not to be an ass, but I think it would be nice if
>> all the required
>>> libraries could be moved into fink.  But I also
>> see the benefit of
>>> having them static/unchanged/and included.
>>>
>>> Also I think its a bad idea to have users mess
>> with the X11R6, this
>>> directory could very well change next October when
>> OSX Tiger is
>>> released.  And the make system somehow finds the
>> correct ttl font from
>>> 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
>>>>> /usr/x11R6.
>>>>>
>>>>> When building the release, I had the problem of
>> having one
>>>>> (freetype) correctly named but of the wrong
>> version in X11R6. This
>>>>> resulted in drawing bug. Having one set of
>> correct libs available as
>>>>> separate download would insure that even the not
>> too experienced but
>>>>> curious could build from source.
>>>>>
>>>>> Then when finally installing the good one (from
>> another location on
>>>>> the disk), the angry god of paths lib make sure
>> that gcc pick up
>>>>> another wrong one.
>>>>> I solved this by putting all external libs (or a
>> link) in the lib
>>>>> tree and reducing the path lib to only that and
>> system. As the libs
>>>>> go in a separate tree in CVS, there is no
>> drawback for the
>>>>> experienced coders.
>>>>
>>>> My vote goes also for including all libs that
>> blender uses and that
>>>> are not part of a default OS X installation
>> should go into the lib
>>>> tree in CVS in precompiled form.
>>>>
>>>> IMHO it should be able to to build blender
>> without any additional
>>>> 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
>>>>
>>>
>>> _______________________________________________
>>> 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
>
>
>
> =09
> 	=09
> __________________________________
> Do you Yahoo!?
> Win a $20,000 Career Makeover at Yahoo! HotJobs
> http://hotjobs.sweepstakes.yahoo.com/careermakeover
> _______________________________________________
> Bf-committers mailing list
> Bf-committers@blender.org
> http://www.blender.org/mailman/listinfo/bf-committers
>