Compile - Revision history

Dkearns: s/LibertyEiffel/Liberty Eiffel/

2016-06-08T12:06:35Z

s/LibertyEiffel/Liberty Eiffel/

← Older revision		Revision as of 14:06, 8 June 2016
Line 1:		Line 1:
	[[Category:Tool]]		[[Category:Tool]]

−	<TT>compile</TT> is the most important tool because it is '''the''' ~~LibertyEiffel~~ compiler.	+	<TT>compile</TT> is the most important tool because it is '''the''' Liberty Eiffel compiler.
	In a normal installation, it is invoked by the command <b><TT>[[se]] c</TT></b>.		In a normal installation, it is invoked by the command <b><TT>[[se]] c</TT></b>.

Line 51:		Line 51:
	\|-		\|-
	\| valign="top" \| <code>-version</code>		\| valign="top" \| <code>-version</code>
−	\| Display the ~~LibertyEiffel~~ version number.	+	\| Display the Liberty Eiffel version number.
	\|}		\|}

Line 62:		Line 62:
	==== Example 1 ====		==== Example 1 ====

−	When ~~LibertyEiffel~~ is installed correctly, you can run the following command to test compile the notorious ''Hello world'' program:	+	When Liberty Eiffel is installed correctly, you can run the following command to test compile the notorious ''Hello world'' program:

	se c hello_world		se c hello_world
Line 70:		Line 70:
	se c -verbose hello_world		se c -verbose hello_world

−	and suddenly ~~LibertyEiffel~~ becomes ''very'' chatty! It just has to tell you about every file used and every file written.	+	and suddenly Liberty Eiffel becomes ''very'' chatty! It just has to tell you about every file used and every file written.

	An executable program is generated (normally <TT>a.out</TT> under UNIX, <TT>a.exe</TT> under Windows) which can be run directly.		An executable program is generated (normally <TT>a.out</TT> under UNIX, <TT>a.exe</TT> under Windows) which can be run directly.

Dkearns: s/method/feature/

2016-06-08T12:04:45Z

s/method/feature/

← Older revision		Revision as of 14:04, 8 June 2016
Line 27:		Line 27:
	starting point, which is, in fact, the creation of a class. In the ACE mode, this information is given by		starting point, which is, in fact, the creation of a class. In the ACE mode, this information is given by
	parameters in the ACE file.		parameters in the ACE file.
−	In the traditional mode, you have to give at least the class name: by default the creation ~~method~~ is called <TT>make</TT>, and this must exist; otherwise, it is necessary to specify the creation ~~method~~.	+	In the traditional mode, you have to give at least the class name: by default the creation feature is called <TT>make</TT>, and this must exist; otherwise, it is necessary to specify the creation feature.

−	In all cases, the creation ~~method~~ must be a ~~method~~ ''with no arguments''.	+	In all cases, the creation feature must be a feature ''with no arguments''.

	=== Common options ===		=== Common options ===

Hzwakenberg at 19:35, 5 September 2014

2014-09-05T19:35:57Z

← Older revision		Revision as of 21:35, 5 September 2014
Line 1:		Line 1:
−	[[Category:Smarteiffel]]
	[[Category:Tool]]		[[Category:Tool]]

−	<TT>compile</TT> is the most important tool because it is '''the''' ~~SmartEiffel~~ compiler.	+	<TT>compile</TT> is the most important tool because it is '''the''' LibertyEiffel compiler.
	In a normal installation, it is invoked by the command <b><TT>[[se]] c</TT></b>.		In a normal installation, it is invoked by the command <b><TT>[[se]] c</TT></b>.

Line 52:		Line 51:
	\|-		\|-
	\| valign="top" \| <code>-version</code>		\| valign="top" \| <code>-version</code>
−	\| Display the ~~SmartEiffel~~ version number.	+	\| Display the LibertyEiffel version number.
	\|}		\|}

Line 63:		Line 62:
	==== Example 1 ====		==== Example 1 ====

−	When ~~SmartEiffel~~ is ~~correctly~~ installed, you can run the following command to test compile the notorious ''Hello world'' program:	+	When LibertyEiffel is installed correctly, you can run the following command to test compile the notorious ''Hello world'' program:

	se c hello_world		se c hello_world
Line 71:		Line 70:
	se c -verbose hello_world		se c -verbose hello_world

−	and suddenly ~~SmartEiffel~~ becomes ''very'' chatty! It just has to tell you about every file used and every file written.	+	and suddenly LibertyEiffel becomes ''very'' chatty! It just has to tell you about every file used and every file written.

	An executable program is generated (normally <TT>a.out</TT> under UNIX, <TT>a.exe</TT> under Windows) which can be run directly.		An executable program is generated (normally <TT>a.out</TT> under UNIX, <TT>a.exe</TT> under Windows) which can be run directly.

Ramack at 21:13, 4 March 2013

2013-03-04T21:13:59Z

