Does anyone use the gg:usr drawer? What files have been put there and into which directory?

GG:usr/include for example is the place for includes to third party system components. For example Reggae and TTEngine install their includes there.

In my case, also:
gg:usr/bin for svn, sdl-config, freetype-config...
gg:usr/lib/ for extra lib#?.a

It could also be usefull to store extra man pages and more.

Please note some people prefer to move all additional files into gg:usr/local/bin, lib, include...

Quote:
That can get nasty then :-( IMHO it was unfortunate that gg:usr was advertized as user space. The include directory will cause problems. I am working on a binutils/gcc update and it will (probably) use usr:local as installation prefix. It could continue using gg: as installation place if thats prefered. However, the location for the default includes changes from gg: to usr: because thats an internal GCC expectation for a native compiler. The change to gg: was always cumbersome. Since this clashes with the current gg:usr usage for includes, all headers from there must move. That could be usr:local/include, <prefix>/ppc-morphos/include or usr:local/os-include (through setenv C_INCLUDE_PATH). I hope that change won't cause to much confusion...

I don't know if I understood correctly what you mean, but gg:usr is == usr:

Quote:
Yes. What I wanted to say is this: the current use if this location will cause problems with a future GCC update. Thats because the default include location changes from gg: to usr: If usr: and gg: are distinct, then you must move gg:include[std] to usr and you can only do that if you move the current contents of gg:usr/include to a different place, eg. $prefix/include (might be usr:local/include or gg:include(!)), $prefix/ppc-morphos/include or $prefix/os-include. For the latter you have to use setenv C_INCLUDE_PATH.