files). Its syntax is very simple -- see the following sections.
Since make searches by default for a @file{Makefile} and not for
files). Its syntax is very simple -- see the following sections.
Since make searches by default for a @file{Makefile} and not for
-@file{Makefile.rules} or @file{Makefile.omk}, there must be a small
+@file{Makefile.rules} or @file{Makefile.omk}, there must@footnote{When
+USE_LEAF_MAKEFILES is set to @samp{n}, this @file{Makefile} can be
+omitted in subdirectories. @xref{USE_LEAF_MAKEFILES}.} be a small
generic @file{Makefile} in every directory, whose task is only to find
@file{Makefile.rules} in the actual or any parent directory and include
it. This search is performed only once at the beginning of compilation.
generic @file{Makefile} in every directory, whose task is only to find
@file{Makefile.rules} in the actual or any parent directory and include
it. This search is performed only once at the beginning of compilation.
project and don't need to modify project's original Makefiles.
This variable can be set either globally in a @file{config.*} file or
project and don't need to modify project's original Makefiles.
This variable can be set either globally in a @file{config.*} file or
parameters to interface QT application to the rest of the compilation
tree. Then @command{make} is called there to compile QT
application. Variable @samp{QTDIR} must be set to the directory with
parameters to interface QT application to the rest of the compilation
tree. Then @command{make} is called there to compile QT
application. Variable @samp{QTDIR} must be set to the directory with
@end defvar
@node System-Less, RTEMS, Linux, Properties of Specific Makefile.rules
@subsection System-Less
@end defvar
@node System-Less, RTEMS, Linux, Properties of Specific Makefile.rules
@subsection System-Less
+This @file{Makefile.rules} is deigned for compilation of code for
+(small) micro-controllers without operating systems. See
+@uref{http://rtime.felk.cvut.cz/hw/index.php/System-Less_Framework} for
+more information about our framework, which uses this rules.
+
@node RTEMS, , System-Less, Properties of Specific Makefile.rules
@subsection RTEMS
@node RTEMS, , System-Less, Properties of Specific Makefile.rules
@subsection RTEMS
@node Running OMK under Windows OS, Interfacing OMK to popular IDEs, Properties of Specific Makefile.rules, OMK User's Manual
@section Running OMK under Windows OS
@node Running OMK under Windows OS, Interfacing OMK to popular IDEs, Properties of Specific Makefile.rules, OMK User's Manual
@section Running OMK under Windows OS
+It is possible to use OMK under Windows OS with MinGW (see
+@uref{http://www.mingw.org/}). Unfortunately, the compilation speed is
+much lower than on UNIX systems.
+
+TODO: Is it necessary to install anything special?
+
@node Interfacing OMK to popular IDEs, Troubleshooting, Running OMK under Windows OS, OMK User's Manual
@section Interfacing OMK to popular IDEs
@node Interfacing OMK to popular IDEs, Troubleshooting, Running OMK under Windows OS, OMK User's Manual
@section Interfacing OMK to popular IDEs
Sometimes, you may want to compile one file the same way as OMK does
it, but run the compilation manually from command line. For example,
you want to debug some preprocessor macros and you only want to
Sometimes, you may want to compile one file the same way as OMK does
it, but run the compilation manually from command line. For example,
you want to debug some preprocessor macros and you only want to
V=2}. This will print all commands executed together with directory
navigation messages. Find the command you want to execute manually in
the output. To run it, you need to change the working directory to the
correct one in the @file{_build} tree. The correct directory can be
found in make output on the line @samp{Entering directory} preceding
the desired command.
V=2}. This will print all commands executed together with directory
navigation messages. Find the command you want to execute manually in
the output. To run it, you need to change the working directory to the
correct one in the @file{_build} tree. The correct directory can be
found in make output on the line @samp{Entering directory} preceding
the desired command.
@end itemize
@node Original README, OMK Development, OMK User's Manual, Top
@end itemize
@node Original README, OMK Development, OMK User's Manual, Top
@item
Make system should allow to freely move cross-dependant components in
directory structure without need to update users of moved component (I
@item
Make system should allow to freely move cross-dependant components in
directory structure without need to update users of moved component (I
example. If a component is renamed or version is added to then name,
all Makefiles in CAN will require update).
@item
example. If a component is renamed or version is added to then name,
all Makefiles in CAN will require update).
@item
to link tree pointing into readonly media or can be anywhere
else if @code{MAKERULES_DIR} and @code{SOURCES_DIR} are specified.
to link tree pointing into readonly media or can be anywhere
else if @code{MAKERULES_DIR} and @code{SOURCES_DIR} are specified.