Compiling with GCC has created a problem with the .xresources and xrdb files.

PROBLEM

Compiling with GCC has created a problem with the .xresources and xrdb files. The build produced a GUI that was more or less just a blank screen, no menus, buttons, graphics, etc - presumably because none of the necessary xresources were being loaded.

SOLUTION

The issue of automatically loading the xresources seems to be down to exactly how you specify that XAPPLRESDIR environment variable. According to The X Development Kit Users Guide p12. The environment variable is supposed to point to where the relevant xrdb file for that application actually is and all those various other .xrdbs that the top level one then #includes.

According To Hummingbird Exceed XDK R&D the "C" comments and "#includes" can be dynamically loaded by the server at the application run-time, even if not by a static xrdb.txt file loaded by Exceed at server startup.

Additional Information from Hummingbird Exceed XDK R&D

1. Should the xrdb syntax in Exceed support the xrdb files as supplied for the unix native versions - i.e. with the c-style comments and the #includes?

   Yes, it should support the syntax, an include files and comments. But resource file name should not have an extention like .ad, but should be the same as your app class name.

2. Is there a way to get Exceed to automatically load on demand the individual xrdb files for each application (as happens on Irix/Linux) - rather than the user having to physically integrate them into one single monolithic server-wide xrdb text file?

   You can put all resource files in directory specified by USERDIR (usually C:\Documents and Settings\All Users\Application Data\Hummingbird\Connectivity\7.10\Exceed\)
   You can specify XAPPLRESDIR as "c:\temp"in reg db under Exceed key or as env variable XAPPLRESDIR=c:\temp where c:\temp is your resource dir.

3. How important is a relative path as compared to a full path?
   Not important as long as resource files can be found.

1. To use the relative path you need to specify XAPPLRESDIR as relative to the location of the Xapp.exe in /home/Xapp/Xapp2/src/Xappresource then it will work.
   Syntax:
   XAPPLRESDIR=../../data
2. To use the absolute path you need to specify XAPPLRESDIR using a DOS/Windows-like file location, rather than a Unix-like one.
   Syntax:
   XAPPLRESDIR=C:\cygwin\home\xapp\Xapp\data