Menu
▾
▴
visualpython-users
|
From: <hea...@ct...> - 2003-07-21 13:45:43
|
Goo Morning. I am finally able to compile, install, and use VPython from OS X. My systems are running OS 10.2.6, Fink 0.5.3, Safari 1.0, Apple's X11 Beta 3, VPython installer version 2.1.102--30709, and the December 2002 Apple Dev Tools. There is a note on the Fink home page regarding the recent update to the Dec. 2002 Dev Tools. Apparently there are problems with gcc 3.3. Here are some additional instructions that I feel should be placed on the OS X page at VPython.org. - After installing Fink, Gtk+, and Python22, make sure the Fink packages autoconf2.5, automake, automake1.6, numeric, and pkgconfig are installed too. - Before issuing the "./configure --prefix=/sw" command, place the following lines in your ~/.cshrc file: setenv CFLAGS -I/sw/include setenv LDFLAGS -L/sw/include setenv CXXFLAGS $CFLAGS setenv CPPFLAGS $CXXFLAGS setenv BROWSER open The first four are needed so that the compiler can find Fink's gtk and OpenGL libraries. The last environment variable is needed so that invoking help (by pressing F1) from inside IDLE_fork will work. - Note that enabling the "root" account really isn't necessary. You can just use "sudo make install" and give your default admin password. Of course, if there are multiple users on your Mac then the first user's password should suffice since the first user created under OS X automatically has admin privileges. Thanks for everyone's help! Cheers, Joe Heafner - Instructional Astronomy and Physics Home Page http://users.vnet.net/heafnerj/index.html I don't have a Lexus, but I do have a Mac. Same thing. |
|
From: <hea...@ct...> - 2003-07-21 15:39:34
|
>From: "hea...@ct..." <hea...@ct...> > >version 2.1.102--30709, and the December 2002 Apple Dev Tools. There is a > That should read "version 2.1.1-20030709". Sorry for the typos. Cheers, Joe Heafner - Instructional Astronomy and Physics |
|
From: Jonathan B. <jbr...@ea...> - 2003-07-21 19:12:50
|
On Mon, 2003-07-21 at 09:45, hea...@ct... wrote: > Good Morning. > > I am finally able to compile, install, and use VPython from OS X. My systems are > running OS 10.2.6, Fink 0.5.3, Safari 1.0, Apple's X11 Beta 3, VPython installer > version 2.1.102--30709, and the December 2002 Apple Dev Tools. There is a > note on the Fink home page regarding the recent update to the Dec. 2002 Dev > Tools. Apparently there are problems with gcc 3.3. Here are some additional > instructions that I feel should be placed on the OS X page at VPython.org. That doesn't surprise me. Debian ran into severe problems with 3.3 with the official 3.3.0 release when it came out, and the version that Apple is shipping is a pre-release CVS build. But then, so was the 3.1 build that they shipped too. The C++ front end has had a lot of bugfixing work done to it for the upcoming 3.3.1 release. > - After installing Fink, Gtk+, and Python22, make sure the Fink packages > autoconf2.5, automake, automake1.6, numeric, and pkgconfig are installed > too. You shouldn't need Autoconf or Automake for visual unless you are regenerating aclocal.m4, Makefile.in (in any directory except cvisual) or configure. Did you need to do that? The current scripts are generated with autoconf 2.53 and automake 1.6. Did you need these programs for some other purpose? > - Before issuing the "./configure --prefix=/sw" command, place the following > lines in your ~/.cshrc file: > > setenv CFLAGS -I/sw/include > setenv LDFLAGS -L/sw/include > setenv CXXFLAGS $CFLAGS > setenv CPPFLAGS $CXXFLAGS > setenv BROWSER open A note about CFLAGS/CXXFLAGS. Autoconf automatically sets both of these variables to "-O2 -g" unless they are already set in the environment. So, with these settings, just about any Autoconf-based installation procedure will build without optimization or debugging symbols. So, you will probably want to `setenv CFLAGS "-I/sw/include -O2"` (note the double quotes) at least, and if you want to provide more useful bugreports, add -g as well. > The first four are needed so that the compiler can find Fink's gtk and OpenGL > libraries. The last environment variable is needed so that invoking help (by > pressing F1) from inside IDLE_fork will work. > > - Note that enabling the "root" account really isn't necessary. You can just use > "sudo make install" and give your default admin password. Of course, if there > are multiple users on your Mac then the first user's password should suffice > since the first user created under OS X automatically has admin privileges. > > Thanks for everyone's help! > > Cheers, > Joe Heafner - Instructional Astronomy and Physics > Home Page http://users.vnet.net/heafnerj/index.html > I don't have a Lexus, but I do have a Mac. Same thing. Thanks for the feedback, Jonathan Brandmeyer |
|
From: <hea...@ct...> - 2003-07-21 19:51:01
|
>From: "Jonathan Brandmeyer" <jbr...@ea...> > >> - After installing Fink, Gtk+, and Python22, make sure the Fink packages >> autoconf2.5, automake, automake1.6, numeric, and pkgconfig are installed >> too. > >You shouldn't need Autoconf or Automake for visual unless you are >regenerating aclocal.m4, Makefile.in (in any directory except cvisual) >or configure. Did you need to do that? The current scripts are >generated with autoconf 2.53 and automake 1.6. Did you need these >programs for some other purpose? > You've officially gone over my head. :-) All I know is that "make" wouldn't run to completion for me until these packages were installed. However, I've only done all of this on my iBook. Tonight I will repeat it all on my iMac and I'll try to reproduce my results. >A note about CFLAGS/CXXFLAGS. Autoconf automatically sets both of these >variables to "-O2 -g" unless they are already set in the environment. >So, with these settings, just about any Autoconf-based installation >procedure will build without optimization or debugging symbols. So, you >will probably want to `setenv CFLAGS "-I/sw/include -O2"` (note the >double quotes) at least, and if you want to provide more useful >bugreports, add -g as well. > Noted. I'll do this on my iMac. Cheers, Joe Heafner - Instructional Astronomy and Physics |
|
From: Joe H. <hea...@vn...> - 2003-07-22 23:41:27
|
On Monday, Jul 21, 2003, at 15:12 US/Eastern, Jonathan Brandmeyer wrote: >> - After installing Fink, Gtk+, and Python22, make sure the Fink >> packages >> autoconf2.5, automake, automake1.6, numeric, and pkgconfig are >> installed >> too. > > You shouldn't need Autoconf or Automake for visual unless you are > regenerating aclocal.m4, Makefile.in (in any directory except cvisual) > or configure. Did you need to do that? The current scripts are > generated with autoconf 2.53 and automake 1.6. Did you need these > programs for some other purpose? After building Visual on my iMac, I see that you're quite correct. The autoconf2.5, automake, and automake1.6 packages aren't needed. I had them for compiling XEphem. I neglected to mention that the gtkglarea package is required. So, in addition to Gtk+ (plus all its dependencies) and Python22 (plus all its dependencies), the pkgconfig, gtkglarea, and numeric packages are required to build Visual. Of course, the system-xfree86 package is required if you're using Apple's X11 implementation, as is the X11 SDK. >> - Before issuing the "./configure --prefix=/sw" command, place the >> following >> lines in your ~/.cshrc file: >> >> setenv CFLAGS -I/sw/include >> setenv LDFLAGS -L/sw/include >> setenv CXXFLAGS $CFLAGS >> setenv CPPFLAGS $CXXFLAGS >> setenv BROWSER open > > A note about CFLAGS/CXXFLAGS. Autoconf automatically sets both of > these > variables to "-O2 -g" unless they are already set in the environment. > So, with these settings, just about any Autoconf-based installation > procedure will build without optimization or debugging symbols. So, > you > will probably want to `setenv CFLAGS "-I/sw/include -O2"` (note the > double quotes) at least, and if you want to provide more useful > bugreports, add -g as well. I actually forgot about this, but it's something I can do if I want to rebuild Visual. I hope these changes get put on the VPython OS X page for potential OS X users, especially that BROWSER flag. I nearly lost sleep over that one. Cheers, Joe Heafner ----- <http://www.donotcall.gov/> Use it! Be sure to complain about having to re-register every five years and about the fact that political fundraisers are exempt! |
|
From: <jos...@ca...> - 2003-07-21 20:00:38
|
Hi, How to zoom in and zoom out with code, eg controlling the zoom with some scene params thanks.... |
|
From: Bruce S. <bas...@un...> - 2003-07-24 00:56:39
|
See the section "Controlling One or More Visual Display Windows" in the=20 on-line reference manual. Basically, you need to adjust scene.forward=20 (direction of view), scene.range (or equivalently scene.scale) for zoom,=20 possibly scene.fov (field of view). Note that the demo program=20 stonehenge.py continually adjusts zoom and rotate based on mouse motion,=20 to let you move through the scene. Bruce Sherwood Jos=E9 A Mart=EDn H wrote: > Hi, How to zoom in and zoom out with code, eg controlling the zoom with= some > scene params >=20 >=20 > thanks.... >=20 >=20 >=20 > ------------------------------------------------------- > This SF.net email is sponsored by: VM Ware > With VMware you can run multiple operating systems on a single machine. > WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual machines at the > same time. Free trial click here: http://www.vmware.com/wl/offer/345/0 > _______________________________________________ > Visualpython-users mailing list > Vis...@li... > https://lists.sourceforge.net/lists/listinfo/visualpython-users |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X