Configuration file - Revision history

Hzwakenberg at 21:56, 21 December 2021

2021-12-21T21:56:19Z

← Older revision		Revision as of 23:56, 21 December 2021
Line 27:		Line 27:
	== File syntax ==		== File syntax ==

−	The file ~~is written using~~ a simple text format. It is split up into sections that each begin with a word between square brackets on a single line. Each section ~~is comprised~~ of key-value pairs separated by a colon.	+	The configuration file uses a simple text format. It is split up into sections that each begin with a word between square brackets on a single line. Each section consists of key-value pairs separated by a colon.

	Example:		Example:

Hzwakenberg at 07:31, 25 September 2018

2018-09-25T07:31:26Z

← Older revision		Revision as of 09:31, 25 September 2018
Line 1:		Line 1:
−	Most Liberty Eiffel tools need some kind of configuration which is stored in a unique file to ~~allow~~ the user ~~not~~ ~~too~~ ~~have~~ ~~over-~~long command lines. This is named '''liberty.cfg''' on windows systems and '''liberty.se''' on unix-like systems.	+	Most Liberty Eiffel tools need some kind of configuration which is stored in a unique file to prevent the user from having to use overly long command lines. This is named '''liberty.cfg''' on windows systems and '''liberty.se''' on unix-like systems.

	In particular it contains		In particular it contains
Line 10:		Line 10:
	An initial version of this configuration is generated by [[install\|the installation tool]] of Liberty Eiffel.		An initial version of this configuration is generated by [[install\|the installation tool]] of Liberty Eiffel.

−	== Where is this configuration ==	+	== Where is this configuration file stored? ==
	It is possible to have several configuration files, which are treated by priority and more specific files can override the settings from the general ones. The lowest priority is attributed to system-wide files, while user-specific (e.g. <tt>~/.serc</tt>) and session-specific (the <tt>Liberty</tt> environment variable) get higher priority. In case a configuration location is a directory, all the entries of the directory are merged (or to be accurate: all entries are handled with priority defined via alphabetical sort of the names). All that because of some distributions like to add/remove files instead of grep'ing and sed'ing huge configuration file.		It is possible to have several configuration files, which are treated by priority and more specific files can override the settings from the general ones. The lowest priority is attributed to system-wide files, while user-specific (e.g. <tt>~/.serc</tt>) and session-specific (the <tt>Liberty</tt> environment variable) get higher priority. In case a configuration location is a directory, all the entries of the directory are merged (or to be accurate: all entries are handled with priority defined via alphabetical sort of the names). All that because of some distributions like to add/remove files instead of grep'ing and sed'ing huge configuration file.
	Default configuration file locations:		Default configuration file locations:
Line 27:		Line 27:
	== File syntax ==		== File syntax ==

−	The file is written using a simple text format. It is split in sections that each begin with a word between square brackets on a single line. Each section is comprised of key-value pairs separated by a colon.	+	The file is written using a simple text format. It is split up into sections that each begin with a word between square brackets on a single line. Each section is comprised of key-value pairs separated by a colon.

	Example:		Example:
Line 109:		Line 109:
	=== Tools ===		=== Tools ===

−	All ~~the~~ tools used by the [[se]] command are set here. These tools must be in the directory pointed to by the <tt>bin</tt> key of the <tt>[General]</tt> section. The key is used as first argument of [[se]].	+	All tools used by the [[se]] command are set here. These tools must be in the directory pointed to by the <tt>bin</tt> key of the <tt>[General]</tt> section. The key is used as first argument of [[se]].

	The [[install\|installation tool]] installs the following default commands:		The [[install\|installation tool]] installs the following default commands:

Hzwakenberg: "Elate" support was removed appropriately a year ago

2017-02-18T09:57:02Z

"Elate" support was removed appropriately a year ago

← Older revision		Revision as of 11:57, 18 February 2017
Line 20:		Line 20:
	\| Unix and Cygwin:		\| Unix and Cygwin:
	\| <TT>/etc/serc</TT>, <TT>/etc/xdg/liberty-eiffel</TT>, '''<TT>/etc/liberty-eiffel</TT>''', <TT>/usr/local/etc/liberty-eiffel</TT>, '''<TT>~/.config/liberty-eiffel</TT>''', <TT>~/.serc</TT> <TT>~/.liberty-eiffel</TT> (look-up in this order, XDG_CONFIG_HOME is taken into account to adjust the paths)		\| <TT>/etc/serc</TT>, <TT>/etc/xdg/liberty-eiffel</TT>, '''<TT>/etc/liberty-eiffel</TT>''', <TT>/usr/local/etc/liberty-eiffel</TT>, '''<TT>~/.config/liberty-eiffel</TT>''', <TT>~/.serc</TT> <TT>~/.liberty-eiffel</TT> (look-up in this order, XDG_CONFIG_HOME is taken into account to adjust the paths)
−	\|-
−	\| Elate:
−	\| <TT>/lang/eiffel/serc</TT>
	\|}		\|}
	The suggested directories are '''bold'''.		The suggested directories are '''bold'''.

Ramack at 19:34, 17 February 2017

2017-02-17T19:34:26Z

← Older revision		Revision as of 21:34, 17 February 2017
Line 1:		Line 1:
−	Most Liberty Eiffel tools need some kind of configuration which is stored in a unique file to allow the user not too have over-long command lines. This is named liberty.cfg on windows systems and liberty.se on unix-like systems.	+	Most Liberty Eiffel tools need some kind of configuration which is stored in a unique file to allow the user not too have over-long command lines. This is named '''liberty.cfg''' on windows systems and '''liberty.se''' on unix-like systems.

	In particular it contains		In particular it contains

