to conclude this tedious topic I better give an update for those who dont read the logs. Discussed this with Brect (over lunch) and Martin (over IRC) and Both agree this is best in the long run.
Now the default scons behavior is to remove the install dir each time so it always contains an up to date build, however Aligorith uses scons for development on windows, which needs DLL's etc, so copying each time isnt nice. For this case I added WITHOUT_BF_OVERWRITE_INSTALL This also brought up the issue that on windows there isnt a ~/.blender directory thats easy to access/create (I'm not clear on the details). Would be good to have a home dir on windows too but thats another topic. On Thu, Feb 11, 2010 at 1:51 PM, Brecht Van Lommel <bre...@blender.org> wrote: > Hi, > > I don't think we should try to support people installing scripts there > and try to make the build systems clever about this. These really are > just standard building rules, don't work in directories or files that > are autogenerated by the build system because any changes will get > overwritten. If anyone wants to make this kind of unsupported usage > more convenient I guess they can, but more important in my opinion is > fixing the problem of outdated scripts, and getting loading scripts > from the user directory to work properly. > > Loading from the user directory seems to be suboptimal on Windows > right now, the expected directory is this. > C:\Documents and Settings\User\.blender\scripts > > That can be changed to this, and the folder can be created > automatically on startup to make things easier. > C:\Documents and Settings\User\Blender Foundation\Blender\scripts > > Brecht. > _______________________________________________ > Bf-committers mailing list > Bf-committers@blender.org > http://lists.blender.org/mailman/listinfo/bf-committers > -- - Campbell _______________________________________________ Bf-committers mailing list Bf-committers@blender.org http://lists.blender.org/mailman/listinfo/bf-committers