← Older revision		Revision as of 23:13, 4 March 2013
Line 1:		Line 1:
−	[[Category:~~Book~~]]	+	[[Category:Smarteiffel]]
		+	[[Category:Tool]]
−
−
−
−	<!-- translation hint: see http://smarteiffel.loria.fr/man/compile.html -->

	<TT>compile</TT> is the most important tool because it is '''the''' SmartEiffel compiler.		<TT>compile</TT> is the most important tool because it is '''the''' SmartEiffel compiler.

Ramack: 14 revisions: initial import from SamrtEiffel Wiki - The Grand SmartEiffel Book

2013-03-03T21:04:31Z

14 revisions: initial import from SamrtEiffel Wiki - The Grand SmartEiffel Book

New page

[[Category:Book]]



<TT>compile</TT> is the most important tool because it is '''the''' SmartEiffel compiler.
In a normal installation, it is invoked by the command <b><TT>[[se]] c</TT></b>.

There are two ways of invoking it: the ''traditional'' mode and the ''ACE'' mode.
* In the traditional mode, many options can be specified on the command line.
* In the [[ACE]] mode ''(Assembly of Classes in Eiffel)'', most of its options are not allowed on the
command line; they have their equivalents ''in'' the ACE file.

== Synopsis ==

* <code>se c [common_options] [c2c_options] <root_class> [<root_procedure>]</code>
* <code>se c [common_options] <ace_file.ace></code>

The first syntax is the traditional mode, the second is the ACE mode.

In the ACE mode, the name of the [[ACE]] file provided must end with the suffix <TT>.ace</TT>.

The <TT>compile</TT> command runs through several stages:
# the <TT>[[compile_to_c]]</TT> command is called to produce the C files (<TT>*.h</TT> and <TT>*.c</TT>).
A script file is also created, whose name depends on the application.
# this script is executed line by line; normally, it call the C compiler for each <TT>.c</TT> file, then it finishes with the link phase.
# if the <TT>-clean</TT> option is used, the <TT>[[clean]]</TT> command is called.

Like <TT>[[compile_to_c]]</TT>, <TT>compile</TT> must have at least one argument which gives the program's
starting point, which is, in fact, the creation of a class. In the ACE mode, this information is given by
parameters in the ACE file.
In the traditional mode, you have to give at least the class name: by default the creation method is called <TT>make</TT>, and this must exist; otherwise, it is necessary to specify the creation method.

In all cases, the creation method must be a method ''with no arguments''.

=== Common options ===

{| cellspacing="4" cellpadding="0" width="100%"
|-
| width="20%" valign="top" | <code>-clean</code>
| By default, the generated C files are kept from one execution to the next. This allows incremental compilation, since only the files changed since the last invocation of <TT>compile</TT> are regenerated.

Since the Eiffel compilation is usually much faster than the C compilation, this usually saves a lot of time.

However, there are situations when one wants to remove all the old generation of files, so as to start from scratch.

The <TT>-clean</TT> option deletes the C files, the object files and several other generated files, by invoking the <TT>[[clean]]</TT> command at the end of the compilation.
|-
| valign="top" | <code>-help</code>
| Display a short summary of the command line syntax,as well as a complete list of the compiler's options.
|-
| valign="top" | <code>-verbose</code>
| Display (an enormous amount of) information during the compilation: a complete list of files loaded, the [[type inference]] scores, the generated files, and so on.
|-
| valign="top" | <code>-version</code>
| Display the SmartEiffel version number.
|}

=== c2c options ===

These options are passed directly to <TT>[[compile_to_c]]</TT>. See that command for details.

=== Examples of using traditional mode ===

==== Example 1 ====

When SmartEiffel is correctly installed, you can run the following command to test compile the notorious ''Hello world'' program:

se c hello_world

In this mode, by default, the compiler is very silent; to see more detail, enter

se c -verbose hello_world

and suddenly SmartEiffel becomes ''very'' chatty! It just has to tell you about every file used and every file written.

An executable program is generated (normally <TT>a.out</TT> under UNIX, <TT>a.exe</TT> under Windows) which can be run directly.

==== Example 2 ====

Enter the following command to create a finalised version of our ''Hello world'':

se c -boost -c_mode release hello_world

