1 \input texinfo @c -*-texinfo-*-
3 @setfilename omk-manual
4 @settitle OMK: Ocera Make System
8 Manual for Ocera Make System (OMK)
10 Copyright @copyright{} 2007 Michal Sojka, Pavel Pisa
14 @title Ocera Make System Manual
16 @vskip 0pt plus 1filll
23 @node Top, Overview of OMK, (dir), (dir)
24 @top Ocera Make System
38 @node Overview of OMK, OMK User's Manual, Top, Top
42 OMK is an advanced make system written entirely in GNU make. Compiling
43 software using OMK requires only GNU make binary and standard UNIX
44 utilities (@command{sh}, @command{sed}, @command{cmp} and
45 @command{tr}@footnote{@command{tr} is needed only for OMK to be
46 compatible with MinGW.}) installed. OMK aims to be developer friendly;
47 to use OMK, you do not need to understand (sometimes) cryptic syntax of
50 You can use OMK on all platforms where you can run GNU Make including
51 Cygwin and MinGW. MS DOS was not tested.
57 @c Easy to use for beginners.
59 @c Automatic handling of dependencies.
61 @c Supported host platforms: all Un*x operating system including Linux,
62 @c Cygwin, MS DOS and maybe others.
71 @node Why to Use OMK?, Quick Start, Overview of OMK, Overview of OMK
72 @section Why to Use OMK?
74 Here we list some of OMK features, which we think are important for
75 choosing of a make system.
80 Makefile in source directories are usually very @b{simple}.
82 There is only @b{one} @file{Makefile.rules} for most of components of
85 OMK greatly simplifies compilation of projects, where source files are
86 spread between @b{multiple directories}.
88 OMK handles properly @b{dependencies} of source files and libraries,
89 so it is not necessary to recompile the whole project if only several
92 OMK allows to freely @b{move} cross-dependant components @b{in
93 directory structure} without the need to update users of moved
94 component. I hate something like
95 @option{-I../../sched/rtlshwq/include} in makefiles for example. If a
96 component is renamed or version is added to the name, many Makefiles
97 in the project would require an update.
99 The above feature is very helpful in @b{combining components}
100 (libraries) from different projects/developers to a single project by
101 simply creating symbolic links to external components.
103 Compilation of an OMK based projects don't require to install any
104 files before successful finish of build.
106 OMK allows to call @command{make} for a particular subdirectory in the
109 Under OMK all products of compilation are stored @b{out of source
110 directories}. This simplifies work with version control systems and
111 helps when simultaneous compilation for multiple targets/platforms is
116 @node Quick Start, History, Why to Use OMK?, Overview of OMK
119 If you get some sources, which are distributed with OMK, usually the
120 following commands are sufficient to compile the whole project.
129 @noindent To use OMK in your own project, follow these steps:
133 Take appropriate @file{Makefile.rules}, put it together with leaf
134 @file{Makefile} to the root directory of your project.
136 Create @file{Makefile.omk} files in all directories you want to
137 compile something. Please refer to @ref{OMK User's Manual} to learn
138 what to write in @file{Makefile.omk} files.
140 Run @command{make omkize} in the root directory.
143 @noindent Your project is now ready to compile.
146 @node History, , Quick Start, Overview of OMK
149 OMK was originally written by Pavel Pisa as a solution to have one
150 common make system for OCERA project, where we needed to compile
151 user-space programs, Linux kernel modules and RT Linux modules in one
152 package. Although this system was not accepted for the whole OCERA
153 project. Several individual developers (mostly from Czech Technical
154 University) liked it and started to use it.
156 As a number of projects using OMK grew it was necessary to modularize
157 the make system to support more ``targets''. Michal Sojka took care
158 about the process of modularization.
160 @node OMK User's Manual, Original README, Overview of OMK, Top
161 @chapter OMK User's Manual
166 * Compiling Programs::
168 * Multiple Directories::
169 * Dependency Tracking::
170 * Configuration and Conditional Compilation::
171 * Advanced OMK Features::
172 * Properties of Specific Makefile.rules::
173 * Running OMK under Windows OS::
174 * Interfacing OMK to popular IDEs::
178 @node Basic Concepts, Invoking OMK, OMK User's Manual, OMK User's Manual
179 @section Basic Concepts
181 The main concept of OMK is very simple. In the root directory of the
182 projects resides a file called @file{Makefile.rules}. This file contains
183 all compilation rules needed for compilation of a particular
184 project. There are different @file{Makefile.rules} for different
185 platforms (Unix, RTEMS, system-less, ...). In every subdirectory a
186 @file{Makefile.omk} is stored. This file determines what should be done
187 in the respective directory (e.g. compile a program from several source
188 files). Its syntax is very simple -- see the following sections.
190 Since make searches by default for a @file{Makefile} and not for
191 @file{Makefile.rules} or @file{Makefile.omk}, there must be a small
192 generic @file{Makefile} in every directory, whose task is only to find
193 @file{Makefile.rules} in the actual or any parent directory and include
194 it. This search is performed only once at the beginning of compilation.
196 @c TODO: Pavel's note about qmake.
198 The compilation process itself is comprised of several passes. Every
199 pass traverses the whole directory structure@footnote{In future, we are
200 planning some optimization that allows OMK to traverse the directories
201 only once and thus decrease compilation time.} and does a particular
202 task in every directory of the project. Typically, these passes are:
204 @anchor{include-pass}
206 This pass takes all include files marked for ``export'' and copies
207 (or links) them to the @file{include} directory under
208 @file{_compiled} directory. @xref{Header Files}.
210 Also, during this pass, automatically generated header file are
211 generated according to the current
212 configuration. @xref{Configuration and Conditional Compilation}.
214 During this pass, all include files are in place, so all libraries
217 Finally, programs can be compiled and linked against libraries
218 created in the previous pass.
221 The results of compilation are stored under the @file{_compiled}
222 directory. This directory is structured as a classical Unix file-system
223 (it contains directories like @file{bin}, @file{lib} and @file{include})
224 and can be directly copied to the target device or to some directory on
225 a host computer (e.g. @file{/usr/local}).
227 Besides @file{_compiled} directory, there in a @file{_build}
228 directory. Under this directory are stored some temporary files and
229 intermediate compilation products (object files, dependency files etc.).
231 In the next section, we provide an overview of methods, how to invoke
232 OMK from command line. Section @ref{Interfacing OMK to popular IDEs}
233 covers running of OMK from popular IDEs.
235 Sections @ref{Compiling Programs} through @ref{Configuration and
236 Conditional Compilation} deals with the content of
237 @file{Makefile.omk}. Its syntax in usual cases compatible to GNU
238 Automake's @file{Makefile.am} syntax. Also, the scheme for naming
239 variables was inspired by Automake so most OMK variables have the name
240 like @samp{@var{target}_@var{TYPE}}.
242 @node Invoking OMK, Compiling Programs, Basic Concepts, OMK User's Manual
243 @section Invoking OMK
245 Before using OMK for the first time, you have to call:
247 @command{make default-config}
249 @noindent See @ref{Configuration and Conditional Compilation} for
250 details. If you forget to do this, OMK will notice you.
252 To compile the whole project or only some subtree of the project, call
256 @noindent in the appropriate directory.
258 To clean files in @file{_build} directory but not in @file{_compiled}
264 To clean the compilation completely, you can either remove
265 @file{_compiled} and @file{_build} directories manually, or call
267 @command{make distclean}
269 @noindent which does the same. This command removes these directories
270 even if you call it from a subdirectory.
272 To debug compilation problems, you can use @code{V} variable (see
278 You can also set values of some other variables on command line for
279 temporary change something. The example below compiles the code
280 temporarily with debugging information:
282 @command{make CFLAGS="-g -O0 -Wall"}
285 If your project uses an alternative make-system (e.g. Automake or custom
286 makefiles), it might be useful for you to use the command:
288 @command{make omkize}
290 @noindent This will find all @file{Makefile.omk} files in all subdirectories
291 and copies generic @file{Makefile} from the root directory to that
292 subdirectories. This way you can easily switch your project to use OMK.
298 If this variable equals to @samp{1}, the whole command lines for all
299 executed commands are displayed. When not set or zero, only short
300 messages are printed. Value of @samp{2} displays the whole command lines
301 as with @samp{1} and in addition directory navigation messages are
305 @node Compiling Programs, Libraries, Invoking OMK, OMK User's Manual
306 @section Compiling Programs
308 To tell OMK to compile a program, you need to set some variables in
309 @file{Makefile.omk} (usually) in the directory where program sources are
312 In the example bellow a program @command{test} will be compiled from
313 source @file{test.c}.
316 @verbatiminclude ../tests/programs/Makefile.omk
319 @noindent The variables are:
321 @anchor{bin_PROGRAMS}
323 Contains a list of names (whitespace separated) of programs to be
324 compiled in this directory.
327 @defvar test_PROGRAMS
328 Almost the same as @ref{bin_PROGRAMS}, but resulting binaries are
329 stored in @file{bin-tests} directory instead of @file{bin}. This
330 variable is intended for various test programs not to be mixed with
334 @defvar utils_PROGRAMS
335 Almost the same as @ref{bin_PROGRAMS}, but resulting binaries are
336 stored in @file{bin-utils} directory instead of @file{bin}. This
337 variable is intended for various development utilities not to be mixed
338 with the final product.
342 For every program name @var{xxx} in @code{bin_PROGRAMS},
343 @code{test_PROGRAMS} or @code{utils_PROGRAMS}, this variable contains
344 a list of sources that are needed to compile the program. OMK uses an
345 extension of the filename to determine the compiler to compile this
350 This variable contains a list of libraries the program @var{xxx} will
359 This variable contains a list of libraries all programs in this
360 directory needs to be linked to.
364 Directives passed to the C or C++ compiler with additional directories
365 to be searched for header files. In most cases you need to specify an
366 absolute path. To specify a directory relative to the source
367 directory, you can use the @code{$(SOURCES_DIR)} variable, which
368 refers to the directory, where @file{Makefile.omk} is located. This
369 variable applies to all compilations invoked in the current directory.
372 INCLUDES = -I$(SOURCES_DIR)/my_include_dir
377 Directives passed to the C or C++ compiler with preprocessor macro
378 definitions. This variable applies to all compilations invoked in the
387 @c FIXME: INCLUDES variable should not be set by rtlinux rules.
389 @node Libraries, Multiple Directories, Compiling Programs, OMK User's Manual
393 With OMK, you can easily create statically or dynamically linked
394 libraries. The way of creating libraries is very similar to how programs
395 are created. @xref{Compiling Programs}.
397 In @file{Makefile.omk}, you specify several variables, which defines how
398 the libraries should be compiled. In the example below the library
399 @samp{mylib} (full filename will be @file{libmylib.a}) is created from
400 two sources @file{funca.c} and @file{funcb.c}. Interface of this library
401 is defined in @file{myfunc.h}. Therfore, we export this header for use
405 @verbatiminclude ../tests/libraries/Makefile.omk
408 @noindent Variables for use with libraries are:
410 @defvar lib_LIBRARIES
411 Specifies a list of statically linked libraries to be compiled. OMK
412 automaticvally prepends @code{lib} prefix library names.
415 @defvar shared_LIBRARIES
416 Specifies a list of dynamically linked libraries to be compiled.
420 For every library name @var{xxx} in @code{lib_LIBRARIES} or
421 @code{shared_LIBRARIES}, this variable contains a list of sources that
422 are needed to compile the library. OMK uses an extension of the
423 filename to determine the compiler to compile this source.
430 @node Header Files, , Libraries, Libraries
431 @subsection Header Files
433 C and C++ libraries are not very useful without header files. OMK
434 provides several variables that specify activities on header files.
436 During compilation, header files are copied (or linked) from source
437 directories to the @file{_compiled} tree
438 (see @ref{include-pass}). Libraries and programs are then compiled against
441 @anchor{include_HEADERS}
442 @defvar include_HEADERS
443 Specifies the list of header files to be exported for use by other
444 libraries/programs. The files are exported directly to the
445 @file{include} directory even if the file is located in a subdirectory
446 (like @file{sci_regs.h} in the example below)
449 include_HEADERS = regs.h periph/sci_regs.h
453 @defvar nobase_include_HEADERS
454 Similar to @ref{include_HEADERS}, but the directory prefix is always
455 kept. To include the file exported by this variable, use
456 @code{#include <@var{prefix}/@var{header.h}>}.
459 @defvar renamed_include_HEADERS
460 Exports the header files under different name. The form of the items
461 in this whitespace separated list is: @var{real name}@code{->}@var{new
465 renamed_include_HEADERS = orte_config_omk_win32.h->orte_config.h
470 If this variable equals to @samp{y}, symbolic links to headers in
471 source directories are used in @file{_compiled} tree instead of
474 Normally, the header files are copied into @file{_compiled} directory
475 to be prepared for transfer into target location afterwards. Copying
476 ensures that resulting libraries are in correspondence with the header
477 files even if the header is changed by a developer but the library is
480 @c Another reason for having single include directory for the whole
481 @c project is tat every component knows where to find header files of
484 On the other side, the copying could make problems during
485 development. Most @acronym{IDE}s, allows you to jump directly to the
486 place, where an error is reported by the compiler. If the error is in
487 a header file, IDE opens you the copy of the header file. If you
488 correct the error there, after the next compilation, your header file
489 will be overwritten by the old version from your source tree.
491 This option is not typically used in @file{Makefile.omk}, but in the
492 top level configuration file @file{config.omk} or on command line.
495 @node Multiple Directories, Dependency Tracking, Libraries, OMK User's Manual
496 @section Multiple Directories
498 OMK is probably most useful in projects consisting of multiple
499 directories. For such projects, it is not easy to write from scratch
500 classic Makefiles that provides all the needed features.
502 You can instruct OMK to descend to a (sub)directory by setting the
503 @code{SUBDIRS} variable in @file{Makefile.omk}.
506 This variable contains a list of directories, in which compilation
507 must be also invoked. Usually, names of subdirectories are used, but
508 you can use any path specification here.
510 Compilation is invoked in these directories before it is invoked in
511 the current directory.
513 @c TODO: Write tests for this.
515 @defvar ALL_OMK_SUBDIRS
516 This variable is set by OMK and can be used as the value of
517 @code{SUBDIRS} variable. It contains a list of all direct
518 subdirectories, which contain @file{Makefile.omk}. This is especially
519 useful if you are combining several projects or components
520 together. In the root directory of your project, you just create
521 symbolic links the components from other projects and all the linked
522 directories automatically appears as the value of this variable.
525 SUBDIRS = $(ALL_OMK_SUBDIRS)
529 @node Dependency Tracking, Configuration and Conditional Compilation, Multiple Directories, OMK User's Manual
530 @section Dependency Tracking
532 OMK automatically handles tracking of dependencies of files in compiled
533 projects. It uses gcc's @option{-M@var{x}} options to do this for object
534 files. This way, whenever you change some header file, OMK recompiles
535 only those files, where the changed header was really included.
537 Dependencies are also maintained for libraries and binaries. To find the
538 dependencies, OMK parses linker map files, so a change to some library
539 causes recompilation of all programs using that library.
541 @node Configuration and Conditional Compilation, Advanced OMK Features, Dependency Tracking, OMK User's Manual
542 @section Configuration and Conditional Compilation
544 In many projects, it is necessary to configure the compilation process. By
545 this configuring we mean, setting some parameters that influence the
546 output of compilation process. In GNU projects, @command{configure}
547 script is usually responsible for configuration. User provides some
548 parameters to @command{configure}, which is run before compilation, and
549 this script does all steps needed to configure the sources and
550 make-system in the desired way.
552 OMK has its own configuration mechanism, which is described in this
553 section. For future releases, we plan that this mechanism can make use
554 of GNU Autoconf, but currently there is no directly integrated support
557 There exist three different configuration files
558 @file{config.omk-default}, @file{config.target} and
559 @file{config.omk}. All of these have to be stored in the same directory
560 as @file{Makefile.rules}. During compilation, these files are included
561 in @file{Makefile.rules} in this order which means that variables
562 assigned in the former files are overridden by those from later
563 ones. All settings specified here apply to the whole compilation
564 tree. Each file is intended for a different kind of configuration
567 @item config.omk-default
568 Stores default configuration of compiled components. This file is
569 automatically generated (see below) and should not be edited by users.
571 Stores default configuration for a project or target hardware. This
572 file is intended to be stored in a version control system and should
573 be modified only by the maintainer of the project.
575 For cross compiled projects, this file typically contains settings of
576 variables like @var{CC} and @var{CFLAGS}.
578 This is a file for end users, where any default settings set in the
579 above files can be overridden. This file should not be stored in
580 version control system. The project should compile without having this
584 Besides variables defined in @file{config.target}, @file{Makefile.omk}
585 in any subdirectory can specify some configuration parameters. When
586 @command{make default-config} is run, all these parameters are found and
587 together with their default values are stored as makefile variables in
588 @file{config.omk-default}. This file is included during compilation, so
589 if you don't specify other values, these defaults are used. If you are
590 not satisfied with these defaults, you can override the values of
591 parameters either locally for your build in @file{config.omk} or
592 globally for all people working with the project in
593 @file{config.target}.
595 @subsection Specifying Configuration Parameters
597 To specify names and default values of configuration parameters use the
598 @code{default_CONFIG} variable in @file{Makefile.omk}.
600 @defvar default_CONFIG
601 This variable contains a list of configuration parameters and their
602 default values. The format of every item in this list is
603 @var{CONFIG_xxxx}=@var{value}. You can name the parameter as you want,
604 but it is good practice to start the name with @samp{CONFIG_} prefix.
606 OMK can automatically generate header files, with C preprocessor macro
607 definitions according to the OMK's configuration parameters. The
608 actual content of generated header files depends on the form of the
609 @var{value}. The possible forms are:
612 @item @samp{y}, @samp{n} or @samp{x}
613 This defines boolean parameters. If the value of the parameter is
614 @samp{y}, the @samp{#define CONFIG_@var{xxx} 1} is generated, if it is
615 @samp{n}, no @code{#define} is generated.
617 @samp{x} is a special value called @emph{recessive 'n'}. The meaning
618 is that this parameter influences the component in the current
619 directory (i.e. the corresponding @code{#define} will be included in
620 @code{LOCAL_CONFIG_H}; see @ref{LOCAL_CONFIG_H}) but the default value
621 is not specified here. If the default value is not specified anywhere,
622 the behavior is the same as if @samp{n} is specified.
624 Numeric parameters. The define looks like @samp{#define CONFIG_@var{xxx} @var{number}}
626 Text without quotes. The define looks like @samp{#define CONFIG_@var{xxx} @var{text}}
628 Text with quotes. The define looks like @samp{#define CONFIG_@var{xxx} "@var{text}"}
632 @noindent Example of using @code{default_CONFIG}. @file{Makefile.omk} reads like:
634 @verbatiminclude ../tests/config/default/Makefile.omk
636 @noindent and @file{subdir/Makefile.omk} like:
638 @verbatiminclude ../tests/config/default/subdir/Makefile.omk
641 @noindent After running @command{make default-config}, the content of
642 @file{config.omk-default} will be:
644 @verbatiminclude ../tests/config/default/config.omk-correct
647 @subsection Using Configuration Parameters
649 Configuration parameters can be used in two ways:
652 as variables in @file{Makefile.omk} and
654 as C/C++ preprocessor macros in OMK generated header files.
657 @noindent For the first use, your @file{Makefile.omk} may contain something like:
659 SUBDIRS = arch/$(CONFIG_ARCH)
661 ifeq ($(CONFIG_DEBUG),y)
662 DEFS += -DUSE_SIMULATOR
666 @noindent For the second use, there are several variables that control
667 the generation of header files with configuration values. These
668 variables are described here:
670 @anchor{LOCAL_CONFIG_H}
671 @defvar LOCAL_CONFIG_H
672 The value of this variable is the name of a header file, which will
673 contain all configuration parameters declared in the current directory
674 by @code{default_CONFIG}. This header file is accessible only by files
675 in the current directory and it should be included like @code{#include
678 In @file{Makefile.omk}, the use of this variable can look like this:
681 LOCAL_CONFIG_H = myconfig.h
685 @defvar config_include_HEADERS
686 This variable is similar to @code{LOCAL_CONFIG_H}. One difference is
687 that the generated header file is accessible to all sub-projects in
688 all directories, not only to the files in the same directory (the
689 header is stored in @file{_compiled} tree). The second difference is
690 that you have to specify, which configuration parameters you want to
691 appear in the header file.
695 This variable determines the configuration parameters that should be
696 stored in a header file specified by
697 @code{config_include_HEADERS}. The @var{xxx} in the name of this
698 variable needs to be the same as the base name (without extension) of
702 @noindent Example of using @code{config_include_HEADERS}:
704 default_CONFIG = CONFIG_LINCAN=y CONFIG_LINCANRTL=n CONFIG_LINCANVME=n
705 config_include_HEADERS = global.h
706 global_DEFINES = CONFIG_OC_LINCAN CONFIG_OC_LINCANRTL
709 @noindent Here, we include only two out of the three configuration
710 parameters defined in the current @file{Makefile.omk}. It is also
711 possible to include configuration parameters defined in a different
714 @subsection Common Variables
716 It is common practice to use @file{config.omk} to store project-wide
717 settings. Here is the list of variables, which are commonly set here
718 (but they can also be set elsewhere, e.g. in @file{Makefile.omk}).
720 You can easily ``reconfigure'' your project by changing the
721 @file{config.omk} file. It is useful to have several configurations
722 stored in different files and let @file{config.omk} be a symbolic link
723 to the desired configuration.
727 The name of C compiler.
729 Command line options for C compiler.
731 The name of C++ compiler.
733 Additional parameters (besides @code{CFLAGS}) to by passed to C++
737 @node Advanced OMK Features, Properties of Specific Makefile.rules, Configuration and Conditional Compilation, OMK User's Manual
738 @section Advanced OMK Features
740 In this section we list several OMK features, which are more complicated
741 or rarely used so they were omitted in previous sections.
745 The @file{_compiled} directory can be shared between multiple projects
746 (by using symbolic links).
749 If you work on a bigger project, you usually don't need to rebuild the
750 whole project and call @command{make} only in a
751 subdirectory. Sometimes, it might be useful to rebuild the whole
752 project. You can either change working directory to the root of your
753 project and call @command{make} there or, as a shortcut, you can use
754 @code{W} variable (see @ref{W}) to compile everything directly from a
761 Searching for @file{Makefile.rules} works such way, that if you get
762 into sources directory over symbolic links, OMK is able to unwind your
763 steps back. This implies you can make links to component directories
764 on read-only media, copy @file{Makefile.rules}, @file{Makefile} and
765 top-level @file{Makefile.omk}, adjust @file{Makefile.omk} to contain
766 only required components and then call @command{make} in the top
767 directory or even in read-only directories after changing working
768 directory from your tree to readonly media.
774 If this variable equals to @samp{1}, the @b{whole} project is
775 (re)compiled, even if @command{make} is called from a subdirectory.
778 @anchor{USE_LEAF_MAKEFILES}
779 @defvar USE_LEAF_MAKEFILES
780 If this variable equals to @samp{n} (default is unset), then OMK uses
781 the leaf @file{Makefile} only when it is invoked by simple
782 @command{make} command. Later, during recursive directory descent leaf
783 @file{Makefile} is not used and @file{Makefile.rules} is included
786 This feature is useful if you are integrating some non-OMK project into
787 your project. You only add @file{Makefile.omk} files to the other
788 project and don't need to modify project's original Makefiles.
790 This variable can be set either globally in a @file{config.*} file or
791 locally in some @file{Makefile.omk}. In the latter case, it influences
792 only subdirectories of the directory containing @file{Makefile.omk}.
797 This variable is set internally by OMK and its value is the absolute
798 path to the directory with compiled sources. It can be used if you need
799 to refer to sources files in some custom constructs in
803 include_HEADERS = $(notdir $(wildcard $(SOURCES_DIR)/*.h))
809 The same as @ref{SOURCES_DIR}. Provided for Automake compatibility.
812 @defvar{MAKERULES_DIR}
813 This variable is set internally by OMK and its value is the absolute
814 path to the directory containing @file{Makefile.rules} currently used
818 @defvar{OMK_RULES_TYPE}
819 Identification the type of @file{Makefile.rules} used for
820 compilation. Values are like @samp{linux}, @samp{rtems}, @samp{sysless},
821 ... This variable is automatically generated during creation of
822 @file{Makefile.rules} and can be used in configuration files (see
823 @ref{Configuration and Conditional Compilation}) or in
824 @file{Makefile.omk} to tweak compilation for specific targets.
827 @node Properties of Specific Makefile.rules, Running OMK under Windows OS, Advanced OMK Features, OMK User's Manual
828 @section Properties of Specific Makefile.rules
830 In previous sections, general properties of @file{Makefile.rules} were
831 documented. This section contains documentation to features found only
832 in some particular @file{Makefile.rules}.
840 @node Linux, System-Less, Properties of Specific Makefile.rules, Properties of Specific Makefile.rules
843 This @file{Makefile.rules} is used not only for Linux as the name
844 sugest, but also for other Unices and even for Windows.
847 The name of the operating system (OS) where make was invoked.
851 Should specify the name of OS where the resulting binary should be
852 used. If not specified manually, it equals to BUILD_OS.
857 @node System-Less, RTEMS, Linux, Properties of Specific Makefile.rules
858 @subsection System-Less
860 @node RTEMS, , System-Less, Properties of Specific Makefile.rules
864 @node Running OMK under Windows OS, Interfacing OMK to popular IDEs, Properties of Specific Makefile.rules, OMK User's Manual
865 @section Running OMK under Windows OS
867 @node Interfacing OMK to popular IDEs, Troubleshooting, Running OMK under Windows OS, OMK User's Manual
868 @section Interfacing OMK to popular IDEs
872 KDevelop has support for custom build systems. To use KDevelop to
873 develop projects using OMK follow these steps. These steps are valid for
874 version 3.5.0 of KDevelop, but for previous versions it doesn't differ
879 Import project to KDevelop (from menu choose @emph{Project---Import
880 existing project}). Select the type of project to @emph{Generic C
881 Application (Custom Buildsystem)}.
887 Then answer to following dialogs as you want.
892 @image{kdevelop3} @image{kdevelop4}
896 If you are working only on some small part of the bigger project, you
897 usually don't want to recompile the whole project every time. In
898 @emph{Project---Project Options}, you can specify the subdirectory where to
905 If you want to switch between several configurations easily (see also
906 @ref{Configuration and Conditional Compilation}), in the same dialog
907 you can add @option{-e} to make options. This makes environment variables
908 have higher precedence than those in @file{config.omk-default}. Then,
909 you can define several environments with different
910 @code{CONFIG_@var{xxx}} variables and their values.
916 You can easily switch the configurations from @emph{Build---Make
926 @subsection Emacs, VIM, etc.
928 Since OMK compilation is started by executing @command{make} command,
929 many common editors can work easily with OMK.
931 Under Emacs, you can use @command{compile} or @command{recompile}
932 commands as you are used to do.
934 @node Troubleshooting, , Interfacing OMK to popular IDEs, OMK User's Manual
935 @section Troubleshooting
939 If you rename some file or directory and then you can't compile your
940 project, call @command{make clean} in the directory with errors. The
941 reason for this behavior is that OMK remembers dependencies of every
942 file. After renaming something, the original name is still stored in
943 dependencies, but make doesn't know how to create this non-existent
947 Sometimes, you may want to compile one file the same way as OMK does
948 it, but run the compilation manually from command line. For example,
949 you want to debug some preprocessor macros and you only want to
950 produce preprocessed source instead of object file.
952 To compile something manually, you can run OMK with @command{make
953 V=2}. This will print all commands executed together with directory
954 navigation messages. Find the command you want to execute manually in
955 the output. To run it, you need to change the working directory to the
956 correct one in the @file{_build} tree. The correct directory can be
957 found in make output on the line @samp{Entering directory} preceding
961 @node Original README, OMK Development, OMK User's Manual, Top
962 @chapter Original README
964 Since this manual still doesn't cover all aspects of OMK, we include
965 here a @file{README.rules} file, which was written for the first version
968 @b{Important notice:} This make system uses features found in recent
969 versions of GNU Make program. If you encounter problems with package
970 building, check, that you use correct version of Make program. The
971 Make older than version 3.80, could not be used. Even Make version
972 3.80 has annoying bug which causes building fail with misleading
973 message "virtual memory exhausted". Please, upgrade at least to
974 version 3.81 of GNU Make.
976 There is list of features which we want to solve with our make system:
979 Central @file{Makefile.rules} for most of components of a bigger project.
981 FIXME (our CAN framework includes more libraries common with our other
982 projects, we need to separate some utility libraries etc.)
984 The rules in more spread Makefiles are way to the hell (update for
985 different kernel, RT-Linux etc would be nightmare in other case).
987 Make system should allow to freely move cross-dependant components in
988 directory structure without need to update users of moved component (I
989 hate somethink like @option{-I../../sched/rtlshwq/include} in CAN makefiles for
990 example. If a component is renamed or version is added to then name,
991 all Makefiles in CAN will require update).
993 Make system should be able to compile mutually cross-dependant
994 libraries and should ensure, that change in one component sources or
995 headers would result in relink or rebuild in components linked against
996 that library or including modified header file.
998 Make system has to enable compilation out of OCERA full source tree
999 (we would lost many users of particular components in other case).
1001 Compile should be able to do all above work without need to install
1002 any files before successful finish of build.
1004 Because we use some libraries for RT-Linux build and user-space build,
1005 we need to solve how to compile from same sources to both targets.
1007 The build system should allow to call make for particular source
1008 subdirectory. Time of recursive make through all subdirectories is
1011 Make system should enable to build out of sources tree (else clean or
1012 working with CVS sandbox gets fussy and simultaneous multiple targets
1015 It would be good, if there is a possibility to call make from
1016 read-only media sources.
1018 Make system should store results of build in some separate directory
1019 structure to simple install and testing.
1021 Makefiles in sources directories should be simple.
1024 There is probably only one alternative fully supporting above requirements
1025 and it is GNU Autoheader...Automake...Autoconf... system.
1026 But it is complicated and requires big amount of support files.
1027 It would be acceptable if it could be easily used for OCERA framework.
1028 But there are important show stoppers for that system:
1031 It would require deep revision of all OCERA CVS contents and agreement
1032 on this would be problematic
1034 This system is not well prepared for dual compilation for Linux and
1035 RT-Linux sub-targets. It would mean many changes in default autoconf
1036 setup to support this. Probably simplest way would be to rebuild GCC
1037 tool chain for something like i586-elf-rtlinux. This would require
1038 even more space for OCERA development.
1041 The problem calls for some solution, which would have minimal impact
1042 on other components and would be elegant and would be maintainable
1043 and small, because our main goal is components development and not
1044 make systems development.
1046 There is result of our trial. It is OMK make system.
1047 The @file{Makefile} and @file{Makefile.omk} files should be in all source
1048 directories. Common @file{Makefile.rules} file is required in the toplevel
1049 sources directory. Alternatively this file could be moved
1050 to link tree pointing into readonly media or can be anywhere
1051 else if @code{MAKERULES_DIR} and @code{SOURCES_DIR} are specified.
1053 @c !!! tohle tam nejak zmizelo, mozna by to chtelo skontrolovat, ze to
1054 @c sedi s aktualnim stavem
1057 Syntax of Makefile.omk files is for usual cases compatible
1058 to Automake's Makefile.am descriptions. There are specific targets
1059 for RT-Linux and Linux kernel related stuff
1061 Makefile.omk user defined variables
1064 list of subdirectories intended for make from actual directory
1066 list of the user-space libraries
1067 @item shared_LIBRARIES
1068 list of the user-space shared libraries
1069 @item kernel_LIBRARIES
1070 list of the kernel-space libraries
1071 @item rtlinux_LIBRARIES
1072 list of the RT-Linux kernel-space libraries
1073 @item include_HEADERS
1074 list of the user-space header files
1075 @item nobase_include_HEADERS
1076 headers copied even with directory part
1077 @item kernel_HEADERS
1078 list of the kernel-space header files
1079 @item rtlinux_HEADERS
1080 list of the RT-Linux kernel-space header files
1082 list of the require binary programs
1083 @item utils_PROGRAMS
1084 list of the development utility programs
1085 @item kernel_MODULES
1086 list of the kernel side modules/applications
1087 @item rtlinux_MODULES
1088 list of RT-Linux the kernel side modules/applications
1090 list of specific target sources
1092 additional include directories and defines for user-space
1093 @item kernel_INCLUDES
1094 additional include directories and defines for kernel-space
1095 @item rtlinux_INCLUDES
1096 additional include directories and defines for RT-Linux
1097 @item default_CONFIG
1098 list of default config assignments CONFIG_XXX=y/n ...
1101 The Makefile is same for all sources directories and is only 14 lines
1102 long. It is there only for convenience reasons to enable call "make"
1103 from local directory. It contains code which locates
1104 @file{Makefile.rules} in actual or any parent directory. With standard
1105 BASH environment it works such way, that if you get into sources
1106 directory over symbolic links, it is able to unwind yours steps back
1107 => you can make links to readonly media component directories, copy
1108 @file{Makefile.rules}, Makefile and toplevel Makefile.omk, adjust
1109 Makefile.omk to contain only required components and then call make in
1110 top or even directories after crossing from your tree to readonly
1113 The system compiles all files out of source directories. The actual
1114 version of system is adapted even for OCERA tree mode if
1115 @code{OCERA_DIR} variable is defined in @file{Makefile.rules}
1117 There are next predefined directory name components, which can be
1121 @item BUILD_DIR_NAME = _build
1122 prefix of directory, where temporary build files are stored
1123 @item COMPILED_DIR_NAME = _compiled
1124 prefix of directory, where final compilation results are stored
1125 @item GROUP_DIR_NAME = yyy
1126 this is used for separation of build sub-trees in OCERA environment
1127 where more @file{Makefile.rules} is spread in the tree
1130 Next directories are used:
1133 @item KERN_BUILD_DIR := $(MAKERULES_DIR)/$(BUILD_DIR_NAME)/kern
1134 directory to store intermediate files for kernel-space targets
1135 @item USER_BUILD_DIR := $(MAKERULES_DIR)/$(BUILD_DIR_NAME)/user
1136 directory to store intermediate files for user-space targets
1138 @item USER_INCLUDE_DIR := $(MAKERULES_DIR)/$(COMPILED_DIR_NAME)/include
1139 directory to store exported include files which should be installed later
1140 on user-space include path
1141 @item USER_LIB_DIR := $(MAKERULES_DIR)/$(COMPILED_DIR_NAME)/lib
1142 same for user-pace libraries
1143 @item USER_UTILS_DIR := $(MAKERULES_DIR)/$(COMPILED_DIR_NAME)/bin-utils
1144 utilities for testing, which would not probably be installed
1145 @item USER_BIN_DIR := $(MAKERULES_DIR)/$(COMPILED_DIR_NAME)/bin
1146 binaries, which should go into directory on standard system PATH
1147 (/usr/local/bin, /usr/bin or $(prefix)/bin)
1149 @item KERN_INCLUDE_DIR := $(MAKERULES_DIR)/$(COMPILED_DIR_NAME)/include-kern
1150 directory to store exported include files which should be installed later
1151 on kernel-space include path
1152 @item KERN_LIB_DIR := $(MAKERULES_DIR)/$(COMPILED_DIR_NAME)/lib-kern
1153 same for kernel-pace libraries
1154 @item KERN_MODULES_DIR := $(MAKERULES_DIR)/$(COMPILED_DIR_NAME)/modules
1155 builded modules for Linux kernel or RT-Linux system
1158 There is more recursive passes through directories to enable
1159 mutual dependant libraries and binaries to compile.
1160 Next passes are defined
1163 @item default-config
1164 generates @file{config.omk-default} or xxx-default (FIXME) configuration file
1166 checks and creates required build directories
1168 copies header files to @code{USER_INCLUDE_DIR} and @code{KERN_INCLUDE_DIR}
1170 builds objects in USER_BUILD_DIR/@var{relative path} and creates libraries
1172 @item binary-pass and utils-pass
1173 links respective binaries in USER_@{BIN,UTILS@}_DIR directory. If some
1174 object file is missing it compiles it in USER_BUILD_DIR/@var{relative path}
1175 @item kernel-lib-pass
1176 builds libraries for kernel space targets
1178 builds kernel modules
1181 The amount of passes is relatively high and consumes some time. But
1182 only other way to support all required features is to assemble one big
1183 toplevel Makefile, which would contain all components and targets
1186 Drawbacks of designed make system
1189 the system is not as fast as we would like
1191 it lacks Autoconf and configure extensive support for many systems
1192 from UNIX to DOS and WINDOWS
1194 it does not contain support for checking existence of target
1195 libraries and functionalities as GNU Autoconf
1197 it is heavily dependant on GNU MAKE program. But it would not be big
1198 problem, because even many commercial applications distribute GNU MAKE
1199 with them to be able to work in non-friendly systems
1201 the key drawback is dependence on recent MAKE version 3.80 and better
1202 and even version 3.80 of MAKE has important bug, which has been
1203 corrected in newer sources (FIXME)
1206 The last point is critical. I have not noticed it first, because
1207 I use Slackware-9.2 and it contains latest released version
1208 of MAKE (version 3.80).
1209 The problem appears when I have tried to build bigger libraries.
1210 There is bug in version 3.80, which results in misleading
1211 error "Virtual memory exhausted". It is known bug with ID 1517
1214 * long prerequisite inside eval(call()) => vm exhausted, Paul D. Smith
1218 I have optimized some rules to not push memory to the edge,
1219 but there could be still issues with 3.80 version.
1221 I have downloaded latest MAKE CVS sources. The compilation required
1222 separate lookup and download for .po files and full Autoheader... cycle.
1223 I have put together package similar to release. Only ./configure --prefix=...
1224 and make is required. CVS sources contains version 3.81beta1.
1225 You can download prepared sources archive from
1226 @indicateurl{http://paulandlesley.org/make/make-3.81beta1.tar.bz2}
1227 Or you can get our local copy from
1228 @indicateurl{http://cmp.felk.cvut.cz/~pisa/can/make-3.81beta1.tar.gz}
1230 The archive contains even "make" binary build by me, which should work
1231 on other Linux distributions as well. Older version of MAKE (3.79.x
1232 released about year 2000) found on Mandrake and RedHat are not
1233 sufficient and do not support eval feature. I do not expect, that
1234 Debian would be more up-to-date or contain fixes to MAKE vm exhausted
1237 The local CTU archive with our CAN components prepared for inclusion
1238 into OCERA SF CVS could be found in my "can" directory
1240 @indicateurl{http://cmp.felk.cvut.cz/~pisa/can/ocera-can-031212.tar.gz}
1242 The code should build for user-space with new make on most of Linux distros
1243 when make is updated.
1245 If you want to test compile for RT-Linux targets, line
1248 #RTL_DIR := /home/cvs/ocera/ocera-build/kernel/rtlinux
1251 in @file{Makefile.rules} has to be activated and updated
1252 to point RT-Linux directory containing "rtl.mk".
1253 There is only one library ("ulutrtl") and test utility compiled for RT-Linux
1254 (@file{can/utils/ulut/ul_rtlchk.c}).
1256 The next line, if enabled, controls compilation in OCERA project tree
1259 #OCERA_DIR := $(shell ( cd -L $(MAKERULES_DIR)/../../.. ; pwd -L ) )
1262 The LinCAN driver has been updated to compile out of source directories.
1264 Please, check, if you could compile CAN package and help us with integration
1265 into OCERA SF CVS. Send your comments and objections.
1267 The OMK system has been adapted to support actual OCERA configuration process.
1268 I am not happy with ocera.mk mix of defines and poor two or three rules,
1269 but OMK is able to overcome that.
1271 The OMK system has integrated rules (default-config) to build default
1272 configuration file. The file is named @file{config.omk-default} for
1273 the stand-alone compilation. The name corresponds to OCERA config +
1274 "-default" if OCERA_DIR is defined. This file contains statements
1275 from all @code{default_CONFIG} lines in all @file{Makefile.omk}. The
1276 file should be used for building of own @file{config.omk} file, or as
1277 list for all options if Kconfig is used.
1279 @c @chapter OMK Reference
1281 @node OMK Development, Variable Index, Original README, Top
1282 @chapter OMK Development
1286 @node Variable Index, , OMK Development, Top
1287 @unnumbered Variable Index
1291 @c @node Concept Index, , Variable Index, Top
1292 @c @unnumbered Concept Index