[Bf-committers] cache python scripts for re-distribution.

[Campbell Barton]

Richard, its not that we focus on windows only - just that for *nix
packagers this is trivial since we can assume the right version of
python installed (unlike windows where we bundle python libs but no
exe).

for the pacman file see ./build_files/package_spec/pacman/PKGBUILD we have this.

  python -m compileall \
	$pkgdir/usr/share/blender/$blender_version/scripts/startup \
	$pkgdir/usr/share/blender/$blender_version/scripts/modules \
	$pkgdir/usr/share/blender/$blender_version/scripts/addons


It does bloat the packages a bit, but since Python do this I'm
guessing its accepted.

On Thu, Oct 6, 2011 at 1:32 PM, Martin Poirier <theeth at yahoo.com> wrote:
> It will be part of the windows installer, not the build process.
>
> If it's ever part of the build, for sure, it will need a switch.
>
> Martin
>
>
> ________________________________
> From: Richard Shaw <hobbes1069 at gmail.com>
> To: Martin Poirier <theeth at yahoo.com>; bf-blender developers <bf-committers at blender.org>
> Sent: Wednesday, October 5, 2011 10:02:15 PM
> Subject: Re: [Bf-committers] cache python scripts for re-distribution.
>
> On Wed, Oct 5, 2011 at 8:40 PM, Martin Poirier <theeth at yahoo.com> wrote:
>> Doing it in the installer is a perfectly acceptable solution. As you said, Python does it (as does the installers of some extensions).
>>
>> Martin
>
> Just an FYI... Right now it looks like you're only considering this
> for Windows based systems which is fine, but it ends up being
> generalized as part of the build process make sure there's a build
> flag to disable it. At least on Fedora/Redhat rpmbuild byte-compiles
> python as part of the package generation process.
>
> Thanks,
> Richard
> _______________________________________________
> Bf-committers mailing list
> Bf-committers at blender.org
> http://lists.blender.org/mailman/listinfo/bf-committers
>



-- 
- Campbell