2 // vim: set syntax=asciidoc:
7 Overall, these coding style rules are here to help you to add new files in
8 OpenADK or refactor existing ones.
10 [[writing-rules-config-in]]
15 +Config.in+ files contain entries for almost anything configurable in
16 OpenADK. Mostly all Config.in files for packages are autogenerated and
17 should not be manually edited. The following rules apply for the top level
18 Config.in, for the files in target/config and target/linux/config.
20 An entry has the following pattern:
25 select BR2_PACKAGE_LIBBAR
26 depends on ADK_PACKAGE_LIBBAZ
29 This is a comment that explains what foo is.
34 * The +bool+, +depends on+, +default+, +select+ and +help+ lines are indented
37 * The help text itself should be indented with one tab and two
40 The +Config.in+ files are the input for the configuration tool
41 used in OpenADK, which is an enhanced version of _Kconfig_. For further
42 details about the _Kconfig_ language, refer to
43 http://kernel.org/doc/Documentation/kbuild/kconfig-language.txt[].
50 * Header: The file starts with a license header.
53 # This file is part of the OpenADK project. OpenADK is copyrighted
54 # material, please see the LICENCE file in the top-level directory.
57 * Assignment: use +:=+ or ++=+ followed by two tabs:
65 * Indentation: use tab only:
69 $(CP) $(WRKINST)/usr/lib/libfoo*.so* \
70 $(IDIR_LIBFOO)/usr/lib
74 * Optional dependency:
76 ** Prefer multi-line syntax.
78 ifeq ($(ADK_PACKAGE_LIBFOO_WITH_PYTHON),y)
79 CONFIGURE_ARGS+= --with-python-support
81 CONFIGURE_ARGS+= --without-python-support
88 The documentation uses the
89 http://www.methods.co.nz/asciidoc/[asciidoc] format.
91 For further details about the http://www.methods.co.nz/asciidoc/[asciidoc]
92 syntax, refer to http://www.methods.co.nz/asciidoc/userguide.html[].