PageRenderTime 7ms CodeModel.GetById 1ms app.highlight 2ms RepoModel.GetById 2ms app.codeStats 0ms

/src/wrappers/glib/examples/quark_example.ace

http://github.com/tybor/Liberty
Unknown | 176 lines | 138 code | 38 blank | 0 comment | 0 complexity | 94e82257bdeeeb394829c40bd392d7c7 MD5 | raw file
  1system "quark_example"
  2		-- Replace SYSTEM_NAME with the name of the executable file
  3		-- to be generated for your system. (This is the equivalent of
  4		-- the -o flag in traditional command line mode.)
  5
  6root
  7
  8 QUARK_EXAMPLE: make
  9		-- Replace ROOT_CLASS and creation_procedure with the names of the
 10		-- root class and the root creation procedure for your system.
 11
 12default -- section of the system
 13
 14	assertion (all);
 15		-- The default level of assertion checking for the system.
 16		-- Choose the appropriate value: boost, no, require, ensure,
 17		-- invariant, loop, check, all.
 18
 19	assertion_flat_check (no);
 20		-- In flat mode each assertion will be executed in no_check mode.
 21		-- This means that while checking assertion, no other assertion will
 22		-- be checked. This mode has only sense in assertion modes from
 23		-- require to debug.
 24
 25	debug (yes);
 26		-- The default debug level for the system.
 27		-- Choose yes, no, or any "key" you wish.
 28
 29	trace (no);
 30		-- The default trace mode for the system. Choose yes or no.
 31
 32	collect (yes);
 33		 -- Choose yes here to add garbage collector support to your system.
 34		 -- Choose no here to indicate that you don't want the garbage collector
 35		 -- to be included in your system; no is the equivalent of the -no_gc
 36		 -- flag in traditional command line mode.
 37
 38	no_style_warning (no);
 39		 -- My humble opinion is that you should always write no here.
 40		 -- Yes is the equivalent of the -no_style_warning flag in traditional
 41		 -- command line mode.
 42
 43	no_warning (no);
 44		 -- My humble opinion is that you should always write no here.
 45		 -- Yes is the equivalent of the -no_warning flag in traditional
 46		 -- command line mode.
 47
 48	verbose (no);
 49		 -- The equivalent of the -verbose flag. (Also note that the -verbose
 50		 -- flag is still accepted in ACE file mode.)
 51
 52	manifest_string_trace (yes);
 53		 -- The equivalent of the -manifest_string_trace flag.
 54
 55	high_memory_compiler (no);	
 56		 -- The equivalent of the -high_memory_compiler flag.
 57
 58	profile (yes);
 59		 -- The equivalent of the -profile flag.
 60
 61	relax (yes);
 62		 -- The equivalent of the -relax flag.
 63
 64cluster -- section
 65	current: "."
 66	glib: "${eiffel_libraries}/eiffel-glib/loadpath.se"
 67	standard: "${path_lib}/loadpath.se"
 68
 69external -- section for elements written in another language
 70	-- Directories where to search for C .h files:
 71	-- external_header_path: "/usr/local/expat/include /usr/local/include/mjpegtools"
 72	--external_header_path: "$(pkg-config --cflags glib-2.0)"
 73
 74
 75	-- External object files to be considered; update and uncomment the
 76	-- following line:
 77	-- external_object_files: "foo.o bar.o"
 78
 79	-- External C files to be considered; update and uncomment the
 80	-- following line:
 81	-- external_c_files: "foo.c bar.c"
 82
 83	-- External C++ files to be considered; update and uncomment the
 84	-- following line:
 85	-- external_c_plus_plus_files: "foo.cpp bar.cpp"
 86
 87	-- The equivalent of the -cecil flag of the traditional command line mode.
 88	-- To indicate some cecil file to be considered, update and uncomment
 89	-- the following lines:
 90	-- cecil ("my_cecil_file1.se")
 91	-- cecil ("my_cecil_file2.se")
 92	-- cecil ("my_cecil_file3.se")
 93	-- ...
 94
 95	-- External libraries directory path to be considered; update and uncomment
 96	-- the following line:
 97	--external_lib_path: "	$(pkg-config --cflags --libs glib-2.0)"
 98
 99	-- From release -0.74Beta#20 and later SmartEiffel supports linker
100	-- external_lib_path. Just leave out the -L:
101	-- external_lib_path: "/usr/local /foo/bar"
102	-- In this case external_lib_path will work on Windows too.
103
104	-- External libraries to be considered; update and uncomment the following
105	-- line:
106	--external_lib: "$(pkg-config --libs glib-2.0)"
107
108	-- or linker independent:
109	-- external_lib: "m X11"
110
111generate -- section
112
113	no_strip(no);
114	-- Yes would mean that you don't want to run "strip" on the generated
115	-- executable. This is the equivalent of the -no_strip flag of the
116	-- traditional command line mode. (I.e. to use a C level debugger on your
117	-- system, you should choose yes here).
118
119	no_split(no);
120	-- Yes would mean that you want one big single C file for the complete
121	-- system, pinstead of the many small C files produced by default ("no").
122	-- This may be useful for delivery of the most efficient version. (Some
123	-- C compilers including gcc can then do better inlining.)
124
125	clean(no);
126	-- Yes would mean that you want to remove all generated C files, all
127	-- generated object files as well as other temporary files generated
128	-- during the compilation process. (See also command clean.)
129
130	-- The equivalent of the -cc flag of the traditional command line mode.
131	-- To select a different C compiler from the default, update and uncomment
132	-- the following line:
133	-- cc : "gcc"
134
135	-- To decide which C compiler options are to be passed, you need to use
136	-- this keyword as well as a good understanding of your C compiler.
137	-- Update and uncomment the following line:
138	c_compiler_options : "$(pkg-config --cflags glib-2.0)"
139
140	-- Some options are to be passed only to the linker. Update and uncomment
141	-- the following line:
142	linker_options : "$(pkg-config --libs glib-2.0)"
143
144	-- For the equivalent of the -no_main flag of the traditional command line
145	-- mode, uncomment the following line:
146	-- no_main (yes)
147
148	-- For the equivalent of the -gc_info flag of the traditional command line
149	-- mode, uncomment the following line:
150	-- gc_info (yes)
151
152	-- For the equivalent of the -wedit flag of the traditional command line
153	-- mode. To Include support for the Wedit debugger uncomment the following
154	-- line:
155	-- wedit (yes)
156
157
158-- Additional information about system environment variables:
159--    Inside manifest strings, you are allowed to use system
160--    environment variables using the same notation as in the traditional
161--    "loadpath.se" files. Actually, this notation is inspired by the
162--    traditional UNIX bracketed notation as for example: ${FOO} or ${Bar}
163--    or ${SmartEiffel}.
164--
165-- Additional information about the ${SmartEiffelDirectory} variable:
166--    If not explicitely set by the user, the ${SmartEiffelDirectory} variable
167--    is automatically computed using the value of the ${SmartEiffel} variable.
168--    (Keep in mind that the ${SmartEiffel} variable is mandatory for using
169--    SmartEiffel.)  The computed value indicates the SmartEiffel main
170--    directory. For example, if the value of ${SmartEiffel} is
171--    "/usr/local/lib/SmartEiffel/sys/system.se"
172--    the computed value is "/usr/local/lib/SmartEiffel/". This automatically
173--    defined variable ${SmartEiffelDirectory} is useful for indicating the
174--    location of the SmartEiffel standard library.
175--
176end