Subject:
|
Re: pressing keys causes LDGLite to step
|
Newsgroups:
|
lugnet.cad.dev.mac
|
Date:
|
Fri, 21 Jun 2002 14:14:26 GMT
|
Viewed:
|
1800 times
|
| |
|
|
In article <35F31E60-84CE-11D6-B597-00306564BFBA@mac.com>,
Jim DeVona <anoved@mac.com> wrote:
> On Thursday, June 20, 2002, at 10:23 PM, Don Heyse wrote:
>
> > Now having said this, it's clear that we could use some instructions
> > that walk through installing the fixed GLUT library because I've got a
> > feeling it's probably not going to come in any future official updates
> > of OS X. Maybe Jim could whip some up since he's actually done it, and
> > then this could be incorporated into the documentation at ldraw.org.
> >
> > Don
>
> Thanks for the push... I've been meaning to write up some directions to
> put on my site anyway. So, I did. You can find them at
> http://wind.prohosting.com/anoved/files/GLUT4.txt (only 2k).
>
> Notice that the directions are not ldraw or ldglite specific - they are
> just general directions for installing the updated GLUT on Mac OS X.
>
> On Thursday, June 20, 2002, at 11:48 PM, Christopher Masi wrote:
>
> > Do most OS X users even have the compiler installed? I installed the BSD
> > subsystem, but I haven't installed the Developers Tools yet. Also, I
> > have a feeling that the next update is going to be a paid update, so a
> > good number of users might not be getting the update/upgrade.
>
> Well, most 'regular' users probably don't have the Developer Tools
> installed, although they probably do have the Tools CD that came with Mac
> OS X. It's been a long time since I've installed them, so I don't remember
> how complicated the process is, but it ought not to be complicated at all.
I would expect that the installation of the Developer Tools is straight
forward. I din't install them because the readme said that 700 MB of
space were required. I have been playing with iMovie, and I regularrly
fill my drive to capacity with out having the Developer Tools installed.
> The average user shouldn't have to configure a thing. You hardly need to
> deal with them at all, though, to compile the new GLUT... just double
> click a project file, click 'build', wait, and then quit.
Just a double click to compile. Hmmm... maybe I will install those
Developer Tools. I thought it was all command line driven using things
that I have vaguely heard of like "makefile" and "cc (gcc)"
> I would suspect that the next release will be paid, too. If the next
> release does include a new GLUT, I would doubt its the exact same one
> we're dealing with here, but it certainly could be an improvement. I don't
> really know about that.
>
> So yeah... perhaps a precompiled version of the new GLUT with a script to
> handle installation is in order?
>
> Jim
A precompiled version would get over one hurdle (I am currently in this
bunch*), and the Mac crowd that likes to tinker but is not so
comfortable with Unix and compling software would be able to use the new
GLUT.
A script would get the GLUT over the next hurdle, and the just make my
Mac work crowd could use the new GLUT.
The last hurdle is determining whether the new GLUT is better than the
old GLUT. What I mean is, a lot of people (me included) feel that
mucking with the OS by installing 3rd party extensions is asking for
trouble (recent examples for me include DoubleCommand, which causes
kernel panics with 10.1.5, and the OS X iMate extension, which has some
problems when used with PowerBooks.)
By the way, thanks for the instructions. I'll be trying the new GLUT for
myself in a little while.
Chris
*Although, since what you said sound pretty simple I might just give it
a try. It will make me feel geeky in a good sort of way to compile my
own software.
--
remove *nogarbageplease*. to e-mail me
Do you see these anomalies in OS X too?
http://homepage.mac.com/cjmasi/osx-issues/os_x_issues.htm
|
|
Message has 2 Replies:
 | | Re: pressing keys causes LDGLite to step
|
| (...) Nope, Project Builder and Interface Builder provide very robust GUIs (although you can use the command line if you want to). Compiling takes a *bit* more effort than just double clicking the file, of course... more like double click... and (...) (22 years ago, 21-Jun-02, to lugnet.cad.dev.mac)
| | | Re: pressing keys causes LDGLite to step
|
| (...) [snip] (...) If you want to feel really geeky you can move on to the next level and try out those fabulous command line tools heard so much about. Grab the ldglite sources and try this: make -f makefile.osx Then you can become an uber-geek by (...) (22 years ago, 21-Jun-02, to lugnet.cad.dev.mac)
|
Message is in Reply To:
| | Re: pressing keys causes LDGLite to step
|
| (...) Thanks for the push... I've been meaning to write up some directions to put on my site anyway. So, I did. You can find them at (URL) (only 2k). Notice that the directions are not ldraw or ldglite specific - they are just general directions for (...) (22 years ago, 21-Jun-02, to lugnet.cad.dev.mac)
|
12 Messages in This Thread:
 
 
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
This Message and its Replies on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
