[PD-dev] Compiling externals for Windows

[Roman Haefeli]

On Tue, 2015-06-23 at 11:00 +0200, Roman Haefeli wrote:
> On Tue, 2015-06-23 at 10:04 +0200, Roman Haefeli wrote:
> > On Tue, 2015-06-23 at 09:29 +0200, IOhannes m zmoelnig wrote:
> > > the question is, why does it still try to use the old path?
> > > could it be something in the path settings?
> > > 
> > > could you do try the following?:
> > > 
> > > - start Pd
> > > - turn on the tcl prompt (Menu: Help -> Tcl prompt)
> > > - type in the tcl prompt run:
> > >     ::pdwindow::post "$::sys_staticpath\n"
> > > 
> > > and see (and tell us) what it gives you.
> > 
> > Result:
> > 
> > {C:/Program Files (x86)/Common Files/Pd} C:/Users/rhaefeli/AppData/Roaming/Pd H:/Downloads/pd_compiled/pd_compiled/extra
> > 
> > So it seems that deken just picks the first which cannot be assumed to
> > be always the correct one (fine for loading, bad for writing).

Setting line 31 to:

set ::deken::installpath  $env(USERPROFILE)

makes deken download to the correct path in W7. Can't test in Windows XP
right now.