Building a delivery

Revision as of 15:20, 27 January 2012 by Manus (Talk | contribs) (Updated path of Delivery)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

The following commands create a new delivery of EiffelStudio in the current directory. The script assumes that you are running bash, that you have defined the environment variable EIFFEL_SRC and that you have followed the instructions to compile EiffelStudio.


Before starting, one has to setup a few things:

export SVNURL=
export NEW_ISE_EIFFEL=`pwd`/EiffelXX
svn co $SVNURL/Src/Delivery EiffelXX

Building a delivery (common part)

To build a delivery for any platform, you first need to create the delivery layout correctly. The building of that layout differs between Windows and Unix.

On Unix, you have to do the following:

cd $NEW_ISE_EIFFEL/studio/config
cd $NEW_ISE_EIFFEL/studio/spec
mkdir $ISE_PLATFORM/bin
mkdir $ISE_PLATFORM/include
mkdir $ISE_PLATFORM/lib
mv $ISE_PLATFORM/finish_freezing $ISE_PLATFORM/bin

On Windows, this:

cd $NEW_ISE_EIFFEL/studio/config
mv windows $ISE_PLATFORM
cd $NEW_ISE_EIFFEL/studio/spec
mkdir $ISE_PLATFORM/include
mkdir $ISE_PLATFORM/lib
cp -f windows/compile_library.bat $ISE_PLATFORM/compile_library.bat

Building a delivery for the same platform

After having followed the instructions to compile EiffelStudio, you must have the runtime compiled. Then you first need to copy the new headers:

cp $EIFFEL_SRC/C/run-time/*.h $NEW_ISE_EIFFEL/studio/spec/$ISE_PLATFORM/include

And then the various binary objects that were generated. Again here Windows and Unix have a different set of steps.

On Unix, you need to do the following:

cp $EIFFEL_SRC/C/ $NEW_ISE_EIFFEL/studio/spec/$ISE_PLATFORM/include
cp $EIFFEL_SRC/C/run-time/lib* $NEW_ISE_EIFFEL/studio/spec/$ISE_PLATFORM/lib
cp $EIFFEL_SRC/C/run-time/x2c $NEW_ISE_EIFFEL/studio/spec/$ISE_PLATFORM/bin
cp $EIFFEL_SRC/C/ipc/daemon/ecdbgd $NEW_ISE_EIFFEL/studio/spec/$ISE_PLATFORM/bin

On Windows, you need to do the following:

cp $EIFFEL_SRC/C/run-time/lib/* $NEW_ISE_EIFFEL/studio/spec/$ISE_PLATFORM/lib/$ISE_C_COMPILER
cp $EIFFEL_SRC/C/run-time/x2c.exe $NEW_ISE_EIFFEL/studio/spec/$ISE_PLATFORM/bin
cp $EIFFEL_SRC/C/ipc/daemon/ecdbgd.exe $NEW_ISE_EIFFEL/studio/spec/$ISE_PLATFORM/bin

Now your delivery is ready to receive the executable that you will have compiled.

Building a delivery for cross compilation

If you are developing on a platform (host) but targeting a different platform (target), you can reuse all the steps above except the part about copying x2c and ecdbgd. First ecdbgd can be omitted since this is used for debugging and we do not provide an emulator for you that would debug a binary generated for another platform.

What is so special about x2c then? This program converts our platform independent generated C code into a platform specific C code. However this program has to run on your host platform and the default build of the runtime built it for the target. So you need to do the following two steps to compile the proper executable for your target platform:

cd $EIFFEL_SRC/C/run-time
cc -O3 -c offset.c
cc -I. -I./include -Wall -O3 -c x2c.c
cc -o x2c x2c.o offset.o

After that you can copy x2c to the location mentioned above.

Information.png Note: we used cc as to represent your platform specific C compiler. Most of the time it will be gcc


Other ways to build a delivery

Some users have contributed other ways to build a delivery. Check with the authors to ensure they are properly up-to-date.

A solution based on geant is available to build a delivery from the source code: check Automatic_Build_Scripts

On Windows you may alternativly use the this Powershell script.