Table of Contents
Q: | How do I build a 32-bit version of bugle on an AMD64 system? |
A: | The exact details will depend on your OS. Here is what I do on Gentoo:
Gentoo also tries to be clever by putting in a
|
Q: | Why is a recent (>3.0) version of GCC required? |
A: |
Bugle is driven by a number
of tables that list all the information about the
various types and functions in OpenGL. To capture this
information, it is necessary to parse the OpenGL
header files. It would be very difficult to write a
parser to do this robustly, but GCC already knows how
to do this. Unfortunately, the ability to extract a
parse tree from GCC (the
|
Q: |
Why I am getting an error like |
A: | You need to use a version of GCC that supports this flag. See the previous question for details. |
Q: |
I get an error trying to move
|
A: |
You are probably using GCC
4.0, which has broken support for
|
Q: |
When I compile with GCC 4.2, compilation seems to hang
on |
A: |
There is a performance bug in GCC 4.2.2, possibly
#30052
but possibly not. Either downgrade to 4.1, upgrade to
a version where the bug is fixed , or compile without
optimisation ( |
Q: |
I am getting the error |
A: |
You need to have this file, as it defines extensions
to OpenGL that an application might use. You can
obtain the latest copy from http://www.opengl.org/registry. If you
don't want to put it in your system include
directories, you can create a |
Q: | I am using the NVIDIA header files, and I am getting errors about conflicting definitions. |
A: | Try upgrading to the latest NVIDIA drivers. The 60 series seem to fix many of the problems in older header files.
Alternatively, use the headers from Mesa. You can
place them into a |
Q: |
I am using Gentoo, and during compilation of bugle I
get errors similar to this:
|
A: | This seems to be a problem with Gentoo's system for switching between OpenGL drivers, that causes part of the build process to use the X11 software drivers. A workaround is to switch to the X11 drivers for compilation and installation of bugle:
|
Q: |
I have an x86-64 (Athlon 64/Opteron/EM64T) machine
with 64-bit OS, and compilation fails with the message
|
A: |
This has been reported on Fedora Core 5, where
libtool incorrectly
tries to link against the 32-bit version of
and re-run make. If this still
doesn't work, see if your 64-bit |
Q: |
I am using Fedora 10, and when I run
glxgears under bugle it
exits with the message
|
A: |
This seems to be caused by having two different
versions of |
Q: |
Why do I get the error |
A: |
Most likely your distribution has crippled GCC by
switching on options that improve security but are not
C compliant. Try adding
|
Q: | What is the performance penalty? | ||||||||||||
A: | That depends on what you're doing with the library. If you only use filter-sets that intercept a few functions (like showstats), then all other functions suffer only a small penalty. Using filter-sets that check for error after every function (including showerror and the debugger) adds a much bigger penalty.
To give you an example, here are some rough numbers for Quake3 1.32c on
demo
Tracing is particularly slow because it does file I/O, as well as a lot of text formatting. The overhead will also depend on the CPU/GPU balance. GPU-bound programs will be less affected by overheads. | ||||||||||||
Q: |
I wrote
| ||||||||||||
A: |
You either need to specify a full path to
| ||||||||||||
Q: | How do I get a stack trace when my program crashes inside the OpenGL driver? | ||||||||||||
A: | Use the bugle-unwindstack(7) filter-set. See the manual page for more information. | ||||||||||||
A: |
Use the bugle-log(7) filter-set, and turn
on the | ||||||||||||
Q: |
Do I need to always set | ||||||||||||
A: | No, the first chain in the configuration file is the default. | ||||||||||||
Q: |
Can I avoid using | ||||||||||||
A: |
Yes, you can specify | ||||||||||||
Q: | How do you get SDL-based apps to use BuGLe? | ||||||||||||
A: | On GNU systems, they should work as is. On some systems, it may be necessary to run them as
| ||||||||||||
Q: | How do you get Quake3 or Doom3 to use BuGLe? | ||||||||||||
A: | On GNU systems, they should work as is. On some systems, run it as
Note that Quake3 and Doom3 are 32-bit binaries, so if you have an AMD64 system you will need to compile a 32-bit bugle. | ||||||||||||
Q: | How do you get QT-based apps to use BuGLe? | ||||||||||||
A: |
On GNU systems, they should work as is. There is
currently no known workaround for systems that don't
support | ||||||||||||
Q: | I am using GL_EXT_framebuffer_object to render to texture, but the results do not appear in the texture viewer of gldb-gui. | ||||||||||||
A: | This is a known bug in NVIDIA's 76.76 driver. It is fixed in the 80 series drivers. The results should appear in the framebuffer viewer. | ||||||||||||
Q: |
I'm running 64-bit bugle on a 64-bit OS with a
64-bit application, but when I try to run it, it
tries to open the 32-bit version of | ||||||||||||
A: |
I haven't heard if this actually works, but try
setting | ||||||||||||
A: |
Another potential workaround is to replace
| ||||||||||||
Q: |
I am using ATI drivers and when I run configure, it
does not find | ||||||||||||
A: |
I have had this reported by one Debian user, but
didn't get further details on hardware or driver
version. It appears that this version depended on but
did not link to libpthread. While it is possible to
hack this in |