EiffelStudio: an EiffelSoftware project - User contributions [en]

Syntax checking

2006-04-27T14:32:13Z

Classens: /* Software Requirement Specification (SaRS) */ added link

[[Category:Projects]]
[[Category:Editor]]

=Overview=
The aim of this project is to have a syntax checking done as you type.
Syntax errors should be highlighted and eventualy also options for correcting the error should be proposed.

The Project is named '''SynChé''', which is a combination of syntax and checking.
The ''é'' at the end is important, as a cool name needs either a recursive acronym or a special character from a non English language.

=Software Requirement Specification (SaRS)=
you can find our SaRS [[Syntax_checking/SRS|here]] (comming soon)

=Milestones=

==M1: April 25th==
* Get home-grown EiffelStudio up and running.

==M2: May 2nd==
* '''Put your name in this Wiki!'''
* Analyse source code to certain degree, so discussion about interfaces between parser and visual is possible

==M3: May 9th==
* Full SRS written
* Further Project Milestones specified, based on SRS and knowledge about code

=Team=
Everyone intrested in this project is welcome to join our mailinglist [http://origo.ethz.ch/cgi-bin/mailman/listinfo/es-ui es-ui@origo.ethz.ch].
At this point, the team is divided into two groups at this point, one responsible for the parser, the other one for visual feedback (like underlininig).

== Visual Feedback ==
* [[User:jabernet| Janick Bernet]] (scapegoat aka project leader)
* [[User:fdevries| Fabien de Vries]]
* [[User:indermum| Matthias Indermühle]]
* [[User:clerco| Olivier Clerc]]

== Parser ==
* [[User:maser| Martin Luder]]
* [[User:chrhuber| Christoph Huber]]

== Assistant ==
* [[User:classens| Stephan Classen]]

EMU

2006-04-27T14:30:04Z

Classens: outsourced the srs for bether readability

[[Category:Projects]]

=Overview=
==Name==
EMU stands for '''Eiffel Multi User'''.
==Goal==
The aim of this project is to integrate a simple repository functionality into EiffelStudio.

=Software Requirements Specification=
You can find our SRS [[EMU/SRS|here]]

=Milestones=

==M1: April 25th==
* set up mailinglist es-emu@origo.ethz.ch ([[User:Schoelle|Bernd]])
* wiki page up to date
* everyone managed to compile Eiffelstudio

==M2: May ??? ==
* To be completed by the team

=Team=
Everyone interested in this project is welcome to join our mailinglist [http://origo.ethz.ch/cgi-bin/mailman/listinfo/es-emu es-emu@origo.ethz.ch]

* [[User:Barnski| Bernhard Buss]] (project leader)
* [[User:Zandrea| Andrea Zimmermann]]
* [[User:Kamala| Claudia Kuster]]
* [[User:sdomenic| Domenic Schröder]]
* [[User:luc3D| Lucien Hansen]]
* [[User:ramons| Ramon Schwammberger]]
* [[User:Trickli| Tobias Rickli]]
* [[User:classens| Stephan Classen]]

EMU/SRS

2006-04-27T14:29:22Z

Classens:

=The Parts=
* EMU-Protocol
* EMU-Server
* EMU-Client
* EMU-IDE integration

=Developer Requirements=
==EMU-Protocol==
defines Client/Server communication with
* client/server states
* available messages
* client/server actions

==EMU-Server==
* stores and manages code-repository
* synchronizes code of clients
* manages Locking-System
* Account-System
* project update
* add/create new code (classes)
* change-logging
* optional: Media-upload
* optional: BackUp-System
* optional: Release-versions
* optional: Server-Admin-Tool

===Locking-System===
* list of locked code
* check if code (class) is locked
* lock / unlock code (class)

===Code-Synchronization===
* broadcast code-changes
* bring user code up to date

===Account-System===
The server uses an account-system to organize its projects and users.
Every project has its own users assigned.

====Project-Accounts====
* project name
* project-admin(s)
* user lists
* project status
* editable / creatable with a project-admin-tool

====User-Accounts====
* usernames
* used for logins
* assign locked code & changes to users
* online status

==Change-Log==
Every lock/unlock action is locked with following data:
* user name
* date and time
* type of action
* code element (class name)

==EMU-Client==
* interface for IDE and server
* provides features to login and communicate with server on an abstract base
* upload/download code elements to/from server
* notify IDE of server-messages (code-updates)
* modular / independent of IDE-integration
* optional: upload media files

===IDE-Notifications===
The client needs to notify the IDE of the new changes.

==EMU-IDE integration==
* minimal change to existing ES-classes and features.
* modular integration: activatable and removable / hideable

=User Requirements=
* easy to use
* target is a small project group of up to 20 developers.
* code synchronisation process mostly hidden from user
* minimal extra work (less total work)
* better efficiency

Compiling EiffelStudio

2006-04-25T06:58:47Z

Classens: /* Compiling run-time on Windows */ note to the special file windows-msc-x86

[[Category:Compiler]]
[[Category:EiffelStudio]]

== Installing EiffelStudio ==

To compile EiffelStudio, you need an already working EiffelStudio compiler on your machine. The current source tree '''requires at least version 5.7''' of EiffelStudio. You can download it from http://eiffelsoftware.origo.ethz.ch/downloads/builds/. This version still requires a registration (we missed to remove the registration cluster while compiling). You need to '''activate''' EiffelStudio (see below), because in some cases the compiler won't work correctly if not activated. [[Installing EiffelStudio]] is covered in its own article.

'''Note:''' on Windows you will need the Microsoft C compiler to compile Eiffel Studio. How to install the free version of the Microsoft C compiler: [[Installing Microsoft C compiler]]

===Compilation methods===
Currently there are two compilation methods.
* You can use one of the [[Automatic Build Scripts]]
* Alternatively you can compile EiffelStudio from scratch following the instructions in this document.

If possible, use the [[Automatic Build Scripts]] and report any errors to the [http://origo.ethz.ch/cgi-bin/mailman/listinfo/es-devel developer mailing list].

==Extracting source code==

===Checking out from SVN===
#Point an environment variable called '''EIFFEL_SRC''' to the directory where you want to compile EiffelStudio Usually we use the '''XXdev''' convention for this directory name - where XX is the version number from the current developped version of the compiler.
#Make sure that '''ISE_EIFFEL''', '''ISE_PLATFORM''' and '''ISE_C_COMPILER''' (on windows only) are properly defined
#Perform the following checkout procedures:

'''DOS'''
<pre>
set SVNURL=https://eiffelsoftware.origo.ethz.ch/svn/es
svn co %SVNURL%/trunk/Src 57dev
svn co %SVNURL%/trunk/Delivery 57dev/Delivery
svn co %SVNURL%/trunk/free_add_ons 57dev/free_add_ons
</pre>

'''Bash'''
<pre>
export SVNURL=https://eiffelsoftware.origo.ethz.ch/svn/es
svn co $SVNURL/trunk/Src 57dev
svn co $SVNURL/trunk/Delivery 57dev/Delivery
svn co $SVNURL/trunk/free_add_ons 57dev/free_add_ons
</pre>

To update the sourcefiles to the latest revision, perform the following steps:

'''Bash and DOS'''
<pre>
cd 57dev
svn up
svn up free_add_ons
svn up Delivery
</pre>

==Installing gobo==

Please make sure to use the version provided or the very latest version from CVS. All other versions (including the official 3.4 release) will not work because of name clashes in the UC_STRING class between GOBO and EiffelStudio. 
As the anonymous CVS on sourceforge is currently broken, use the following link from the gobo newsgroup to get the [http://www.gobosoft.com/download/gobo-cvs-060418.zip CVS-checkout of 18.April].

===Windows specific===

You have to unzip the gobo distribution from $EIFFEL_SRC/free_add_ons/gobo/gobo_34_win.tgz and extract it into $EIFFEL_SRC/library.

===Unix specific===

You have to unzip the gobo distribution from $EIFFEL_SRC/free_add_ons/gobo/gobo_34_unix.tgz and extract it into $EIFFEL_SRC/library. Here is the list of commands to do this:
<pre>cd $EIFFEL_SRC/library
tar -xvzf $EIFFEL_SRC/free_add_ons/gobo/gobo_34_unix.tgz
</pre>

==Compiling C libraries==

===Compiling run-time on Windows===

Before being able to compile the run-time, you need to ensure that '''bash''' is in your '''PATH'''. You can download it from [http://www.cygwin.com http://www.cygwin.com]. Also make sure, that the path to the binaries of your c compiler is placed before the path to cygwin or else the wrong linker will be used. Once done you can do: 
'''Important:''' if you are using the setup as described in [[Installing Microsoft C compiler]] pleas read this first: [http://origo.ethz.ch/pipermail/es-devel/2006-April/000082.html mail from manus] you need to replace this file: <code>%EIFFEL_SRC%/C/CONFIGS/windows-msc-x86</code>

'''DOS'''
<pre>cd %EIFFEL_SRC%/C
configure [win32|win64] [b|m]</pre>

'''Bash'''
<pre>cd $EIFFEL_SRC/C
./configure.bat [win32|win64] [b|m]</pre>

The first argument indicated whether you are compiling the run-time for 32 or 64 bits. The second one is to tell which C compiler will be used. For now only `b' (Borland) and `m' (Microsoft) are officially supported. We also informally support `g' (GCC) and `l' (LCC).

On Windows 32 bits to clean up all the generated files you do:

'''DOS'''
<pre>configure clean</pre>
'''Bash'''
<pre>./configure.bat clean</pre>

On Windows 64 bits, you do:
<pre>configure cleand</pre>

===Compiling run-time on Unix===

The command is simply:
<pre>cd $EIFFEL_SRC/C
./quick_configure</pre>
This requires that '''ISE_PLATFORM''' is properly defined. The `quick_configure' script will look for the file CONFIGS/$ISE_PLATFORM and use it to extract the platform specific information to compile the run-time. If not found then an error will be reported.

===Compiling C code from libraries===

Here is the list of commands to compile all required C libraries on Windows:

'''DOS'''
<pre>cd %EIFFEL_SRC%/library/net/Clib
make_msc.bat
cd %EIFFEL_SRC%/library/vision2/Clib
make_msc.bat
cd %EIFFEL_SRC%/library/wel/Clib
make_msc.bat</pre>
'''Bash'''
<pre>cd $EIFFEL_SRC/library/net/Clib
./make_msc.bat
cd $EIFFEL_SRC/library/vision2/Clib
./make_msc.bat
cd $EIFFEL_SRC/library/wel/Clib
./make_msc.bat</pre>

On Unix it is slightly different:
<pre>cd $EIFFEL_SRC/library/event/Clib
finish_freezing -library
cd $EIFFEL_SRC/library/net/Clib
finish_freezing -library
cd $EIFFEL_SRC/library/vision2/Clib
finish_freezing -library
cd $EIFFEL_SRC/library/vision2/implementation/gtk/Clib
finish_freezing -library</pre>

Make sure that '''ISE_EIFFEL''' is set correctly to your current "EiffelStudio" installation!

===Compiling C code from C_library===

This is only required on Windows to read PNG file. On Unix, this is not required because it is included in GTK+2.4. Simply do the following:

'''DOS'''
<pre>cd %EIFFEL_SRC%/C_library/zlib
make_msc.bat
cd %EIFFEL_SRC%/C_library/libpng
make_msc.bat</pre>
'''Bash'''
<pre>cd $EIFFEL_SRC/C_library/zlib
./make_msc.bat
cd $EIFFEL_SRC/C_library/libpng
./make_msc.bat</pre>

===Compiling C code from compiler===

This is only required on Windows as this C code is a tiny wrapper around the Microsoft C++ API to generate and to debug .NET code.

To compile it, you first need to install the Microsoft .NET SDK. You can download it from their website.

After installing it, you need to update your '''LIB''' and '''INCLUDE''' environment variable to include the path the lib and include directory of the .NET Framework SDK.

Once properly installed, you can do:

'''DOS'''
<pre>cd %EIFFEL_SRC%/Eiffel/library/cli_writer/Clib
nmake</pre>
'''Bash'''
<pre>cd $EIFFEL_SRC/Eiffel/library/cli_writer/Clib
nmake</pre>

==Compiling EiffelStudio==

Now that we have taken care of the C code compilation we can compile the compiler. There are four ace files in $EIFFEL_SRC/Eiffel/Ace:
* batch.mswin.ace
* newbench.mswin.ace
* batch.unix.ace
* newbench.linux.ace
The first two are for windows, the last two for unix (even if the last one says `linux').

To compile simply do:
<pre>ec -ace <chosen_ace_file> -c_compile</pre>

Please note: the 'ec' binary produced by the newbench .ace file contains the full Eiffel compiler, including the batch version. 'estudio' is just a wrapper (available in Src/bench/C/ipc/daemon). So, you need either the one or the other.

===Windows specific===

At the end of the compilation for the workbench version, the C compilation will fail reporting an undefined reference to `nbref'. This is because the ace file has been built for the finalized version of EiffelStudio not the workbench version. To fix this problem do the following:
<pre>copy ec.lnk h</pre>
Then edit the file `h' and replace '''mtcompiler.lib''' by '''mtwcompiler.lib'''.
Once this is done you can complete you do:
<pre>link @h</pre>
In order to update to the new version of metadata consumer tool, follow the instructions described [[Compiling Metadata Consumer|here]].

===Unix specific===

Like the windows version the C compilation, it will fail, but this time for two reasons:
* nbref
* linking order causing many errors to be reported

Here is the recommended way, make a copy of the generated Makefile and put it at the same level as your EIFGEN directory. Edit it and replace '''libmtcompiler.a''' by '''libmtwcompiler.a''', then search for "$(EXTERNALS) $(EIFLIB)" and replace it by "$(EIFLIB) $(EXTERNALS)". Once this is done, you can do:
<pre>make -f ../../Makefile</pre>

A little script that does the necessary changes: Place it at the same level as the EIFGEN directory is.

<code>[bash,N]
#!/bin/bash

cp EIFGEN/W_code/Makefile .
sed 's/libmtcompiler\.a/libmtwcompiler\.a/g' Makefile > tmp
sed 's/\$(EXTERNALS) \$(EIFLIB)/\$$EIFLIB$ \$$EXTERNALS$/g' tmp > Makefile
cd EIFGEN/W_code
make -f ../../Makefile
</code>

'''Note:''' These changes are not required if you try to compile a finalized version of EiffelStudio, but only if you want to create a workbench version of EiffelStudio for development and debugging.

Also, if you encounter problems with your self-compiled version of EiffelStudio, you might try to compile it with GCC 3.x. Version 4 of GCC has a slight change in semantics and EiffelStudio has not been updated. You can see the change in behavior in the following code:

<code>[C,N]
#include <stdio.h>

int a;
int b;
int *pointer;

int foo()
{
pointer = &b;
return 4;
}

int main (int argc, char** argv)
{
a = 3;
b = 0;

pointer = &a;

*pointer = foo();

printf ("You are using GCC %d.%d\n",a,b);
return 0;
}
</code>

===Mac OS X specific===

The basic steps are:
* compile it under linux (as described above, but finalize with ec -ace <chosen_ace_file> -finalize -c_compile)
* copy the F_Code directory to the mac (and build the whole source arround it... so that it almost looks like under linux).
* compile it there using make (compile all the dependencies as described above, then try to compile ... & ok change a lot of stuff in the Makefile.SH's or do it otherwise! )
* fix whatever problems appear

for more information : try the experimental release from http://eiffelsoftware.origo.ethz.ch/downloads/porting/ and have a look at the basher.sh - skript

You can get the F_code build under Linux with gcc-3.3 and gtk2.8.17 (same as available under darwin ports) here [24.04.06]: http://n.ethz.ch/student/dfurrer/files/f_code.tar.gz

still todo : script to generate a working environement for EiffelStudio

note : it seems to be neccessary to install gtk-2.6 if you want to build a working environement for EiffelStudio (neccessary for some vision2-libraries)

a first (binary) experimental releas is available from http://eiffelsoftware.origo.ethz.ch/downloads/builds/experimental/

Syntax checking

2006-04-23T08:27:19Z

Classens: /* Team */

[[Category:Projects]]
[[Category:Editor]]

=Overview=
The aim of this project is to have a syntax checking done as you type.
Syntax errors should be highlited and eventualy also options for correcting the error should be propossed.

=Milestones=

==M1: April 25th==

==M2: May ??? ==
* To be completed by the team

=Team=
Everyone intrested in this project is welcome to join our mailinglist [http://origo.ethz.ch/cgi-bin/mailman/listinfo/es-ui es-ui@origo.ethz.ch]

* [[User:jabernet| Janick Bernet]] (big boss and scapegoat)
* [[User:maser| Martin Luder]]
* [[User:clerco| Olivier Clerc]]
* [[User:classens| Stephan Classen]]

EMU

2006-04-23T08:26:02Z

Classens: /* Team */

[[Category:Projects]]

=Overview=
Eiffel Multi User: The aim of this project is to integrate a repository functionality into EiffelStudio.

=Software Requirements Specification=
==The Parts==
* EMU-Server (stores and manages code-repository)
* EMU-Client (communicates with EMU-Server)
* EMU-IDE integration

==Developer Requirements==
===EMU-Server===
===EMU-Client===
===EMU-IDE integration===
* minimal change to existing ES-classes and features.
* modular integration: activatable and removable / hideable

==User Requirements==
* easy to use
* target is a small project group of up to 20 developers.

=Milestones=

==M1: April 25th==
* set up mailinglist es-emu@origo.ethz.ch ([[User:Schoelle|Bernd]])
* wiki page up to date
* everyone managed to compile Eiffelstudio

==M2: May ??? ==
* To be completed by the team

=Team=
Everyone intrested in this project is welcome to join our mailinglist [http://origo.ethz.ch/cgi-bin/mailman/listinfo/es-emu es-emu@origo.ethz.ch]

* [[User:Barnski| Bernhard Buss]] (project leader)
* [[User:Zandrea| Andrea Zimmermann]]
* [[User:Kamala| Claudia Kuster]]
* [[User:sdomenic| Domenic Schröder]]
* [[User:luc3D| Lucien Hansen]]
* [[User:ramons| Ramon Schwammberger]]
* [[User:classens| Stephan Classen]]

EMU

2006-04-23T08:24:55Z

Classens: /* Team */ added maillist link

Syntax checking

2006-04-23T08:23:56Z

Classens: /* Team */

[[Category:Projects]]
[[Category:Editor]]

=Overview=
The aim of this project is to have a syntax checking done as you type.
Syntax errors should be highlited and eventualy also options for correcting the error should be propossed.

=Milestones=

==M1: April 25th==

==M2: May ??? ==
* To be completed by the team

=Team=
* [[User:jabernet| Janick Bernet]] (big boss and scapegoat)
* [[User:maser| Martin Luder]]
* [[User:clerco| Olivier Clerc]]

Everyone intrested in this project is welcome to join our mailinglist [http://origo.ethz.ch/cgi-bin/mailman/listinfo/es-ui es-ui@origo.ethz.ch]

* TODO add project leader
* TODO add project members
* [[User:FoB| Stephan Classen]]

Compiling EiffelStudio

2006-04-21T14:18:42Z

Classens: /* Compilation methods */

[[Category:Compiler]]
[[Category:EiffelStudio]]

== Installing EiffelStudio ==

To compile EiffelStudio, you need an already working EiffelStudio compiler on your machine. The current source tree '''requires at least version 5.7''' of EiffelStudio. You can download it from http://eiffelsoftware.origo.ethz.ch/downloads/builds/. This version still requires a registration (we missed to remove the registration cluster while compiling). You need to '''activate''' EiffelStudio (see below), because in some cases the compiler won't work correctly if not activated. [[Installing EiffelStudio]] is covered in its own article.

'''Note:''' on Windows you will need the Microsoft C compiler to compile Eiffel Studio. How to install the free version of the Microsoft C compiler: [[Installing Microsoft C compiler]]

===Compilation methods===
Currently there are two compilation methods.
* You can either compile EiffelStudio from scratch following the instructions in this document.
* Alternatively you can use a [[Automatic Build Scripts]]
If possible, use the compilation script and report any errors to the developer mailing list.

==Extracting source code==

===Checking out from SVN===
#Point an environment variable called '''EIFFEL_SRC''' to the directory where you want to compile EiffelStudio Usually we use the '''XXdev''' convention for this directory name - where XX is the version number from the current developped version of the compiler.
#Make sure that '''ISE_EIFFEL''', '''ISE_PLATFORM''' and '''ISE_C_COMPILER''' (on windows only) are properly defined
#Perform the following checkout procedures:

'''Windows'''
<pre>
set SVNURL=https://eiffelsoftware.origo.ethz.ch/svn/es
svn co %SVNURL%/trunk/Src 57dev
svn co %SVNURL%/trunk/Delivery 57dev/Delivery
svn co %SVNURL%/trunk/free_add_ons 57dev/free_add_ons
</pre>

'''Bash'''
<pre>
export SVNURL=https://eiffelsoftware.origo.ethz.ch/svn/es
svn co $SVNURL/trunk/Src 57dev
svn co $SVNURL/trunk/Delivery 57dev/Delivery
svn co $SVNURL/trunk/free_add_ons 57dev/free_add_ons
</pre>

To update the sourcefiles to the latest revision, perform the following steps:

'''Bash and Windows'''
<pre>
cd 57dev
svn up
svn up free_add_ons
svn up Delivery
</pre>

==Installing gobo==

Please make sure to use the version provided or the very latest version from CVS. All other versions (including the official 3.4 release) will not work because of name clashes in the UC_STRING class between GOBO and EiffelStudio. 
As the anonymous CVS on sourceforge is currently broken, use the following link from the gobo newsgroup to get the [http://www.gobosoft.com/download/gobo-cvs-060418.zip CVS-checkout of 18.April].

===Windows specific===

You have to unzip the gobo distribution from $EIFFEL_SRC/free_add_ons/gobo/gobo_34_win.tgz and extract it into $EIFFEL_SRC/library.

===Unix specific===

You have to unzip the gobo distribution from $EIFFEL_SRC/free_add_ons/gobo/gobo_34_unix.tgz and extract it into $EIFFEL_SRC/library. Here is the list of commands to do this:
<pre>cd $EIFFEL_SRC/library
tar -xvzf $EIFFEL_SRC/free_add_ons/gobo/gobo_34_unix.tgz
</pre>

==Compiling C libraries==

===Compiling run-time on Windows===

Before being able to compile the run-time, you need to ensure that '''bash''' is in your '''PATH'''. You can download it from [http://www.cygwin.com http://www.cygwin.com]. Also make sure, that the path to the binaries of your c compiler is placed before the path to cygwin or else the wrong linker will be used. Once done you can do:

'''Windows''' (cmd)
<pre>cd %EIFFEL_SRC%/C
configure [win32|win64] [b|m]</pre>

'''Bash'''
<pre>cd $EIFFEL_SRC/C
./configure.bat [win32|win64] [b|m]</pre>

The first argument indicated whether you are compiling the run-time for 32 or 64 bits. The second one is to tell which C compiler will be used. For now only `b' (Borland) and `m' (Microsoft) are officially supported. We also informally support `g' (GCC) and `l' (LCC).

On Windows 32 bits to clean up all the generated files you do:

'''Windows'''
<pre>configure clean</pre>
'''Bash'''
<pre>./configure.bat clean</pre>

On Windows 64 bits, you do:
<pre>configure cleand</pre>

===Compiling run-time on Unix===

The command is simply:
<pre>cd $EIFFEL_SRC/C
./quick_configure</pre>
This requires that '''ISE_PLATFORM''' is properly defined. The `quick_configure' script will look for the file CONFIGS/$ISE_PLATFORM and use it to extract the platform specific information to compile the run-time. If not found then an error will be reported.

===Compiling C code from libraries===

Here is the list of commands to compile all required C libraries on Windows:

'''Windows'''
<pre>cd %EIFFEL_SRC%/library/net/Clib
make_msc.bat
cd %EIFFEL_SRC%/library/vision2/Clib
make_msc.bat
cd %EIFFEL_SRC%/library/wel/Clib
make_msc.bat</pre>
'''Bash'''
<pre>cd $EIFFEL_SRC/library/net/Clib
./make_msc.bat
cd $EIFFEL_SRC/library/vision2/Clib
./make_msc.bat
cd $EIFFEL_SRC/library/wel/Clib
./make_msc.bat</pre>

On Unix it is slightly different:
<pre>cd $EIFFEL_SRC/library/event/Clib
finish_freezing -library
cd $EIFFEL_SRC/library/net/Clib
finish_freezing -library
cd $EIFFEL_SRC/library/vision2/Clib
finish_freezing -library
cd $EIFFEL_SRC/library/vision2/implementation/gtk/Clib
finish_freezing -library</pre>

Make sure that '''ISE_EIFFEL''' is set correctly to your current "EiffelStudio" installation!

===Compiling C code from C_library===

This is only required on Windows to read PNG file. On Unix, this is not required because it is included in GTK+2.4. Simply do the following:

'''Windows'''
<pre>cd %EIFFEL_SRC%/C_library/zlib
make_msc.bat
cd %EIFFEL_SRC%/C_library/libpng
make_msc.bat</pre>
'''Bash'''
<pre>cd $EIFFEL_SRC/C_library/zlib
./make_msc.bat
cd $EIFFEL_SRC/C_library/libpng
./make_msc.bat</pre>

===Compiling C code from compiler===

This is only required on Windows as this C code is a tiny wrapper around the Microsoft C++ API to generate and to debug .NET code.

To compile it, you first need to install the Microsoft .NET SDK. You can download it from their website.

After installing it, you need to update your '''LIB''' and '''INCLUDE''' environment variable to include the path the lib and include directory of the .NET Framework SDK.

Once properly installed, you can do:

'''Windows'''
<pre>cd %EIFFEL_SRC%/Eiffel/library/cli_writer/Clib
nmake</pre>
'''Bash'''
<pre>cd $EIFFEL_SRC/Eiffel/library/cli_writer/Clib
nmake</pre>

==Compiling EiffelStudio==

Now that we have taken care of the C code compilation we can compile the compiler. There are four ace files in $EIFFEL_SRC/Eiffel/Ace:
* batch.mswin.ace
* newbench.mswin.ace
* batch.unix.ace
* newbench.linux.ace
The first two are for windows, the last two for unix (even if the last one says `linux').

To compile simply do:
<pre>ec -ace <chosen_ace_file> -c_compile</pre>

Please note: the 'ec' binary produced by the newbench .ace file contains the full Eiffel compiler, including the batch version. 'estudio' is just a wrapper (available in Src/bench/C/ipc/daemon). So, you need either the one or the other.

===Windows specific===

At the end of the compilation for the workbench version, the C compilation will fail reporting an undefined reference to `nbref'. This is because the ace file has been built for the finalized version of EiffelStudio not the workbench version. To fix this problem do the following:
<pre>copy ec.lnk h</pre>
Then edit the file `h' and replace '''mtcompiler.lib''' by '''mtwcompiler.lib'''.
Once this is done you can complete you do:
<pre>link @h</pre>
In order to update to the new version of metadata consumer tool, follow the instructions described [[Compiling Metadata Consumer|here]].

===Unix specific===

Like the windows version the C compilation, it will fail, but this time for two reasons:
* nbref
* linking order causing many errors to be reported

Here is the recommended way, make a copy of the generated Makefile and put it at the same level as your EIFGEN directory. Edit it and replace '''libmtcompiler.a''' by '''libmtwcompiler.a''', then search for "$(EXTERNALS) $(EIFLIB)" and replace it by "$(EIFLIB) $(EXTERNALS)". Once this is done, you can do:
<pre>make -f ../../Makefile</pre>

A little script that does the necessary changes: Place it at the same level as the EIFGEN directory is.

<code>[bash,N]
#!/bin/bash

cp EIFGEN/W_code/Makefile .
sed 's/libmtcompiler\.a/libmtwcompiler\.a/g' Makefile > tmp
sed 's/\$(EXTERNALS) \$(EIFLIB)/\$$EIFLIB$ \$$EXTERNALS$/g' tmp > Makefile
cd EIFGEN/W_code
make -f ../../Makefile
</code>

'''Note:''' These changes are not required if you try to compile a finalized version of EiffelStudio, but only if you want to create a workbench version of EiffelStudio for development and debugging.

Also, if you encounter problems with your self-compiled version of EiffelStudio, you might try to compile it with GCC 3.x. Version 4 of GCC has a slight change in semantics and EiffelStudio has not been updated. You can see the change in behavior in the following code:

<code>[C,N]
#include <stdio.h>

int a;
int b;
int *pointer;

int foo()
{
pointer = &b;
return 4;
}

int main (int argc, char** argv)
{
a = 3;
b = 0;

pointer = &a;

*pointer = foo();

printf ("You are using GCC %d.%d\n",a,b);
return 0;
}
</code>

===Mac OS X specific===

The basic steps are:
* compile it under linux (as described above, but finalize with ec -ace <chosen_ace_file> -finalize -c_compile)
* copy the F_Code directory to the mac (and build the whole source arround it... so that it almost looks like under linux)
* compile it there using make (compile all the dependencies as described above, then try to compile ... & ok change a lot of stuff in the Makefile.SH's or do it otherwise! )
* fix whatever problems appear

for more information : try the experimental release from http://eiffelsoftware.origo.ethz.ch/downloads/porting/ and have a look at the basher.sh - skript

still todo : skript to generate a working environement for EiffelStudio

note : it seems to be neccessary to install gtk-2.6 if you want to build a working environement for EiffelStudio

EMU

2006-04-21T11:17:38Z

Classens: /* Team */

[[Category:Projects]]

=Overview=
Eiffel Multi User: The aim of this project is to integrate a repository functionality into EiffelStudio.

=Software Requirements Specification=
==The Parts==
* EMU-Server (stores and manages code-repository)
* EMU-Client (communicates with EMU-Server)
* EMU-IDE integration

==Developer Requirements==
===EMU-Server===
===EMU-Client===
===EMU-IDE integration===
* minimal change to existing ES-classes and features.
* modular integration: activatable and removable / hideable

==User Requirements==
* easy to use
* target is a small project group of up to 20 developers.

=Milestones=

==M1: April 25th==
* set up mailinglist es-emu@origo.ethz.ch ([[User:Schoelle|Bernd]])

==M2: May ??? ==
* To be completed by the team

=Team=
Everyone intrested in this project is welcome to join our mailinglist es-emu@origo.ethz.ch

* [[User:Barnski| Bernhard Buss]] (project leader)
* [[User:Kamala| Claudia Kuster]]
* [[User:FoB| Stephan Classen]]

User:Classens

2006-04-21T11:16:34Z

Classens:

Stephan Classen

Teaching Assistant at ETH 
classens [A.T] student.ethz.ch

Advisor for the projects:
*[[Syntax checking]]
*[[EMU]]