Ecere SDK - Installation
Fork me on GitHub

Installation

You may be able to install the Ecere SDK from source if you're running a UNIX system

Source Code

http://github.com/ecere/ecere-sdk/

Clone with Git

git clone https://github.com/ecere/ecere-sdk.git

Tarballs

Latest Release (0.44.15 August 4, 2016
Latest Development Snapshot

Installation per Platform

Target Platforms

Source Code



To build the Ecere SDK from source, you first need to install the development packages for its dependencies. The prefix defaults to /usr. If you wish to install somewhere else, pass e.g. prefix=/usr/local to make.

If you are not running Linux, make sure you are using a recent version of GNU Make (gmake).
Once your dependencies are set up, building and installing Ecere should be as simple as:

make
sudo make install

You can launch the Ecere IDE with the command ide.

Limitations


Given various degrees of efforts, it should be possible to build on other UNIX platforms. You will need a recent version of GNU Make (gmake).

GCC or Clang is required for your C compiler. (TCC might work too)

X86, AMD64, PowerPC, 32 bit ARM architectures are all known to work.

Some assumptions about the C types are currently made. (e.g. char: signed 1 byte, int: 4 bytes, float: 4 bytes, double: 8 bytes)

If your platform offers no way to conform to these assumptions, there would be a lot of code to reconsider.

Please get in touch with us for help or to coordinate efforts improving platform support.

Building the Ecere SDK on Linux/UNIX


We invite you to contribute Ecere packaging for your distribution of choice, or even propose yourself as a maintainer.
We take care of maintaining the Debian packages.

See the source code links in the box in the top-right section of this page for obtaining the source.

Dependencies


You will also need the development packages (headers and linking libraries) for the following dependencies:

Building and Installing


The prefix defaults to /usr. If you wish to install somewhere else, pass e.g. prefix=/usr/local to make.

If you wish to build in one place and install to another directory (e.g. as part of a packaging process), you can use e.g. DESTDIR=/tmp/ecere_package/

Once your dependencies are set up, building and installing Ecere should be as simple as:

make
sudo make install


You can launch the Ecere IDE with the command ide.

You will find desktop icons and entries under share/.

Removing the need for some dependencies

Should any of these dependencies prove difficult to obtain or install, it is possible to tweak the makefiles to build without them.

A missing UPX will just be ignored.

OpenGL can be disabled with DISABLE_GL=y.

For SQLite/FFI, simply dropping the EDA rules will remove those dependencies.

For EcereAudio, you can specify ECERE_AUDIO=n to build without.

For NCurses, X11 (if OpenGL is disabled as well) and bitmap formats, simply excluding the file from the Makefile should work. (Embedded graphics will no longer work if you disable PNG)

Adding -DECERE_NOTRUETYPE and -DECERE_NOFONTCONFIG to CPPFLAGS should remove the need for FontConfig and FreeType, but you will lose text rendering.

Only zlib is absolutely required by libecere (to support Ecere archives and resources, which could be disabled to build without), and none of them is required to build libecereCOM (the barebone eC runtime library).

Although it is recommended you use the libraries from your distribution, should they be useful to you, you will find versions of zlib, freetype, libungif, libjpeg, libpng, sqlite and libffi in the deps/ folder.

An old version of HarfBuzz is also included in ecere/src and always statically linked as part of Ecere unless you define ECERE_NOTRUETYPE.