visualpython-users

Re: [Visualpython-users] Event-driven / callback programming of mouse or keyboard

[Bruce S. <Bru...@nc...>]

I can't think of a way to do that within the existing structure.

I'll mention that in the new GlowScript (glowscript.org:
JavaScript/CoffeeScript plus WebGl, based on the VPython design),
events are handled with callbacks.

Bruce Sherwood

On Mon, May 21, 2012 at 12:30 PM, Sophie <its...@ho...> wrote:
> Is there any way to do event-driven programming, with callbacks for mouse or keyboard events? I would rather not use the polling style shown in example on the web site.
>
> e.g.
>
> onKey('a', processKeyA)
>
> onMouseDown(processMouseDown)
>
> onMouseDownOn(myCube, processMouseDownOnObject)
>
> Thanks!

[Visualpython-users] Event-driven / callback programming of mouse or keyboard

[Sophie <its...@ho...>]

Is there any way to do event-driven programming, with callbacks for mouse or keyboard events? I would rather not use the polling style shown in example on the web site.

e.g. 

onKey('a', processKeyA)

onMouseDown(processMouseDown)

onMouseDownOn(myCube, processMouseDownOnObject)

Thanks!

Re: [Visualpython-users] Fwd: Windows CPU Monitoring With vpython

[Bruce S. <Bru...@nc...>]

I previously reported receiving a note from Hadi Syarief which may be
of interest to VPython users. In order to post  to the mailing list I
had to omit the large image he included, showing an array of 9 graphs
of computer performance vs. time, such as memory and cpu usage.

It was pointed out that word wraps were lost, and I was asked to
repost the program as an attachment. Here it is.

Bruce Sherwood

[Visualpython-users] Fwd: Windows CPU Monitoring With vpython

[Bruce S. <Bru...@nc...>]

I received this note from Hadi Syarief which may be of interest to
VPython users. In order to post  to the mailing list I had to omit the
large image he included, showing an array of 9 graphs of computer
performance vs. time, such as memory and cpu usage.

Bruce Sherwood

---------- Forwarded message ----------
From: Hadi Syarief <had...@ho...>
Date: Tue, May 1, 2012 at 9:26 PM
Subject: Windows CPU Monitoring With vpython
To: bru...@nc...


Hi Bruce,

I just want to share my program with others vpyhton user, my goals is
to use vpython and others python module such as matplotlib for
graphical environment.
I use psutil module, wmi module and visual.graph module.

Souce Code :

import wmi
import psutil
import os
from visual.graph import *
from visual.controls import *


