On Jul 28, 2008, at 3:06 PM, Michael Barton wrote:
I never got a clarification from Michael (or I missed it) if -L/usr/
lib was in his link command for NVIZ. That would have confused the
linking, if it was before the tcltk -L flag.
Hi,
I never messed with anything in platform.make except f
On Jul 28, 2008, at 8:35 AM, William Kyngesburye wrote:
On Jul 28, 2008, at 9:34 AM, Glynn Clements wrote:
We needed the -framework flags because -l would get the system tcltk
symlinks.
Er, not if you also use -L, surely?
I never got a clarification from Michael (or I missed it) if -L/usr/
On Wednesday 23 July 2008, Glynn Clements wrote:
> Hamish wrote:
> > > I have added a new module, r.grow.distance, which generates a map
> > > where the value of each cell is the distance to the nearest non-null
> > > cell in the input map (similar to r.cost with a constant cost, except
> > > that
Hello All - I have a question about the v.rast.stats script. I want to maintain
a MASK for the process in order to isolate portions of the raster and attaching
those stats to the vector table. In the script, any user defined mask is
temporarily renamed, but I don't see a place in the script whe
On Jul 28, 2008, at 5:44 AM, Glynn Clements wrote:
Michael Barton wrote:
Is there any pattern to which modules will import and which won't?
All the paths in sys.path are valid.
That isn't what I asked.
Which modules will import, and which won't? Presumably "sys" imports
(that's built i
On Jul 28, 2008, at 9:34 AM, Glynn Clements wrote:
We needed the -framework flags because -l would get the system tcltk
symlinks.
Er, not if you also use -L, surely?
I never got a clarification from Michael (or I missed it) if -L/usr/
lib was in his link command for NVIZ. That would have co
William Kyngesburye wrote:
> >> Looks like we need the tcltk header paths.
> >
> > In that case, I think that we're better off ditching the OSX-specific
> > stuff in its entirety and going back to -I, -L and -l switches. No -F,
> > no -framework.
> >
> We needed the -framework flags because -l wo
On Jul 28, 2008, at 7:50 AM, Glynn Clements wrote:
Looks like we need the tcltk header paths.
In that case, I think that we're better off ditching the OSX-specific
stuff in its entirety and going back to -I, -L and -l switches. No -F,
no -framework.
We needed the -framework flags because -l w
William Kyngesburye wrote:
> >> I haven't run a compile yet - I didn't see any of the sources that
> >> include the tcltk headers get updated yet.
> >
> > The easiest way to find which sources need updating is to compile and
> > see where the errors occur.
>
> I took a stab at it. There seems t
William Kyngesburye wrote:
> >> I haven't run a compile yet - I didn't see any of the sources that
> >> include the tcltk headers get updated yet.
> >
> > The easiest way to find which sources need updating is to compile and
> > see where the errors occur.
>
> I took a stab at it. There seems t
Michael Barton wrote:
> > Is there any pattern to which modules will import and which won't?
>
> All the paths in sys.path are valid.
That isn't what I asked.
Which modules will import, and which won't? Presumably "sys" imports
(that's built into Python)? What about "os"?
Is it just the modul
11 matches
Mail list logo
