make instlinks Simple creates symbolic links from the installed directories to the orignal built libs.
On 2/8/07, RJ <[EMAIL PROTECTED]> wrote:
Hi Robert, I am also doing some debugging on OSG. I am debugging osgdem source code of which i am able to see in ddd debugger. But as soon as i want to go the function of osgTerrain dataset through osgdem code i am not able to do so. I have compiled OSG using make debug option and then i am just doing make install. I have no idea of make instlinks (u mentioned below) can u please explain me how this works. best regards RJ On Thu, 2007-02-08 at 09:32 +0000, Robert Osfield wrote: > Hi Gazi, > > I'm a bit confused. I do debugging on the OSG all the time with gdb > under Linux and don't have to just through any hoops. > > What I do is install links to the libs when I first build the > OpenThreads/Producer/OpenSceneGraph using: > > make instlinks > > Then any time after I just go to a local directory and type make debug > and then links automatically map any runtime calls to the debug > library. > > Robert. > > > > On 2/8/07, Gazi Alankus <[EMAIL PROTECTED]> wrote: > > Hi. Here is some useful information for people who want to debug their > > osg apps all the way downto osg's code with gdb. (or preferably, > > kdevelop or kdbg): > > > > In my Gentoo Linux laptop I was trying to create fully debuggable osg > > libraries. I started with OpenThreads, did "make debug" and installed > > the debug libraries. (I had to do "make __inst_lib; make > > __inst_headers" since "make install" makes and installs the release > > library, not the debug library (This isn't necessary for Producer). > > Anyway, I digress.) My sources are in /usr/src/osg/ and will always > > stay there. > > > > I went to /usr/local/lib and did: > > $ gdb libOpenThreads.so > > and then: > > (gdb) list > > which resulted in: > > 1 ../PThread.c++: No such file or directory. > > in ../PThread.c++ > > > > However when I do it from > > /usr/src/osg/OpenThreads/pthread_src/Linux32.Debug it listed the > > source code properly. I know I can tell gdb where the source is, but > > with a large project like osg it would be a hassle in every debug. > > > > After wrestling with makefiles for a long time I found out how to make > > the library point to absolute paths of sources. In Make/makerules > > lines 151-156: > > > > .SUFFIXES: .cpp .o > > .cpp.o: > > $(CXX) $(CXXFLAGS) -c `pwd`/$< > > .SUFFIXES: .c++ .o > > .c++.o: > > $(CXX) $(CXXFLAGS) -c `pwd`/$< > > > > I added the `pwd`/ to make them absolute paths. Now gdb list shows the > > source code. I'll try similar things for Producer and OSG, I'll post > > if there is another suddle thing to fix. > > > > This could be a thing to fix in the source tree, however I don't know > > how portable it would be. > > > > I used the CVS code but it should be similar for the release packages. > > > > In case you are wondering, I'm debugging for the dreaded "Warning:: > > Picked up error in TriangleIntersect" when picking stuff with mouse. > > > > -Gazi > > _______________________________________________ > > osg-users mailing list > > [email protected] > > http://openscenegraph.net/mailman/listinfo/osg-users > > http://www.openscenegraph.org/ > > > _______________________________________________ > osg-users mailing list > [email protected] > http://openscenegraph.net/mailman/listinfo/osg-users > http://www.openscenegraph.org/ > _______________________________________________ osg-users mailing list [email protected] http://openscenegraph.net/mailman/listinfo/osg-users http://www.openscenegraph.org/
_______________________________________________ osg-users mailing list [email protected] http://openscenegraph.net/mailman/listinfo/osg-users http://www.openscenegraph.org/
