Michael Schwier wrote: > Am 10.04.2007 um 18:48 schrieb Patrick Hartling: > >> Michael Schwier wrote: >>> 2. the compiled tutorials didn't start, because the dylibs were not >>> found, so I tried to set up the environment variables by editing the >>> environment.plist file. The file looks like this but it doesn't work. >>> >>> <?xml version="1.0" encoding="UTF-8"?> >>> <!DOCTYPE plist PUBLIC "-//Apple Computer//DTD PLIST 1.0//EN" >>> "http:// >>> www.apple.com/DTDs/PropertyList-1.0.dtd"> >>> <plist version="1.0"> >>> <dict> >>> <key>DYLD_LIBRARY_PATH</key> >>> <string>/Users/mschwier/Projects/OpenSG/Builds/powerpc- >>> apple- >>> darwin-g++/lib/opt:</string> >>> </dict> >>> </plist> >>> >>> Any ideas what is wrong? I copied the dylibs to the tutorial folder >>> then and it works fine, but thats kind of a dirty solution ... >> It's much easier to set the environment variable DYLD_LIBRARY_PATH >> in your >> shell. By setting it in environment.plist, you will have to restart >> Terminal.app or possibly log out and log back in for the changes to >> take effect. >> > > I did set the environment in the .profile. Now it works fine, thanks :-) > >>> 3. Are there any suggestions or tips how to get a OpenSG based Visual >>> Studio project correctly set up under XCode. I am a complete newbie >>> to this whole Mac thing, so any help from experienced Mac useres is >>> _very_ welcome :-) >> I haven't tried that. It shouldn't be too hard as Xcode is very >> easy to use. >> The one thing that would be a little different than other uses of >> Xcode for >> application development is that OpenSG is not compiled as a >> collection of >> frameworks. That just means that you have to list the OpenSG libraries >> against which you are linking rather than referencing frameworks. >> You would >> still need to reference at least the OpenGL framework and then >> either the >> GLUT, Carbon, or Cocoa framework depending on how you are doing >> windowing. >> At any rate, the Apple documentation is very good, and they have >> excellent >> tutorials on the use of Xcode. I suggest that you start here: >> >> http://developer.apple.com/tools/xcode/ > > thanks for the tips, though I didn't understand yet what you meant > with the framework vs. library thing, but I'll get to it.
If you're using Xcode, I don't think that the difference should be too noticeable. If you were making a command line build yourself, then you would need to handle the difference between the "-framework ..." and "-l..." options for linking. > For our > windowing we are using Qt, since it was great to work with Qt under > windows (they _define_ good documentation) I hope it's the same under > Mac. One of the many nice things about Qt is that it is (by and large) the same API on all platforms. Since you're using Qt for windowing, you can ignore my mention of GLUT, Carbon, and Cocoa. -Patrick -- Patrick L. Hartling | VP Engineering, Infiscape Corp. PGP: http://tinyurl.com/2msw3 | http://www.infiscape.com/
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________ Opensg-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/opensg-users
