> Probably a stupid suggestion, but .......
When someone posts a stupid question, there is no such thing as a stupid suggestion ;-) I like creating a blank project as a habit. Too many weeds in someone else's project files that I don't know about. I'm finally to the point where I prefer XCode over Developers Studio, but I still don't know the in's and out's as well as I should. I've been using Windows since the 16-bit days, and only switched to the Mac a few years ago. I still feel rather foolish sometimes because the environment is really different from what I'm used to for many years prior. Occasionally, I accidentally "get it right", and I don't worry too much about why... this is one of those cases. Shortly after posting the message, I found that adding the frameworks directly from the XCode build directory where they were built worked fine. I then cleaned everything out and rebuilt, put them in the proper framework folder and it just worked. The only thing I can figure is that despite my "certainty that I didn't", I must have built them in debug mode the first time (a pretty stupid mistake, but I have been under duress lately). Or permissions were screwed up somehow... I had been playing back and forth with environment settings between using the Tiger and the Leopard SDK, and I must have gotten distracted at a key moment and got things out of sync. When all else fails, burn it all to the ground and start over! Anyhow, thanks for having pity, all is well now ;-) Richard On Jan 24, 2008, at 10:54 AM, Stephen Northcott wrote: > Richard, > > Probably a stupid suggestion, but have you tried using the OSG > Template, and then adding to that. > > You may be doing that already, but from the way you describe it it > looks like you are doing it the other way around. > > I have not run into the problem you describe, but have found that > sometimes something gets borked when you try to combine other projects > with different dependencies.. When that does happen I have learned > from experience (or perhaps as a function of my inexperience) that > creating a fresh project, and putting it all together cleanly will > solve the problem quicker than a lot of rooting around. > > Hope that is some help, > Stephen. > > On Jan 24, 2008, at 10:21 PM, Richard S. Wright Jr. wrote: > >> After merrily going along my way using OSG on my Mac laptop for a few >> months, I got a new MacPro and started setting everything up fresh. >> >> No matter how I install OSG (download prebuild frameworks, or make >> them myself), when I add them to an XCode project I get a linking >> error "framework not found osg". All the OSG frameworks including >> OpenThreads give me this error when I add them to the project. No >> other frameworks do this, just the OSG frameworks. I'm building on >> Leopard. >> >> Yes, I know something is fu-barred, I never had this problem on my >> MacBook Pro and I have built OSG many times. This is some sort >> esoteric Xcode problem and/or tangentially related to how OSG is >> built. OSG apps build on my MacBook Pro run fine on the MacPro, so >> the >> frameworks really are there... >> >> Any Mac/OSG/XCoders run into this before? I'm using GLUT, and the >> XCode project included (I'm using OSG 2.2 from source) that builds >> OSG >> works, but I cannot find any compiler or linker settings in that >> project that when transported to the other do the trick. >> >> Richard >> >> _______________________________________________ >> osg-users mailing list >> [email protected] >> http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org > > _______________________________________________ > osg-users mailing list > [email protected] > http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org _______________________________________________ osg-users mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
