There are unit tests that do not use URE, e.g., in cppuhelper.

This reverts commit 33e9f3d3.

Conflicts:

	sot/CppunitTest_sot_test_sot.mk
	svl/CppunitTest_svl_urihelper.mk

It does not actually _set_ the command line arguments, but rather _adds_
to them. IMHO the new name reflects this fact better.

Or is there any use case where we would need to use UNO API headers, but
not require the appropriate type database at runtime?

udkapi.rdb, resp. xml/services.rdb were not added to UNO_TYPES, resp.
UNO_SERVICES env. var. in all cases.

This reverts commit f52138de. It was the cause
of infinite recursive loops (huh, why, that was obvious!).

Barcode 1.3.5.0 release:

* LibreOffice 3.4.x-3.5.x support
* Resizeable barcodes
* CODE128 fix

dmake stuff removed

Naming convention for gbuild methods:
- "add" is used for stuff that is logically a part of the target
  (i.e. not registered at the Module, but defined in the target's makefile)
- "use" is used for stuff that is logically a different target
  (i.e. it is registered at the Module, has it's own makefile, may be
  in a different module than the target)

This decreases debug build dir size by about 0.5G for gcc and 1G for clang.

The 'linked' files are not used by anything, and they just waste space.
If somebody wants them for debugging or whatever reason, use --backup.