Reference Materials. Summary

Теперь приступаем к составлению самого summary. The video “Touchable holograms” by Carlos Pineiro on the 5th of October 2010 informs on a new technology, touchable holograms, created by Japanese researchers. Nowadays, it is widely known that holograms are 3-D images produced by two beams of light. Until now they could only be seen but not touched. Researchers at Tokyo University have come up with a technology that is a first significant step away from the mouse and keyboard, touchable hologram. It is reported that this technology consists of the software that uses ultrasonic waves to create pressure on the hand of the user touching the projected hologram. The researchers also use two V-codes from the Nintendo gaming system to track a user’s hand. There is no doubt that this technology could be used for a wide variety of things ranging from light switches to books appearing when needed and disappearing when not. Besides, it might be applied in hospitals to avoid touching contaminated objects. Thus, inspired by the success the Japanese scientists still continue their work on this promising technology to make it perfect.
Most programs don’t need any pre-installation commands, but we have the feature just in case it is needed. To classify the commands in the install rule into these three categories, insert category lines among them. A category line specifies the category for the commands that follow. A category line consists of a tab and a reference to a special Make variable, plus an optional comment at the end. There are three variables you can use, one for each category; the variable name specifies the category. Category lines are no-ops in ordinary execution because these three Make variables are normally undefined (and you should not define them in the makefile). If you don’t use a category line at the beginning of the install rule, all the commands are classified as normal until the first category line. If you don’t use any category lines, all the commands are classified as normal. Typically, a pre-uninstall command would be used for deleting entries from the Info directory.
See Writing Recipes in Rules. But it will echo the following two recipe lines. On the other hand, prefix characters on the recipe line that refers to a canned sequence apply to every line in the sequence. It is sometimes useful to define recipes which do nothing. This is done simply by giving a recipe that consists of nothing but whitespace. You could also use a line beginning with a recipe prefix character to define an empty recipe, but this would be confusing because such a line looks empty. You may be wondering why you would want to define a recipe that does nothing. One reason this is useful is to prevent a target from getting implicit recipes (from implicit rules or the .DEFAULT special target; see Using Implicit Rules and see Defining Last-Resort Default Rules). Empty recipes can also be used to avoid errors for targets that will be created as a side-effect of another recipe: if the target does not exist the empty recipe ensures that make won’t complain that it doesn’t know how to build the target, and make will assume the target is out of date.
We feel it is cleaner to write each line of the recipe to stand on its own and not require this special treatment. This describes conventions for writing the Makefiles for GNU programs. Using Automake will help you write a Makefile that follows these conventions. For more information on portable Makefiles, see POSIX and Portable Make Programming in Autoconf. SHELL variable might be inherited from the environment. Different make programs have incompatible suffix lists and implicit rules, and this sometimes creates confusion or misbehavior. The first line clears out the suffix list, the second introduces all suffixes which may be subject to implicit rules in this Makefile. Don’t assume that . Without one of these prefixes, the current search path is used. ‘—srcdir’ option to configure. Some files are architecture-independent and can be shared by all machines at a site; some are architecture-dependent and can be shared only by machines of the same kind and operating system; others may never be shared between two machines.
Подробнее читайте на: http://www.news161.ru