Difference between revisions of "Building a delivery"
(Updated to reflect how things are now done in 6.6) |
|||
| Line 2: | Line 2: | ||
[[Category:Compiler]] | [[Category:Compiler]] | ||
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 '''{{Red|you have followed [[Compiling_EiffelStudio|the instructions to compile EiffelStudio]]}}'''. | 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 '''{{Red|you have followed [[Compiling_EiffelStudio|the instructions to compile EiffelStudio]]}}'''. | ||
| − | |||
| − | |||
==Prerequisites== | ==Prerequisites== | ||
| Line 53: | Line 51: | ||
Now your delivery is ready to receive the executable that you will have compiled. | 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 | ||
| + | |||
| + | For the above we use '''cc''', your platform C compiler. | ||
| + | |||
| + | ==Other ways to build a delivery== | ||
| + | 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]] [[media:building_delivery.ps1|script]]. | ||
Revision as of 11:13, 25 February 2010
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.
Contents
Prerequisites
Before starting, one has to setup a few things:
export SVNURL=https://svn.eiffel.com/eiffelstudio/trunk export NEW_ISE_EIFFEL=`pwd`/EiffelXX svn co $SVNURL/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 mv unix $ISE_PLATFORM cd $NEW_ISE_EIFFEL/studio/spec mv unix $ISE_PLATFORM mkdir $ISE_PLATFORM/bin mkdir $ISE_PLATFORM/include mkdir $ISE_PLATFORM/lib mv $ISE_PLATFORM/finish_freezing $ISE_PLATFORM/bin mv $ISE_PLATFORM/prelink $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/config.sh $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:
mkdir $NEW_ISE_EIFFEL/studio/spec/$ISE_PLATFORM/lib/$ISE_C_COMPILER 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
For the above we use cc, your platform C compiler.
Other ways to build a delivery
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.
