* update TIPS

* explain, why gc/Makefile.options, gc/Makefile.gc, gc/Makefile

* update samples to use libocc-config

* make tests out of samples; write the rule to check if samples
  and examples are coherent (and warnd the developer if one has been
  changed, but not another) --- this seems necessary, since tests
  probably will have different makefiles. Or maybe we can just
  make samples to be symlinks to certain files in tests? And maybe
  we can add a rule, that runs sample's makefiles to see if they build?
  (This can be added to 'installcheck' target)

* implement installation test --- add new dependency to the 'installcheck'
  target, that after installation tries to build some small thing
  this is meant as a tool for developer to check if all headers are
  installed correctly; we could try to mimic installation in the
  build directory, but this would require handcoding all the install rules
  that Automake generates, just for the "trial" install. And this would
  increase build time, since developer would wait for "trial" installation
  of everything every time he/she wants to run tests. For now let us stick
  to the solution, where only libs are provisionally installed in 
  tmplib. To test if all the headers are installed correctly, we just
  want a small non-DejaGNU test, that is hooked to 'installcheck'.

* add automated dependency tracking (.d files or maybe Automake has
  something? How does it behave when we do a package? Will dependency
  tracking run on the user's machine (e.g. it introduces a dependency
  on 'sed'))

* have a look into threads (there is some m4 code from ICE to check for
  threads; threads were present somewhere in the old Makefiles)

* fix gc Makefile, now it rebuilds too much.

See also Task Tracker at Source Forge.


