> Hi Alexander,
>
> do you plan to implement MAKE_JOBS_SAFE for bsd.scons.mk as well?
> I wonder if just adding _MAKE_JOBS to SCONS_ENV would be enough since -j
> is also supported for scons.
>
That should be enough. scons supports -j.
Alex
___
freebsd
This is just a quick message to note that we have made Python 2.5.1 the default
Python version in the FreeBSD ports collection as of about a minute ago.
This change also included a considerable amount of work to make support for
Python Eggs more useable in the Ports collection, by provoiding a fe
ally
provide a sutible build system replacement, just a suitable make replacement.
Waf is an interesting project [1] if you're interested in seeing SCons done
better.
Alex
1 http://freehackers.org/~tnagy/bksys.html
>
> Tz-Huan
>
> On 11/29/06, Alexander Botero-Lowry <[EMAIL PRO
> Alex, thanks for your reply. stiv @ blender forums pointed me to the
> sixth paragraph in the SCons' manual:
>
> "scons does not automatically propagate the external environment used to
> execute scons to the commands used to build target files. This is so
> that builds will be guaranteed rep
> I'm trying to make a port of the latest Blender with the SCons build.
> The scons command in the do-build target in bsd.scons.mk is expanded in:
Yes, I've had this lovely discussion before. Blender has gone through many
iterations of bad scons behavior, at one point it used to split the args so
we welcome
any committers or submitters interested in helping out with Python
ports!
Hye-Shik Chang (perky@) and Alexander Botero-Lowry (alexbl@)
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubsc
>
> Hi,
>
> Python 2.5 seems to install automatically generated egg-info files for
> each package. This causes each port, which installs files into
> the site-packages directory to leave files around:
>
> For devel/pygame this would be pygame-1.7.1release-py2.5.egg-info.
> For x11-toolkits/py-tk
> Le Lun 25 sep 06 à 11:21:11 +0200, Alexander Zhuravlev
> écrivait :
>> So, how can I determine the fact that the port was compiled with such
>> option, so I can rise an error in my port or compile it with bundled
>> sqlite 3.2 library?
>> Any help will be much appreciated.
>
This is the exact