On Tue 15 Apr 2003, "Van Genechten, Bj=F6rn" wrote:
> I am trying to install glut (to be able to use the vgui_text_tableau),
> I got the files from the internet and copied them into the appropriate
> Glut32.dll --> c:\winnt\system32
> Glut32.lib --> c:\program files\microsoft visual
> Glut.h --> c:\program files\microsoft visual
Good. I'm reasonably sure you only need either the static .lib or the
dynamic .dll, not both. However, I'm not a Windows user.
> But when I start the example program of vxl (using the
> vgui_text_tableau), it still links to the mfc and does not display any
> text on the screen.
> This is what I get on the text screen
> vgui : registered 'mfc'
> vgui : initialize 'mfc'
Did you re-run CMake and recompile vgui?
When you run CMakeSetup, there are two entries you may need to add:
GLUT_INCLUDE_DIR and GLUT_glut_LIBRARY. These may be automatically
found on Windows. I'm not sure. You may need to toggle the "advanced"
button on CMake to see these entries.
Then, you need to re-compile vgui. You will need to actually "clean"
and "rebuild". Why? Because when the glut libraries are found, CMake
automatically sets a pre-processor symbol "HAS_GLUT". In order to use
this, the source files need to be re-compiled. And since it is a
pre-processor flag, the normal dependency checking will not cause an
automatic re-build of the affected source files.
The registered toolkits are determined at the time vgui is
compiled. There is no clean way to avoid this in Standard C++. This
means that vgui needs to be re-compiled[*] every time you add or remove a
toolkit. (After making the appropriate changes in CMake, of course.)
> Can somebody give me some advice on how to solve this ??
> (do I have to change some settings in the cmake, or do I have to rebuil=
> the whole vxl code ??)
In summary, both.
[*] Actually, only vgui_register_all.cxx _needs_ to be
re-compiled. However, depending on the toolkit, some other files may
depend on the pre-processor flags that are set by the toolkit being