PageRenderTime 26ms CodeModel.GetById 17ms app.highlight 3ms RepoModel.GetById 2ms app.codeStats 0ms

/src/wrappers/gobject/examples/g_value_example.ace

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