These options are passed to <TT>[[compile_to_c]]</TT>. This is usually the best way to finalise a program. Note that using [[Configuration_file#C_modes|C mode]] commonly implies the <TT>-no_split</TT> option, as well as passing the <TT>-O3</TT> option to the C compiler.

==== Example 3 ====

To compile a large project (e.g. the class <TT>PROJECT</TT>) with incremental compilation and checking preconditions:

se c -require_check project

The very first time, all the C files are produced and compiled. Subsequently, if you use the same command after changing some Eiffel files, only the changed C files will be recompiled.

Note that extensive modifications of the source can force the recompilation of the whole project.

Again, changing the compilation options also involves recompiling the whole set of generated C files.

80.177.205.209: First translation into English

2005-11-25T21:33:03Z

First translation into English

New page

[[Category:Book]]



<TT>compile</TT> is the most important tool because it is '''the''' SmartEiffel compiler.
In a normal installation, it is invoked by the command <b><TT>[[se]] c</TT></b>.

There are two ways of invoking it: the ''traditional'' mode and the ''ACE'' mode.
* In the traditional mode, many options can be specified on the command line.
* In the [[ACE]] mode ''(Assembly of Classes in Eiffel)'', most of its options are not allowed on the
command line; they have their equivalents ''in'' the ACE file.

== Synopsis ==

* <code>se c [common_options] [c2c_options] <root_classe> [<root_procedure>]</code>
* <code>se c [common_options] <ace_file.ace></code>

The first syntax is the traditional mode, the second is the ACE mode.

In the ACE mode, the name of the [[ACE]] file provided must end with the suffix <TT>.ace</TT>.

The <TT>compile</TT> command runs through several stages:
# the <TT>[[compile_to_c]]</TT> command is called to produce the C files (<TT>*.h</TT> and <TT>*.c</TT>).
A script file is also created, whose name depends on the application.
# this script is executed line by line; normally, it call the C compiler for each <TT>.c</TT> file, then it finishes with the link phase.
# if the <TT>-clean</TT> option is used, the <TT>[[clean]]</TT> command is called.

Like <TT>[[compile_to_c]]</TT>, <TT>compile</TT> must have at least one argument which gives the program's
starting point, which is, in fact, the creation of a class. In the ACE mode, this information is given by
parameters in the ACE file.
In the traditional mode, you have to give at least the class name: by default the creation method is called <TT>make</TT>, and this must exist; otherwise, it is necessary to specify the creation method.

In all cases, the creation method must be a method ''with no arguments''.

=== Common options ===

{| cellspacing="4" cellpadding="0" width="100%"
|-
| width="20%" valign="top" | <code>-clean</code>
| By default, the generated C files are kept from one execution to the next. This allows incremental compilation, since only the files changed since the last invocation of <TT>compile</TT> are regenerated.

Since the Eiffel compilation is usually much faster than the C compilation, this usually saves a lot of time.

However, there are situations when one wants to remove all the old generation of files, so as to start from scratch.

The <TT>-clean</TT> option deletes the C files, the object files and several other generated files, by invoking the <TT>[[clean]]</TT> command at the end of the compilation.
|-
| valign="top" | <code>-help</code>
| Display a short summary of the command line syntax,as well as a complete list of the compiler's options.
|-
| valign="top" | <code>-verbose</code>
| Display (an enormous amount of) information during the compilation: a complete list of files loaded, the [[type inference]] scores, the generated files, and so on.
|-
| valign="top" | <code>-version</code>
| Display the SmartEiffel version number.
|}

=== c2c options ===

These options are passed directly to <TT>[[compile_to_c]]</TT>. See that command for details.

=== Examples of using traditional mode ===

==== Example 1 ====

When SmartEiffel is correctly installed, you can run the following command to test compile the notorious ''Hello world'' program:

se c hello_world

In this mode, by default, the compiler is very silent; to see more detail, enter

se c -verbose hello_world

and suddenly SmartEiffel becomes ''very'' chatty! It just has to tell you about every file used and every file written.

An executable program is generated (normally <TT>a.out</TT> under UNIX, <TT>a.exe</TT> under Windows) which can be run directly.

==== Example 2 ====

Enter the following command to create a finalised version of our ''Hello world'':

se c -boost -c_mode release hello_world

These options are passed to <TT>[[compile_to_c]]</TT>. This is usually the best way to finalise a program. Note that using [[Configuration_file#C_modes|C mode]] commonly implies the <TT>-no_split</TT> option, as well as passing the <TT>-O3</TT> option to the C compiler.

==== Example 3 ====

To compile a large project (e.g. the class <TT>PROJECT</TT>) with incremental compilation and checking preconditions:

se c -require_check project

The very first time, all the C files are produced and compiled. Subsequently, if you use the same command after changing some Eiffel files, only the changed C files will be recompiled.

Note that extensive modifications of the source can force the recompilation of the whole project.

Again, changing the compilation options also involves recompiling the whole set of generated C files.

194.250.98.243 at 12:30, 22 November 2005

2005-11-22T12:30:37Z

← Older revision		Revision as of 14:30, 22 November 2005
Line 1:		Line 1:
	[[Category:Book]]		[[Category:Book]]
		+	{{TranslationWanted}}
−
−	*** Please wait for the French version to stabilize
−	*** Thanks!

Cadrian: typo

2005-07-11T10:57:48Z

typo

← Older revision		Revision as of 12:57, 11 July 2005
Line 1:		Line 1:
−	[[[Category:Book]]	+	[[Category:Book]]

	*** Please wait for the French version to stabilize		*** Please wait for the French version to stabilize

Cadrian: please wait before translating

2005-07-11T09:26:44Z

please wait before translating

New page

[[[Category:Book]]

*** Please wait for the French version to stabilize
*** Thanks!