graph1 = gdisplay(x=0,y=0 ,width=400, height=300,
xtitle='Interval', ytitle='Bytes',
foreground=color.green, background=color.black)
label(display=graph1.display, pos=(50000,100000000000), text="Network
Monitoring")
graph1.display.visible = False # make the display invisible

f1 = gcurve(color=color.cyan)
f2 = gcurve(color=color.red)
f3 = gcurve(color=color.blue)
f4 = gcurve(color=color.green)

graph2 = gdisplay(x=0,y=0, width=400, height=300,xtitle='Interval',
ytitle='Percentage',
foreground=color.green, background=color.black)
label(display=graph2.display, pos=(50000,100), text="CPU and Temp Processor")
graph2.display.visible = False # make the display invisible
f5 = gcurve(color=color.red)
f6 = gcurve(color=color.yellow)

graph3 = gdisplay(x=0,y=0, width=400, height=300,xtitle='Interval',
ytitle='Bytes',
foreground=color.green, background=color.black)
label(display=graph3.display, pos=(50000,100000000000), text="Bytes
Memory Usage")
graph3.display.visible = False # make the display invisible
f7=gcurve(color=color.yellow)
f8=gcurve(color=color.red)

graph4 = gdisplay(x=0,y=0, width=400, height=300,xtitle='Interval',
ytitle='Count',
foreground=color.green, background=color.black)
label(display=graph4.display, pos=(50000,100000000000), text="Read Count")
graph4.display.visible = False # make the display invisible
f9=gcurve(color=color.blue)
f10=gcurve(color=color.orange)

graph5 = gdisplay(x=0,y=0, width=400, height=300,xtitle='Interval',
ytitle='Time',
foreground=color.green, background=color.black)
label(display=graph5.display, pos=(50000,10000000000), text="Read Time")
graph5.display.visible = False # make the display invisible
f11=gcurve(color=color.red)
f12=gcurve(color=color.yellow)

graph6 = gdisplay(x=0,y=0, width=400, height=300,xtitle='Interval',
ytitle='Time',
foreground=color.green, background=color.black)
label(display=graph6.display, pos=(50000,10000000000), text="Read Time")
graph6.display.visible = False # make the display invisible
f13=gcurve(color=color.red)
f14=gcurve(color=color.yellow)
f15=gcurve(color=color.blue)
f16=gcurve(color=color.magenta)
f17=gcurve(color=color.green)

graph7 = gdisplay(x=0,y=0, width=400, height=300,xtitle='Interval',
ytitle='Time',
foreground=color.green, background=color.black)
label(display=graph7.display, pos=(50000,10000000000), text="Read Time")
graph7.display.visible = False # make the display invisible
f18=gcurve(color=color.blue)
f19=gcurve(color=color.orange)
f20=gcurve(color=color.red)
f21=gcurve(color=color.magenta)
f22=gcurve(color=color.green)
f23=gcurve(color=color.cyan)

graph8 = gdisplay(x=0,y=0, width=400, height=300,xtitle='Interval',
ytitle='Time',
foreground=color.green, background=color.black)
label(display=graph8.display, pos=(50000,10000000000), text="Read Time")
graph8.display.visible = False # make the display invisible
f24=gcurve(color=color.yellow)
f25=gcurve(color=color.blue)
f26=gcurve(color=color.red)
f27=gcurve(color=color.orange)

graph9 = gdisplay(x=0,y=0, width=400, height=300,xtitle='Interval',
ytitle='Time',
foreground=color.green, background=color.black)
label(display=graph9.display, pos=(50000,10000000000), text="Read Time")
graph9.display.visible = False # make the display invisible
f28 = gcurve(color=color.cyan)
f29 = gcurve(color=color.red)
f30 = gcurve(color=color.blue)
f31 = gcurve(color=color.green)
f32=gcurve(color=color.yellow)
f33=gcurve(color=color.blue)
f34=gcurve(color=color.red)
f35=gcurve(color=color.orange)
f36 = gcurve(color=color.red)
f37 = gcurve(color=color.yellow)
f38=gcurve(color=color.yellow)
f39=gcurve(color=color.red)
f40=gcurve(color=color.blue)
f41=gcurve(color=color.orange)
f42=gcurve(color=color.red)
f43=gcurve(color=color.yellow)
f44=gcurve(color=color.red)
f45=gcurve(color=color.yellow)
f46=gcurve(color=color.blue)
f47=gcurve(color=color.magenta)
f48=gcurve(color=color.green)
f49=gcurve(color=color.blue)
f50=gcurve(color=color.orange)
f51=gcurve(color=color.red)
f52=gcurve(color=color.magenta)
f53=gcurve(color=color.green)
f54=gcurve(color=color.cyan)


for x in range(100000000):
  e=psutil.network_io_counters()
  d=e.bytes_sent
  f=e.bytes_recv
  g=e.packets_sent
  h=e.packets_recv
  dd=str(d)
  print d
  ff=str(f)
  print f
  gg=str(g)
  print g
  hh=str(h)
  print h
  p = psutil.Process(os.getpid())
  b = p.get_cpu_percent(interval=0.1)
  w=wmi.WMI(namespace="root\wmi")
  temperature_info=w.MSAcpi_ThermalZoneTemperature()[0]
  a=(temperature_info.CurrentTemperature/10)-273
  i=psutil.disk_io_counters()
  j=i.read_count
  k=i.write_count
  l=i.read_bytes
  m=i.write_bytes
  n=i.read_time
  o=i.write_time
  q=psutil.avail_phymem()
  r=psutil.used_phymem()
  s=psutil.total_virtmem()
  t=psutil.avail_virtmem()
  u=psutil.used_virtmem()
  v=psutil.disk_io_counters(perdisk=False)
  z=v.read_count
  z1=v.write_count
  z2=v.read_bytes
  z3=v.write_bytes
  z4=v.read_time
  z5=v.write_time
  z6=psutil.network_io_counters(pernic=False)
  z7=z6.bytes_sent
  z8=z6.bytes_recv
  z9=z6.packets_sent
  z10=z6.packets_recv
  f1.plot(pos=(x,d))
  dd=str(d)
  print d
  f2.plot(pos=(x,f))
  f3.plot(pos=(x,g))
  f4.plot(pos=(x,h))
  f5.plot(pos=(x,b))
  f6.plot(pos=(x,a))
  f7.plot(pos=(x,l))
  f8.plot(pos=(x,m))
  f9.plot(pos=(x,j))
  f10.plot(pos=(x,k))
  f11.plot(pos=(x,n))
  f12.plot(pos=(x,o))
  f13.plot(pos=(x,q))
  f14.plot(pos=(x,r))
  f15.plot(pos=(x,s))
  f16.plot(pos=(x,t))
  f17.plot(pos=(x,u))
  f18.plot(pos=(x,z))
  f19.plot(pos=(x,z1))
  f20.plot(pos=(x,z2))
  f21.plot(pos=(x,z3))
  f22.plot(pos=(x,z4))
  f23.plot(pos=(x,z5))
  f24.plot(pos=(x,z7))
  f25.plot(pos=(x,z8))
  f26.plot(pos=(x,z9))
  f27.plot(pos=(x,z10))
  f28.plot(pos=(x,d))
  dd=str(d)
  print d
  f29.plot(pos=(x,f))
  f30.plot(pos=(x,g))
  f31.plot(pos=(x,h))
  f32.plot(pos=(x,b))
  f33.plot(pos=(x,a))
  f34.plot(pos=(x,l))
  f35.plot(pos=(x,m))
  f36.plot(pos=(x,j))
  f37.plot(pos=(x,k))
  f38.plot(pos=(x,n))
  f39.plot(pos=(x,o))
  f40.plot(pos=(x,q))
  f41.plot(pos=(x,r))
  f42.plot(pos=(x,s))
  f43.plot(pos=(x,t))
  f44.plot(pos=(x,u))
  f45.plot(pos=(x,z))
  f46.plot(pos=(x,z1))
  f47.plot(pos=(x,z2))
  f48.plot(pos=(x,z3))
  f49.plot(pos=(x,z4))
  f50.plot(pos=(x,z5))
  f51.plot(pos=(x,z7))
  f52.plot(pos=(x,z8))
  f53.plot(pos=(x,z9))
  f54.plot(pos=(x,z10))

Re: [Visualpython-users] Keyboard Interactions

[Akasei Y. <ak...@in...>]

I doubt that everyone wanted to set up their system according to my
recommendations - to properly run the program.
Number of events will be increased to handle the keyboard?

2012/4/27 Bruce Sherwood <Bru...@nc...>

> It's available on Windows 7. In the Control Panel search box, enter
> "keyboard", then click on "Keyboard" to get "Keyboard Properties" and
> change the "Repeat delay" setting.
>
> Bruce Sherwood
>
> On Fri, Apr 27, 2012 at 11:10 AM, Anton Sherwood <br...@po...> wrote:
> > On 2012-4-27 05:46, Akasei Yoshiko wrote:
> >> When I press and hold one key (anyone) - there is small pause
> >> between first and the rest of events. How to eliminate this?
> >
> > On MacOS, System Preferences / Keyboard has a slider for "Delay Until
> > Repeat".
> >
> > To my surprise, I can't find an analogous control on Windows 7.
> >
> > --
> > Anton Sherwood *\\* www.bendwavy.org *\\* www.zazzle.com/tamfang
>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Visualpython-users mailing list
> Vis...@li...
> https://lists.sourceforge.net/lists/listinfo/visualpython-users
>

Re: [Visualpython-users] Keyboard Interactions

[Bruce S. <Bru...@nc...>]

It's available on Windows 7. In the Control Panel search box, enter
"keyboard", then click on "Keyboard" to get "Keyboard Properties" and
change the "Repeat delay" setting.

Bruce Sherwood

On Fri, Apr 27, 2012 at 11:10 AM, Anton Sherwood <br...@po...> wrote:
> On 2012-4-27 05:46, Akasei Yoshiko wrote:
>> When I press and hold one key (anyone) - there is small pause
>> between first and the rest of events. How to eliminate this?
>
> On MacOS, System Preferences / Keyboard has a slider for "Delay Until
> Repeat".
>
> To my surprise, I can't find an analogous control on Windows 7.
>
> --
> Anton Sherwood *\\* www.bendwavy.org *\\* www.zazzle.com/tamfang

Re: [Visualpython-users] Keyboard Interactions

[Anton S. <br...@po...>]

On 2012-4-27 05:46, Akasei Yoshiko wrote:
> When I press and hold one key (anyone) - there is small pause
> between first and the rest of events. How to eliminate this?

On MacOS, System Preferences / Keyboard has a slider for "Delay Until 
Repeat".

To my surprise, I can't find an analogous control on Windows 7.

-- 
Anton Sherwood *\\* www.bendwavy.org *\\* www.zazzle.com/tamfang

Re: [Visualpython-users] Keyboard Interactions

[Bruce S. <Bru...@nc...>]

Since your program works normally for me, I'm wondering whether you
mean that you expected to get diagonal motion with both keys held
down? There isn't currently any way to detect multiple simultaneous
keys in VPython (other than combinations with shift, ctrl, or alt, of
course).

As for the delay before repeating starts, I think that's a feature of
most computer systems, intended to prevent unwanted repetition when
you finger lingers just a bit too long on a key. You have to hold the
key down long enough to convince the operating system that you really
do want repetition.

Bruce Sherwood

On Fri, Apr 27, 2012 at 6:43 AM, Akasei Yoshiko <ak...@in...> wrote:
> How i can chack if key is pressed?
> Or when I press arrow Left and arrow Up my "ball" move only in one
> direction.
>
>
>> # -*- coding: UTF-8 -*-
>> from visual import *
>>
>> scene = display( title='Przykład', x=0, y=0, width=640, height=480,
>> center=( 0, 0, 0 ), background=( 0, 0, 0 ), fov=1.0 )
>> ball = sphere( pos=( 0, 0, 0 ), radius=0.5 )
>>
>> scene.autoscale = False
>> scene.range=( 10, 10, 10 )
>>
>> while True:
>>     if scene.kb.keys:
>>         key = scene.kb.getkey()
>>         if key == 'right':
>>             ball.pos.x += 1
>>         if key == 'left':
>>             ball.pos.x -= 1
>>         if key == 'up':
>>             ball.pos.y += 1
>>         if key == 'down':
>>             ball.pos.y -= 1
>
>

[Visualpython-users] Keyboard Interactions

[Akasei Y. <ak...@in...>]

When I press and hold one key (anyone) - there is small pause between first
and the rest of events. How to eliminate this?

[Visualpython-users] Keyboard Interactions

[Akasei Y. <ak...@in...>]

How i can chack if key is pressed?
Or when I press arrow Left and arrow Up my "ball" move only in one
direction.


# -*- coding: UTF-8 -*-
> from visual import *
>
> scene = display( title='Przykład', x=0, y=0, width=640, height=480,
> center=( 0, 0, 0 ), background=( 0, 0, 0 ), fov=1.0 )
> ball = sphere( pos=( 0, 0, 0 ), radius=0.5 )
>
> scene.autoscale = False
> scene.range=( 10, 10, 10 )
>
> while True:
>     if scene.kb.keys:
>         key = scene.kb.getkey()
>         if key == 'right':
>             ball.pos.x += 1
>         if key == 'left':
>             ball.pos.x -= 1
>         if key == 'up':
>             ball.pos.y += 1
>         if key == 'down':
>             ball.pos.y -= 1
>

[Visualpython-users] VPython 5.74

[Bruce S. <Bru...@nc...>]

There's a VPython 5.74 for all platforms available at vpython.org.
This fixes a "level of detail" bug in the display of ellipsoids. Also,
in the github repository are improved instructions for building
VPython on a Mac.

Bruce Sherwood

Re: [Visualpython-users] Rendering with big coordinates

[Bruce S. <Bru...@nc...>]

That was indeed the problem -- the level of detail was miscalculated
because it was based on "radius", which an ellipsoid doesn't have.
I've updated the github repository with new versions of
sphere.hpp/.cpp and ellipsoid.hpp/.cpp, which fix the problem.

I haven't yet built and posted new installers, which will be VPython 5.74.

Bruce Sherwood

On Sun, Apr 22, 2012 at 5:07 PM, Bruce Sherwood <Bru...@nc...> wrote:
> It has nothing to do with the size of the ellipsoid. VPython handles
> numbers with an enormous range; 3400 isn't a big number. The ellipsoid
> object inherits from the sphere object, and you'll see that if you
> change your ellipsoid to a sphere it will look fine.
>
> I was not previously aware of this problem with ellipsoids.  Probably
> the bug is in src/core/sphere.cpp, in the gl_render routine. It must
> be that the "level of detail" (lod) is being calculated incorrectly,
> as though the ellipsoid occupied a very small portion of the window
> (in which case a sphere or ellipsoid is rendered crudely, since then
> you can't see detail). Maybe the mistake is that the screen coverage
> is computed using "radius", which is an attribute of a sphere but not
> of an ellipsoid.
>
> Bruce Sherwood
>
> On Sun, Apr 22, 2012 at 4:11 PM, K.-Michael Aye <kmi...@gm...> wrote:
>> Dear all,
>>
>> I noticed a lack of precision in the rendering of the ellipsoid when going
>> to big numbers.
>> I need these big numbers because I am trying to display planetary remote
>> sensing illumination scenarios.
>> Here is the code I used to create the attached image:
>>
>> from visual import *
>>
>> xaxis = arrow(axis=(4000,0,0), shaftwidth=40, color=color.red)
>> yaxis = arrow(axis=(0,4000,0), shaftwidth=40, color=color.green)
>> zaxis = arrow(axis=(0,0,4000), shaftwidth=40, color=color.blue)
>> mars = ellipsoid(length=2*3396.19,height=2*3396.19,width=2*3376.2,
>> opacity=0.5, color=(1,0.7,0.2))
>>
>>
>> As you can see the ellipsoid is very 'edgy', can this be improved somehow?
>>
>> Best regards,
>> Michael

Re: [Visualpython-users] Rendering with big coordinates

[Bruce S. <Bru...@nc...>]

It has nothing to do with the size of the ellipsoid. VPython handles
numbers with an enormous range; 3400 isn't a big number. The ellipsoid
object inherits from the sphere object, and you'll see that if you
change your ellipsoid to a sphere it will look fine.

I was not previously aware of this problem with ellipsoids.  Probably
the bug is in src/core/sphere.cpp, in the gl_render routine. It must
be that the "level of detail" (lod) is being calculated incorrectly,
as though the ellipsoid occupied a very small portion of the window
(in which case a sphere or ellipsoid is rendered crudely, since then
you can't see detail). Maybe the mistake is that the screen coverage
is computed using "radius", which is an attribute of a sphere but not
of an ellipsoid.

Bruce Sherwood

On Sun, Apr 22, 2012 at 4:11 PM, K.-Michael Aye <kmi...@gm...> wrote:
> Dear all,
>
> I noticed a lack of precision in the rendering of the ellipsoid when going
> to big numbers.
> I need these big numbers because I am trying to display planetary remote
> sensing illumination scenarios.
> Here is the code I used to create the attached image:
>
> from visual import *
>
> xaxis = arrow(axis=(4000,0,0), shaftwidth=40, color=color.red)
> yaxis = arrow(axis=(0,4000,0), shaftwidth=40, color=color.green)
> zaxis = arrow(axis=(0,0,4000), shaftwidth=40, color=color.blue)
> mars = ellipsoid(length=2*3396.19,height=2*3396.19,width=2*3376.2,
> opacity=0.5, color=(1,0.7,0.2))
>
>
> As you can see the ellipsoid is very 'edgy', can this be improved somehow?
>
> Best regards,
> Michael
>
> ------------------------------------------------------------------------------
> For Developers, A Lot Can Happen In A Second.
> Boundary is the first to Know...and Tell You.
> Monitor Your Applications in Ultra-Fine Resolution. Try it FREE!
> http://p.sf.net/sfu/Boundary-d2dvs2
> _______________________________________________
> Visualpython-users mailing list
> Vis...@li...
> https://lists.sourceforge.net/lists/listinfo/visualpython-users
>

Re: [Visualpython-users] Rendering with big coordinates

[K.-Michael A. <kmi...@gm...>]

Attachments don't seem to work here, at least not via gmane so my 
screenshot is here:
http://dl.dropbox.com/u/139035/Screen%20Shot%202012-04-23%20at%2000.05.26.pdf

Michael



On 2012-04-22 22:11:34 +0000, K.-Michael Aye said:

> Dear all,
> 
> I noticed a lack of precision in the rendering of the ellipsoid when
> going to big numbers.
> I need these big numbers because I am trying to display planetary
> remote sensing illumination scenarios.
> Here is the code I used to create the attached image:
> 
> from visual import *
> 
> xaxis = arrow(axis=(4000,0,0), shaftwidth=40, color=color.red)
> yaxis = arrow(axis=(0,4000,0), shaftwidth=40, color=color.green)
> zaxis = arrow(axis=(0,0,4000), shaftwidth=40, color=color.blue)
> mars = ellipsoid(length=2*3396.19,height=2*3396.19,width=2*3376.2,
> opacity=0.5, color=(1,0.7,0.2))
> 
> 
> As you can see the ellipsoid is very 'edgy', can this be improved somehow?
> 
> Best regards,
> Michael
> 
> ------------------------------------------------------------------------------
> For Developers, A Lot Can Happen In A Second.
> Boundary is the first to Know...and Tell You.
> Monitor Your Applications in Ultra-Fine Resolution. Try it FREE!
> http://p.sf.net/sfu/Boundary-d2dvs2
> _______________________________________________
> Visualpython-users mailing list
> Vis...@li...
> https://lists.sourceforge.net/lists/listinfo/visualpython-users

[Visualpython-users] Rendering with big coordinates

[K.-Michael A. <kmi...@gm...>]

Dear all,

I noticed a lack of precision in the rendering of the ellipsoid when 
going to big numbers.
I need these big numbers because I am trying to display planetary 
remote sensing illumination scenarios.
Here is the code I used to create the attached image:

from visual import *

xaxis = arrow(axis=(4000,0,0), shaftwidth=40, color=color.red)
yaxis = arrow(axis=(0,4000,0), shaftwidth=40, color=color.green)
zaxis = arrow(axis=(0,0,4000), shaftwidth=40, color=color.blue)
mars = ellipsoid(length=2*3396.19,height=2*3396.19,width=2*3376.2, 
opacity=0.5, color=(1,0.7,0.2))


As you can see the ellipsoid is very 'edgy', can this be improved somehow?

Best regards,
Michael

[Visualpython-users] CoffeeScript

[Bruce S. <Bru...@nc...>]

GlowScript (glowscript.org) now lets you write programs in the
significantly easier language CoffeeScript rather than in JavaScript.
See the first page of the GlowScript Help.

CoffeeScript is noticeably closer to Python than JavaScript is,
because like Python it uses white space in meaningful ways.

Bruce Sherwood

Re: [Visualpython-users] gl_extensions compile error

[K.-Michael A. <kmi...@gm...>]

On 2012-04-20 02:53:07 +0000, Bruce Sherwood said:

> In the context of my previous response, the first thing to do is to
> install the pure 32-bit version of Python and see whether that cures
> this problem.

It didn't. :( Which now leaves as the only difference the compiler. 
Trying to get it now.

Michael


> 
> Aaron Mavrinac set up the new git repository, and I'm VERY shaky in my
> use of it. I noticed that he removed the SCons stuff, and I've updated
> the build instructions, so those aspects of your findings have been
> taken care of. If you generate more significant commits, I'll ask you
> to talk with Aaron instead of me, because I'm not yet comfortable with
> how to use git.
> 
> Bruce Sherwood
> 
> On Thu, Apr 19, 2012 at 3:14 PM, K.-Michael Aye <kmi...@gm...> wrote:
>> On 2012-04-19 20:47:24 +0000, Bruce Sherwood said:
>> 
>>> I've not seen this in building for the Mac starting from a python.org
>>> distribution of Python. Line 50 in src/core/util/gl_extensions.cpp
>>> doesn't look much like the error that's reported, which is puzzling.
>>> 
>>> You mention "boost_source", which I don't understand. The
>>> "dependencies" folder should contain the following:
>>> 
>>> threadpool folder
>>> boost_files folder, containing
>>>    boost folder of Boost library includes
>> 
>> Aha! That's how. I believe that this is missing from the MAC-OSX.txt
>> build instructions.
>> I now removed my added boost_source include, added a
>> 
>> ln -s /Users/maye/Dropbox/src/boost_1_49_0/boost
>> 
>> into dependencies/boost_files and it works as before, compiling fine
>> until the gl_extensions problem.
>> 
>> If you want, I can add this info to MAC-OSX.txt and send you a git pull
>> request from my fork? Maybe a good time to practice those github
>> collaboration features, as I understand that visual only recently got
>> there? ;)
>> 
>> I agree that line 50 does not look like it at all:
>> 
>>        if ( EXT_texture3D = d.hasExtension( "GL_EXT_texture3D" ) ) {
>>                F( glTexImage3D );
>>                F( glTexSubImage3D );
>>        } else {
>>                #ifdef __APPLE__
>>                        // Supported natively but NOT as an extension
>>                        EXT_texture3D = true;
>> 50 -->          glTexImage3D = ::glTexImage3D;
>>                        glTexSubImage3D = ::glTexSubImage3D;
>>                #endif
>>        }
>> 
>> 
>> but maybe this ifdef __APPLE__ has something to do with it?
>> 
>> 
>> Michael
>> 
>> 
>>>    mac_libs folder containing
>>>       libboost_python.a
>>>       libboost_signals.a
>>>       libboost_thread.a
>>> 
>>> Bruce Sherwood
>>> 
>>> On Thu, Apr 19, 2012 at 2:18 PM, K.-Michael Aye <kmi...@gm...> wrote:
>>>> Okay, some steps further in my endavour to build visual for EPD, I am
>>>> now using the standard makefile for MacOS, but had to add the
>>>> boost_source folder for including the boost header files (maybe i
>>>> messed something up at compile time there, let's see).
>>>> 
>>>> But currently I am blocked by not compiling gl_extensions:
>>>> 
>>>> g++ -fPIC -MMD -DNDEBUG -mmacosx-version-min=10.5 -arch i386 -DPIC -O2
>>>> -g -finline-functions -I../boost_1_49_0 -I../visual/include/mac
>>>> -I../visual/include
>>>> -I/Library/Frameworks/Python.framework/Versions/Current/include/python2.7
>>>> -I/Library/Frameworks/Python.framework/Versions/Current/lib/python2.7/site-packages/numpy/core/include 
>>>> 
>>>> 
>>>> -I../visual/dependencies/boost_files
>>>> -I../visual/dependencies/threadpool/include
>>>> -F/System/Library/Frameworks/AGL.framework
>>>> -F/System/Library/Frameworks/Carbon.framework
>>>> -F/System/Library/Frameworks/OpenGL.framework   -c -o gl_extensions.o
>>>> ../visual/src/core/util/gl_extensions.cpp
>>>> ../visual/src/core/util/gl_extensions.cpp: In member function ‘void
>>>> cvisual::gl_extensions::init(cvisual::display_kernel&)’:
>>>> ../visual/src/core/util/gl_extensions.cpp:50: error: invalid conversion
>>>> from ‘void (*)(GLenum, GLint, GLint, GLsizei, GLsizei, GLsizei, GLint,
>>>> GLenum, GLenum, const GLvoid*)’ to ‘void (*)(GLenum, GLint, GLenum,
>>>> GLsizei, GLsizei, GLsizei, GLint, GLenum, GLenum, const GLvoid*)’
>>>> make: *** [gl_extensions.o] Error 1
>>>> 
>>>> 
>>>> Has anybody ever seen such an error and remembers what was wrong?
>>>> 
>>>> TIA,
>>>> Michael
>>>> 
>>>> 
>>>> 
>>>> 
>>>> ------------------------------------------------------------------------------
>>>> For Developers, A Lot Can Happen In A Second.
>>>> Boundary is the first to Know...and Tell You.
>>>> Monitor Your Applications in Ultra-Fine Resolution. Try it FREE!
>>>> http://p.sf.net/sfu/Boundary-d2dvs2
>>>> _______________________________________________
>>>> Visualpython-users mailing list
>>>> Vis...@li...
>>>> https://lists.sourceforge.net/lists/listinfo/visualpython-users
>>> 
>>> ------------------------------------------------------------------------------
>>> For Developers, A Lot Can Happen In A Second.
>>> Boundary is the first to Know...and Tell You.
>>> Monitor Your Applications in Ultra-Fine Resolution. Try it FREE!
>>> http://p.sf.net/sfu/Boundary-d2dvs2
>>> _______________________________________________
>>> Visualpython-users mailing list
>>> Vis...@li...
>>> https://lists.sourceforge.net/lists/listinfo/visualpython-users
>> 
>> 
>> 
>> 
>> ------------------------------------------------------------------------------
>> For Developers, A Lot Can Happen In A Second.
>> Boundary is the first to Know...and Tell You.
>> Monitor Your Applications in Ultra-Fine Resolution. Try it FREE!
>> http://p.sf.net/sfu/Boundary-d2dvs2
>> _______________________________________________
>> Visualpython-users mailing list
>> Vis...@li...
>> https://lists.sourceforge.net/lists/listinfo/visualpython-users
> 
> ------------------------------------------------------------------------------
> For Developers, A Lot Can Happen In A Second.
> Boundary is the first to Know...and Tell You.
> Monitor Your Applications in Ultra-Fine Resolution. Try it FREE!
> http://p.sf.net/sfu/Boundary-d2dvs2
> _______________________________________________
> Visualpython-users mailing list
> Vis...@li...
> https://lists.sourceforge.net/lists/listinfo/visualpython-users

Re: [Visualpython-users] gl_extensions compile error

[Bruce S. <Bru...@nc...>]

In the context of my previous response, the first thing to do is to
install the pure 32-bit version of Python and see whether that cures
this problem.

Aaron Mavrinac set up the new git repository, and I'm VERY shaky in my
use of it. I noticed that he removed the SCons stuff, and I've updated
the build instructions, so those aspects of your findings have been
taken care of. If you generate more significant commits, I'll ask you
to talk with Aaron instead of me, because I'm not yet comfortable with
how to use git.

Bruce Sherwood

On Thu, Apr 19, 2012 at 3:14 PM, K.-Michael Aye <kmi...@gm...> wrote:
> On 2012-04-19 20:47:24 +0000, Bruce Sherwood said:
>
>> I've not seen this in building for the Mac starting from a python.org
>> distribution of Python. Line 50 in src/core/util/gl_extensions.cpp
>> doesn't look much like the error that's reported, which is puzzling.
>>
>> You mention "boost_source", which I don't understand. The
>> "dependencies" folder should contain the following:
>>
>> threadpool folder
>> boost_files folder, containing
>>    boost folder of Boost library includes
>
> Aha! That's how. I believe that this is missing from the MAC-OSX.txt
> build instructions.
> I now removed my added boost_source include, added a
>
> ln -s /Users/maye/Dropbox/src/boost_1_49_0/boost
>
> into dependencies/boost_files and it works as before, compiling fine
> until the gl_extensions problem.
>
> If you want, I can add this info to MAC-OSX.txt and send you a git pull
> request from my fork? Maybe a good time to practice those github
> collaboration features, as I understand that visual only recently got
> there? ;)
>
> I agree that line 50 does not look like it at all:
>
>        if ( EXT_texture3D = d.hasExtension( "GL_EXT_texture3D" ) ) {
>                F( glTexImage3D );
>                F( glTexSubImage3D );
>        } else {
>                #ifdef __APPLE__
>                        // Supported natively but NOT as an extension
>                        EXT_texture3D = true;
> 50 -->          glTexImage3D = ::glTexImage3D;
>                        glTexSubImage3D = ::glTexSubImage3D;
>                #endif
>        }
>
>
> but maybe this ifdef __APPLE__ has something to do with it?
>
>
> Michael
>
>
>>    mac_libs folder containing
>>       libboost_python.a
>>       libboost_signals.a
>>       libboost_thread.a
>>
>> Bruce Sherwood
>>
>> On Thu, Apr 19, 2012 at 2:18 PM, K.-Michael Aye <kmi...@gm...> wrote:
>>> Okay, some steps further in my endavour to build visual for EPD, I am
>>> now using the standard makefile for MacOS, but had to add the
>>> boost_source folder for including the boost header files (maybe i
>>> messed something up at compile time there, let's see).
>>>
>>> But currently I am blocked by not compiling gl_extensions:
>>>
>>> g++ -fPIC -MMD -DNDEBUG -mmacosx-version-min=10.5 -arch i386 -DPIC -O2
>>> -g -finline-functions -I../boost_1_49_0 -I../visual/include/mac
>>> -I../visual/include
>>> -I/Library/Frameworks/Python.framework/Versions/Current/include/python2.7
>>> -I/Library/Frameworks/Python.framework/Versions/Current/lib/python2.7/site-packages/numpy/core/include
>>>
>>> -I../visual/dependencies/boost_files
>>> -I../visual/dependencies/threadpool/include
>>> -F/System/Library/Frameworks/AGL.framework
>>> -F/System/Library/Frameworks/Carbon.framework
>>> -F/System/Library/Frameworks/OpenGL.framework   -c -o gl_extensions.o
>>> ../visual/src/core/util/gl_extensions.cpp
>>> ../visual/src/core/util/gl_extensions.cpp: In member function ‘void
>>> cvisual::gl_extensions::init(cvisual::display_kernel&)’:
>>> ../visual/src/core/util/gl_extensions.cpp:50: error: invalid conversion
>>> from ‘void (*)(GLenum, GLint, GLint, GLsizei, GLsizei, GLsizei, GLint,
>>> GLenum, GLenum, const GLvoid*)’ to ‘void (*)(GLenum, GLint, GLenum,
>>> GLsizei, GLsizei, GLsizei, GLint, GLenum, GLenum, const GLvoid*)’
>>> make: *** [gl_extensions.o] Error 1
>>>
>>>
>>> Has anybody ever seen such an error and remembers what was wrong?
>>>
>>> TIA,
>>> Michael
>>>
>>>
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> For Developers, A Lot Can Happen In A Second.
>>> Boundary is the first to Know...and Tell You.
>>> Monitor Your Applications in Ultra-Fine Resolution. Try it FREE!
>>> http://p.sf.net/sfu/Boundary-d2dvs2
>>> _______________________________________________
>>> Visualpython-users mailing list
>>> Vis...@li...
>>> https://lists.sourceforge.net/lists/listinfo/visualpython-users
>>
>> ------------------------------------------------------------------------------
>> For Developers, A Lot Can Happen In A Second.
>> Boundary is the first to Know...and Tell You.
>> Monitor Your Applications in Ultra-Fine Resolution. Try it FREE!
>> http://p.sf.net/sfu/Boundary-d2dvs2
>> _______________________________________________
>> Visualpython-users mailing list
>> Vis...@li...
>> https://lists.sourceforge.net/lists/listinfo/visualpython-users
>
>
>
>
> ------------------------------------------------------------------------------
> For Developers, A Lot Can Happen In A Second.
> Boundary is the first to Know...and Tell You.
> Monitor Your Applications in Ultra-Fine Resolution. Try it FREE!
> http://p.sf.net/sfu/Boundary-d2dvs2
> _______________________________________________
> Visualpython-users mailing list
> Vis...@li...
> https://lists.sourceforge.net/lists/listinfo/visualpython-users

Re: [Visualpython-users] gl_extensions compile error

[Bruce S. <Bru...@nc...>]

I uploaded some improvements to the Mac build instructions in
MAC-OSX.txt. In particular, while there were instructions about
placing the libboost files into dependencies/boost_files/mac_libs, it
didn't say that one also needs to place the boost folder (includes)
into dependencies/boost_files.

Since the version of Python 2.7.3 you have installed from python.org
says it was compiled with gcc 4.2.1, that means that you installed the
32_64 (32-bit/64-bit) version of Python, which will not work with
Visual because the Carbon framework works only with a pure 32-bit
version of Python. The Python 2.7.3 download on the Mac download page
at vpython.org is the one you need to use (the link is to python.org).
I should repeat that I'm actively searching for a solution to the
Carbon issue.

I built the Boost 1.49 libraries for Python 3.2 on the Mac just a few
days ago and didn't see anything about ./b2. Perhaps that is related
to trying to use the 32_64 version of Python?

I apologize for the failings in documentation. I think you're the
first person other than me to use these instructions to build VPython
on the Mac, and you're shaking out some omissions and errors on the
build instructions. Thank you!

Bruce Sherwood

On Thu, Apr 19, 2012 at 4:07 PM, K.-Michael Aye <kmi...@gm...> wrote:
> On 2012-04-19 21:14:03 +0000, K.-Michael Aye said:
>
>> On 2012-04-19 20:47:24 +0000, Bruce Sherwood said:
>>
>>> I've not seen this in building for the Mac starting from a python.org
>>> distribution of Python. Line 50 in src/core/util/gl_extensions.cpp
>>> doesn't look much like the error that's reported, which is puzzling.
>
> Because of this statement I made 'make clean', changed the python dist
> in the makefile to the python.org python 2.7 and tried again, resulting
> in the same error.
>
> One question: python.org's 2.7 python is compiled with GCC 4.2.1:
>
> (master+)[maye@paradigm ~/Dropbox/src/mbuild]$ python
> Python 2.7.3 (v2.7.3:70274d53c1dd, Apr  9 2012, 20:52:43)
> [GCC 4.2.1 (Apple Inc. build 5666) (dot 3)] on darwin
>
> But in your makefile you state:
>
> # Use 4.0 compiler rather than 4.2 so as to build in a way compatible
> with OSX 10.5
>
> How does that fit with the requirement that the boost libs had to be
> compiled with the same gcc version as the python we are building
> against? Isn't that inconsistent?
>
> As I don't have a g++4.0 available, all my trials are done with g++4.2,
> could this be our difference? Even so, I also need to understand above
> inconsistency, if it exists.
>
> Another oddity: the boost compile is now asking to use ./b2 instead of ./bjam.
> Indeed ./bjam even fails on me completely, while ./b2 only fails for
> the compilation of the .dylibs. The static ones are created fine though.
> But as I am not yet at linking stage that is for sure not the reason
> for the gl_extensions compile error.
>
>
> Michael

Re: [Visualpython-users] gl_extensions compile error

[K.-Michael A. <kmi...@gm...>]

On 2012-04-19 21:14:03 +0000, K.-Michael Aye said:

> On 2012-04-19 20:47:24 +0000, Bruce Sherwood said:
> 
>> I've not seen this in building for the Mac starting from a python.org
>> distribution of Python. Line 50 in src/core/util/gl_extensions.cpp
>> doesn't look much like the error that's reported, which is puzzling.

Because of this statement I made 'make clean', changed the python dist 
in the makefile to the python.org python 2.7 and tried again, resulting 
in the same error.

One question: python.org's 2.7 python is compiled with GCC 4.2.1:

(master+)[maye@paradigm ~/Dropbox/src/mbuild]$ python
Python 2.7.3 (v2.7.3:70274d53c1dd, Apr  9 2012, 20:52:43)
[GCC 4.2.1 (Apple Inc. build 5666) (dot 3)] on darwin

But in your makefile you state:

# Use 4.0 compiler rather than 4.2 so as to build in a way compatible 
with OSX 10.5

How does that fit with the requirement that the boost libs had to be 
compiled with the same gcc version as the python we are building 
against? Isn't that inconsistent?

As I don't have a g++4.0 available, all my trials are done with g++4.2, 
could this be our difference? Even so, I also need to understand above 
inconsistency, if it exists.

Another oddity: the boost compile is now asking to use ./b2 instead of ./bjam.
Indeed ./bjam even fails on me completely, while ./b2 only fails for 
the compilation of the .dylibs. The static ones are created fine though.
But as I am not yet at linking stage that is for sure not the reason 
for the gl_extensions compile error.


Michael


>> 
>> You mention "boost_source", which I don't understand. The
>> "dependencies" folder should contain the following:
>> 
>> threadpool folder
>> boost_files folder, containing
>> boost folder of Boost library includes
> 
> Aha! That's how. I believe that this is missing from the MAC-OSX.txt
> build instructions.
> I now removed my added boost_source include, added a
> 
> ln -s /Users/maye/Dropbox/src/boost_1_49_0/boost
> 
> into dependencies/boost_files and it works as before, compiling fine
> until the gl_extensions problem.
> 
> If you want, I can add this info to MAC-OSX.txt and send you a git pull
> request from my fork? Maybe a good time to practice those github
> collaboration features, as I understand that visual only recently got
> there? ;)
> 
> I agree that line 50 does not look like it at all:
> 
> 	if ( EXT_texture3D = d.hasExtension( "GL_EXT_texture3D" ) ) {
> 		F( glTexImage3D );
> 		F( glTexSubImage3D );
> 	} else {
> 		#ifdef __APPLE__
> 			// Supported natively but NOT as an extension
> 			EXT_texture3D = true;
> 50 -->		glTexImage3D = ::glTexImage3D;
> 			glTexSubImage3D = ::glTexSubImage3D;
> 		#endif
> 	}
> 
> 
> but maybe this ifdef __APPLE__ has something to do with it?
> 
> 
> Michael
> 
> 
>> mac_libs folder containing
>> libboost_python.a
>> libboost_signals.a
>> libboost_thread.a
>> 
>> Bruce Sherwood
>> 
>> On Thu, Apr 19, 2012 at 2:18 PM, K.-Michael Aye <kmi...@gm...> wrote:
>>> Okay, some steps further in my endavour to build visual for EPD, I am
>>> now using the standard makefile for MacOS, but had to add the
>>> boost_source folder for including the boost header files (maybe i
>>> messed something up at compile time there, let's see).
>>> 
>>> But currently I am blocked by not compiling gl_extensions:
>>> 
>>> g++ -fPIC -MMD -DNDEBUG -mmacosx-version-min=10.5 -arch i386 -DPIC -O2
>>> -g -finline-functions -I../boost_1_49_0 -I../visual/include/mac
>>> -I../visual/include
>>> -I/Library/Frameworks/Python.framework/Versions/Current/include/python2.7
>>> -I/Library/Frameworks/Python.framework/Versions/Current/lib/python2.7/site-packages/numpy/core/include 
>>> 
>>> 
>>> -I../visual/dependencies/boost_files
>>> -I../visual/dependencies/threadpool/include
>>> -F/System/Library/Frameworks/AGL.framework
>>> -F/System/Library/Frameworks/Carbon.framework
>>> -F/System/Library/Frameworks/OpenGL.framework   -c -o gl_extensions.o
>>> ../visual/src/core/util/gl_extensions.cpp
>>> ../visual/src/core/util/gl_extensions.cpp: In member function ‘void
>>> cvisual::gl_extensions::init(cvisual::display_kernel&)’:
>>> ../visual/src/core/util/gl_extensions.cpp:50: error: invalid conversion
>>> from ‘void (*)(GLenum, GLint, GLint, GLsizei, GLsizei, GLsizei, GLint,
>>> GLenum, GLenum, const GLvoid*)’ to ‘void (*)(GLenum, GLint, GLenum,
>>> GLsizei, GLsizei, GLsizei, GLint, GLenum, GLenum, const GLvoid*)’
>>> make: *** [gl_extensions.o] Error 1
>>> 
>>> 
>>> Has anybody ever seen such an error and remembers what was wrong?
>>> 
>>> TIA,
>>> Michael
>>> 
>>> 
>>> 
>>> 
>>> ------------------------------------------------------------------------------
>>> For Developers, A Lot Can Happen In A Second.
>>> Boundary is the first to Know...and Tell You.
>>> Monitor Your Applications in Ultra-Fine Resolution. Try it FREE!
>>> http://p.sf.net/sfu/Boundary-d2dvs2
>>> _______________________________________________
>>> Visualpython-users mailing list
>>> Vis...@li...
>>> https://lists.sourceforge.net/lists/listinfo/visualpython-users
>> 
>> ------------------------------------------------------------------------------
>> For Developers, A Lot Can Happen In A Second.
>> Boundary is the first to Know...and Tell You.
>> Monitor Your Applications in Ultra-Fine Resolution. Try it FREE!
>> http://p.sf.net/sfu/Boundary-d2dvs2
>> _______________________________________________
>> Visualpython-users mailing list
>> Vis...@li...
>> https://lists.sourceforge.net/lists/listinfo/visualpython-users
> 
> 
> 
> 
> ------------------------------------------------------------------------------
> For Developers, A Lot Can Happen In A Second.
> Boundary is the first to Know...and Tell You.
> Monitor Your Applications in Ultra-Fine Resolution. Try it FREE!
> http://p.sf.net/sfu/Boundary-d2dvs2
> _______________________________________________
> Visualpython-users mailing list
> Vis...@li...
> https://lists.sourceforge.net/lists/listinfo/visualpython-users

Re: [Visualpython-users] gl_extensions compile error

[K.-Michael A. <kmi...@gm...>]

On 2012-04-19 20:47:24 +0000, Bruce Sherwood said:

> I've not seen this in building for the Mac starting from a python.org
> distribution of Python. Line 50 in src/core/util/gl_extensions.cpp
> doesn't look much like the error that's reported, which is puzzling.
> 
> You mention "boost_source", which I don't understand. The
> "dependencies" folder should contain the following:
> 
> threadpool folder
> boost_files folder, containing
>    boost folder of Boost library includes

Aha! That's how. I believe that this is missing from the MAC-OSX.txt 
build instructions.
I now removed my added boost_source include, added a

ln -s /Users/maye/Dropbox/src/boost_1_49_0/boost

into dependencies/boost_files and it works as before, compiling fine 
until the gl_extensions problem.

If you want, I can add this info to MAC-OSX.txt and send you a git pull 
request from my fork? Maybe a good time to practice those github 
collaboration features, as I understand that visual only recently got 
there? ;)

I agree that line 50 does not look like it at all:

	if ( EXT_texture3D = d.hasExtension( "GL_EXT_texture3D" ) ) {
		F( glTexImage3D );
		F( glTexSubImage3D );
	} else {
		#ifdef __APPLE__
			// Supported natively but NOT as an extension
			EXT_texture3D = true;
50 -->		glTexImage3D = ::glTexImage3D;
			glTexSubImage3D = ::glTexSubImage3D;
		#endif
	}


but maybe this ifdef __APPLE__ has something to do with it?


Michael


>    mac_libs folder containing
>       libboost_python.a
>       libboost_signals.a
>       libboost_thread.a
> 
> Bruce Sherwood
> 
> On Thu, Apr 19, 2012 at 2:18 PM, K.-Michael Aye <kmi...@gm...> wrote:
>> Okay, some steps further in my endavour to build visual for EPD, I am
>> now using the standard makefile for MacOS, but had to add the
>> boost_source folder for including the boost header files (maybe i
>> messed something up at compile time there, let's see).
>> 
>> But currently I am blocked by not compiling gl_extensions:
>> 
>> g++ -fPIC -MMD -DNDEBUG -mmacosx-version-min=10.5 -arch i386 -DPIC -O2
>> -g -finline-functions -I../boost_1_49_0 -I../visual/include/mac
>> -I../visual/include
>> -I/Library/Frameworks/Python.framework/Versions/Current/include/python2.7
>> -I/Library/Frameworks/Python.framework/Versions/Current/lib/python2.7/site-packages/numpy/core/include 
>> 
>> -I../visual/dependencies/boost_files
>> -I../visual/dependencies/threadpool/include
>> -F/System/Library/Frameworks/AGL.framework
>> -F/System/Library/Frameworks/Carbon.framework
>> -F/System/Library/Frameworks/OpenGL.framework   -c -o gl_extensions.o
>> ../visual/src/core/util/gl_extensions.cpp
>> ../visual/src/core/util/gl_extensions.cpp: In member function ‘void
>> cvisual::gl_extensions::init(cvisual::display_kernel&)’:
>> ../visual/src/core/util/gl_extensions.cpp:50: error: invalid conversion
>> from ‘void (*)(GLenum, GLint, GLint, GLsizei, GLsizei, GLsizei, GLint,
>> GLenum, GLenum, const GLvoid*)’ to ‘void (*)(GLenum, GLint, GLenum,
>> GLsizei, GLsizei, GLsizei, GLint, GLenum, GLenum, const GLvoid*)’
>> make: *** [gl_extensions.o] Error 1
>> 
>> 
>> Has anybody ever seen such an error and remembers what was wrong?
>> 
>> TIA,
>> Michael
>> 
>> 
>> 
>> 
>> ------------------------------------------------------------------------------
>> For Developers, A Lot Can Happen In A Second.
>> Boundary is the first to Know...and Tell You.
>> Monitor Your Applications in Ultra-Fine Resolution. Try it FREE!
>> http://p.sf.net/sfu/Boundary-d2dvs2
>> _______________________________________________
>> Visualpython-users mailing list
>> Vis...@li...
>> https://lists.sourceforge.net/lists/listinfo/visualpython-users
> 
> ------------------------------------------------------------------------------
> For Developers, A Lot Can Happen In A Second.
> Boundary is the first to Know...and Tell You.
> Monitor Your Applications in Ultra-Fine Resolution. Try it FREE!
> http://p.sf.net/sfu/Boundary-d2dvs2
> _______________________________________________
> Visualpython-users mailing list
> Vis...@li...
> https://lists.sourceforge.net/lists/listinfo/visualpython-users

Re: [Visualpython-users] gl_extensions compile error

[Bruce S. <Bru...@nc...>]

I've not seen this in building for the Mac starting from a python.org
distribution of Python. Line 50 in src/core/util/gl_extensions.cpp
doesn't look much like the error that's reported, which is puzzling.

You mention "boost_source", which I don't understand. The
"dependencies" folder should contain the following:

threadpool folder
boost_files folder, containing
   boost folder of Boost library includes
   mac_libs folder containing
      libboost_python.a
      libboost_signals.a
      libboost_thread.a

Bruce Sherwood

On Thu, Apr 19, 2012 at 2:18 PM, K.-Michael Aye <kmi...@gm...> wrote:
> Okay, some steps further in my endavour to build visual for EPD, I am
> now using the standard makefile for MacOS, but had to add the
> boost_source folder for including the boost header files (maybe i
> messed something up at compile time there, let's see).
>
> But currently I am blocked by not compiling gl_extensions:
>
> g++ -fPIC -MMD -DNDEBUG -mmacosx-version-min=10.5 -arch i386 -DPIC -O2
> -g -finline-functions -I../boost_1_49_0 -I../visual/include/mac
> -I../visual/include
> -I/Library/Frameworks/Python.framework/Versions/Current/include/python2.7
> -I/Library/Frameworks/Python.framework/Versions/Current/lib/python2.7/site-packages/numpy/core/include
> -I../visual/dependencies/boost_files
> -I../visual/dependencies/threadpool/include
> -F/System/Library/Frameworks/AGL.framework
> -F/System/Library/Frameworks/Carbon.framework
> -F/System/Library/Frameworks/OpenGL.framework   -c -o gl_extensions.o
> ../visual/src/core/util/gl_extensions.cpp
> ../visual/src/core/util/gl_extensions.cpp: In member function ‘void
> cvisual::gl_extensions::init(cvisual::display_kernel&)’:
> ../visual/src/core/util/gl_extensions.cpp:50: error: invalid conversion
> from ‘void (*)(GLenum, GLint, GLint, GLsizei, GLsizei, GLsizei, GLint,
> GLenum, GLenum, const GLvoid*)’ to ‘void (*)(GLenum, GLint, GLenum,
> GLsizei, GLsizei, GLsizei, GLint, GLenum, GLenum, const GLvoid*)’
> make: *** [gl_extensions.o] Error 1
>
>
> Has anybody ever seen such an error and remembers what was wrong?
>
> TIA,
> Michael
>
>
>
>
> ------------------------------------------------------------------------------
> For Developers, A Lot Can Happen In A Second.
> Boundary is the first to Know...and Tell You.
> Monitor Your Applications in Ultra-Fine Resolution. Try it FREE!
> http://p.sf.net/sfu/Boundary-d2dvs2
> _______________________________________________
> Visualpython-users mailing list
> Vis...@li...
> https://lists.sourceforge.net/lists/listinfo/visualpython-users

Re: [Visualpython-users] gl_extensions compile error

[Kevin K. <ka...@so...>]

It looks to me like you have pointers to one type of function and are
trying to use them as pointers to a different type of function:

from void (*)(GLenum, GLint, GLint,  GLsizei, GLsizei, GLsizei, GLint, GLenum, GLenum, const GLvoid*)
to   void (*)(GLenum, GLint, GLenum, GLsizei, GLsizei, GLsizei, GLint, GLenum, GLenum, const GLvoid*)

Note that the 3rd argument is GLint in one case and GLenum in the other.

[Visualpython-users] gl_extensions compile error

[K.-Michael A. <kmi...@gm...>]

Okay, some steps further in my endavour to build visual for EPD, I am 
now using the standard makefile for MacOS, but had to add the 
boost_source folder for including the boost header files (maybe i 
messed something up at compile time there, let's see).

But currently I am blocked by not compiling gl_extensions:

g++ -fPIC -MMD -DNDEBUG -mmacosx-version-min=10.5 -arch i386 -DPIC -O2 
-g -finline-functions -I../boost_1_49_0 -I../visual/include/mac 
-I../visual/include 
-I/Library/Frameworks/Python.framework/Versions/Current/include/python2.7 
-I/Library/Frameworks/Python.framework/Versions/Current/lib/python2.7/site-packages/numpy/core/include 
-I../visual/dependencies/boost_files 
-I../visual/dependencies/threadpool/include 
-F/System/Library/Frameworks/AGL.framework 
-F/System/Library/Frameworks/Carbon.framework 
-F/System/Library/Frameworks/OpenGL.framework   -c -o gl_extensions.o 
../visual/src/core/util/gl_extensions.cpp
../visual/src/core/util/gl_extensions.cpp: In member function ‘void 
cvisual::gl_extensions::init(cvisual::display_kernel&)’:
../visual/src/core/util/gl_extensions.cpp:50: error: invalid conversion 
from ‘void (*)(GLenum, GLint, GLint, GLsizei, GLsizei, GLsizei, GLint, 
GLenum, GLenum, const GLvoid*)’ to ‘void (*)(GLenum, GLint, GLenum, 
GLsizei, GLsizei, GLsizei, GLint, GLenum, GLenum, const GLvoid*)’
make: *** [gl_extensions.o] Error 1


Has anybody ever seen such an error and remembers what was wrong?

TIA,
Michael

Re: [Visualpython-users] SConstruct

[Bruce S. <Bru...@nc...>]

I'm not an expert on makefiles, but I think the difference you see is
simply that the Linux makefile is explicit that .o files should be
built from .cpp files, whereas the Mac makefile takes advantage of the
default assumptions of makefiles, which I believe include the notion
that .o files should be built from .cpp files.

Bruce Sherwood

On Thu, Apr 19, 2012 at 10:34 AM, K.-Michael Aye <kmi...@gm...> wrote:
> On 2012-04-19 16:02:17 +0000, Bruce Sherwood said:
>
>> SConstruct was just an experience many years ago by Jonathan
>> Brandmeyer and is now irrelevant.
>
> Thanks, I am creating a cleaned up git branch ONLY for an Mac_EPD
> build. Thanks to git this can live totally independent from anything
> else, so I am kicking everything out that's not required anymore.
>
>>
>> There are three quite different build procedures, for Windows, Mac,
>> and Linux, each of them detailed in VCBuild/VCBuild.txt, MAC-OSX.txt,
>> and INSTALL.txt, respectively. And in the Linux case, in addition to
>> the complex autoconfigure machinery currently used to build the Linux
>> tarball posted at vpython.org, there is a simple makefile in src/gtk2
>> intended to give a sense of a basic build stripped to its essentials
>> and aimed specifically at Ubuntu.
>
> That was a good tip, thanks.
> That leaves me puzzled, how the makefile in src/mac actually can work?
> My makefile-foo is a bit rusty, but I am missing something like this
> line from the src/gtk2/makefile:
>
> %.o: %.cpp
>        $(CXX) $(CVISUAL_CPPFLAGS) $(CVISUAL_CXXFLAGS) -MMD -MF $*.d -MT "$*.d
> $*.lo" -c -o $@ $<
>
> in the src/mac version, that clearly makes use of the previously
> defined flags and tells the make system how to create all the objects.
>
> Still it seems the system gets the CXXFLAGS in the Mac's makefile
> somehow at build time, because when I comment them out, the errors I
> get look different.
> Just really puzzling…
>
> Michael
>
>
>>
>> Bruce Sherwood