Ramack: Ramack moved page Configuration file - liberty.cfg to Configuration file

2017-02-17T19:34:05Z

Ramack moved page Configuration file - liberty.cfg to Configuration file

← Older revision	Revision as of 21:34, 17 February 2017
(No difference)

Ramack at 19:33, 17 February 2017

2017-02-17T19:33:10Z

← Older revision		Revision as of 21:33, 17 February 2017
Line 1:		Line 1:
−	Most Liberty Eiffel tools need some kind of configuration which is stored in a unique file to allow the user not too have over-long command lines ;-)	+	Most Liberty Eiffel tools need some kind of configuration which is stored in a unique file to allow the user not too have over-long command lines. This is named liberty.cfg on windows systems and liberty.se on unix-like systems.

	In particular it contains		In particular it contains

Dkearns: s/LibertyEiffel/Liberty Eiffel/

2016-06-16T11:05:27Z

s/LibertyEiffel/Liberty Eiffel/

← Older revision		Revision as of 13:05, 16 June 2016
Line 1:		Line 1:
−	Most ~~LibertyEiffel~~ tools need some kind of configuration which is stored in a unique file to allow the user not too have over-long command lines ;-)	+	Most Liberty Eiffel tools need some kind of configuration which is stored in a unique file to allow the user not too have over-long command lines ;-)

	In particular it contains		In particular it contains
Line 8:		Line 8:
	* C-compiler options for each c_mode		* C-compiler options for each c_mode

−	An initial version of this configuration is generated by [[install\|the installation tool]] of ~~LibertyEiffel~~.	+	An initial version of this configuration is generated by [[install\|the installation tool]] of Liberty Eiffel.

	== Where is this configuration ==		== Where is this configuration ==
Line 53:		Line 53:
	\|-		\|-
	\| valign="top" \| <TT>sys</TT>		\| valign="top" \| <TT>sys</TT>
−	\| the path to the ~~LibertyEiffel~~ system files. This path is used by [[compile_to_c]]. It contains all the basic files included by those compilers. They define the "basic bricks" of the generated Eiffel system.	+	\| the path to the Liberty Eiffel system files. This path is used by [[compile_to_c]]. It contains all the basic files included by those compilers. They define the "basic bricks" of the generated Eiffel system.
	\|-		\|-
	\| valign="top" \| <TT>short</TT>		\| valign="top" \| <TT>short</TT>
Line 59:		Line 59:
	\|-		\|-
	\| valign="top" \| <TT>os</TT>		\| valign="top" \| <TT>os</TT>
−	\| the type of the operating system ~~LibertyEiffel~~ is installed on. The recognized types are: UNIX, Windows, Cygwin, BeOS, Macintosh, Amiga, DOS, OS2, OpenVMS, Elate.	+	\| the type of the operating system Liberty Eiffel is installed on. The recognized types are: UNIX, Windows, Cygwin, BeOS, Macintosh, Amiga, DOS, OS2, OpenVMS, Elate.
	\|-		\|-
	\| valign="top" \| <TT>flavor</TT>		\| valign="top" \| <TT>flavor</TT>
Line 75:		Line 75:
	=== The Environment section ===		=== The Environment section ===

−	The environment section allows you to define ''environment variables'' specific to ~~LibertyEiffel~~. In particular these variables are available in the remaining of the configuration file, in the <tt>loadpath.se</tt> files, ACE files and some command line arguments.	+	The environment section allows you to define ''environment variables'' specific to Liberty Eiffel. In particular these variables are available in the remaining of the configuration file, in the <tt>loadpath.se</tt> files, ACE files and some command line arguments.

	The [[install\|installation tool]] installs the following default variables:		The [[install\|installation tool]] installs the following default variables:

Hzwakenberg at 07:32, 16 June 2016

2016-06-16T07:32:36Z

← Older revision		Revision as of 09:32, 16 June 2016
Line 138:		Line 138:
	=== C modes ===		=== C modes ===

−	~~Those~~ modes are used by the C back-end: used C compiler, options... E. g.	+	These modes are used by the C back-end: used C compiler, options... E. g.
	[boost]		[boost]
	c_compiler_type: gcc		c_compiler_type: gcc

Hzwakenberg: No config files in root directory on Windows anymore

2016-06-14T08:44:57Z

No config files in root directory on Windows anymore

← Older revision		Revision as of 10:44, 14 June 2016
Line 16:		Line 16:
	\|-		\|-
	\| Windows and DOS:		\| Windows and DOS:
−	\| ~~<TT>C:\SE.CFG</TT>, <TT>C:\LIBERTY.CFG</TT>,~~ '''<TT>%ALLUSERSPROFILE%\Liberty-Eiffel</TT>''', <TT>%USERPROFILE%\SE.CFG</TT>, <TT>%USERPROFILE%\LIBERTY.CFG</TT>, '''<TT>%USERPROFILE%\Liberty-Eiffel</TT>''' (lookup in this order)	+	\| '''<TT>%ALLUSERSPROFILE%\Liberty-Eiffel</TT>''', <TT>%USERPROFILE%\SE.CFG</TT>, <TT>%USERPROFILE%\LIBERTY.CFG</TT>, '''<TT>%USERPROFILE%\Liberty-Eiffel</TT>''' (lookup in this order)
	\|-		\|-
	\| Unix and Cygwin:		\| Unix and Cygwin:

Hzwakenberg: Hzwakenberg moved page Configuration file - liberty.se to Configuration file - liberty.cfg

2016-06-01T11:50:41Z

Hzwakenberg moved page Configuration file - liberty.se to Configuration file - liberty.cfg

← Older revision	Revision as of 13:50, 1 June 2016
(No difference)