Change Details

The recommended way to set up your system and build Echo is to do the following. =Installing Dependencies= ==Prerequisites== # Ensure you have [[tools|Mercurial]] installed first. # Ensure you have access to [[/diffusion|the repositories]]. # ~~Ensure you have updated the host fingerprint as per the [[technical_documents/repositories/|Repositories]] page. This will avoid any certificate errors when attempting to clone.~~ ==On Unix-like platforms (Linux, BSD)== # Clone the {rEI} Echo Installer repository into the desired location: ## Open a Terminal and navigate to the directory where you want to clone into ## In a browser, navigate to the {rEI} page and click the {nav icon=download, name=Clone} button. This will show a URL to our server's copy of the project ## Run the command `hg clone` followed by the URL determined above; e.g. `hg clone https://developer.emblem.net.au/diffusion/EI/echoinstaller/` ## Enter your https://developer.emblem.net.au Phabricator username and VCS password. If you haven't set up a Version Control System password go to your [[/settings/panel/vcspassword/]] page and set it. # Navigate to the newly-cloned location in the Terminal. # Change to the `scripts` subdirectory using `cd scripts` # Run `sudo ./SetupEcho.sh` and follow the prompts. ## Note that `./SetupEcho.sh help` will display some help information. ## Note that this installs build tools for C++, such as the `g++` compiler. If it doesn't work, see [[tools/gpp/|Installing g++]]. NOTE: Before continuing with development you will need to logout then back in so your environment includes the Echo environment variables. Alternatively, when using a terminal you can type `source ~/.profile` and the environment variables will be set for that terminal session. Not doing one of these two things will result in compile and link errors as Echo and dependencies won't be found. ==On Windows== See [[projects/echo_3/building/windows/|Development on Windows]]. =Building Echo= The installer script will attempt to build Echo for all targets that were selected (including Debug and Release for Linux). If you want, or need to, to build manually you can do any one of the following: - Navigate to the cloned EchoInstaller directory and run `./BuildEcho.sh`. The default platform is linux. You can specify the platform you want usinhttps://developer.emblem.net.au/diffusion/EI/echoinstaller/g `PLATFORMS=platformname ./BuildEcho.sh` where `platformname` is the lowercase name of the platform. At the time of this writing the following were available: `linux, android, wii, windowscross`. - Navigate to the `echo3` project folder and issue the command `make CONF=Release` to build a Linux Release build, `CONF` can be set to the platform configuration you want to target. For example `make CONF=Wii` builds the Wii configuration. You can see possible configurations by opening `echo3/nbproject`. Each configuration has a makefile. - Open the `echo3` project in [[tools/netbeans|NetBeans]] and build using the IDE. =Verifying things worked= You should receive output if there were errors to the above processes. The installer will output the build result to a `buildlogs` folder that you can inspect to find errors. Please Please [[https://developer.emblem.net.au/maniphest/task/edit/form/1/|report errors]] that you come across since do want the process to be error free when possible. To verify that everything built and that you can run an Echo project you can run the tests. ``` make test ``` Will run through the unit tests for the library. A lot of these tests are graphical and are set to timeout after 30 seconds or so but you can close windows early. If 30 seconds elapses and the window doesn't close, chances are we forgot to add the timeout. Please [[/maniphest/task/edit/form/1/|report it]] so we can fix it. Once you're satisfied and have had fun playing with the tests you can move to the [[projects/echo_3/getting_started/|Getting started]] page for information on building an application.

NOTE: This document is out of date. It is no longer necessary to use {rEI}, instead you only need to clone {rE} and in the scripts folder are the setup scrips. These instructions should be essentially what you need to follow except use {rE} instead of {rEI}. The recommended way to set up your system and build Echo is to do the following. =Installing Dependencies= ==Prerequisites== # Ensure you have [[tools|Mercurial]] installed first. # Ensure you have access to [[/diffusion|the repositories]]. # ~~Ensure you have updated the host fingerprint as per the [[technical_documents/repositories/|Repositories]] page. This will avoid any certificate errors when attempting to clone.~~ ==On Unix-like platforms (Linux, BSD)== # Clone the {rEI} Echo Installer repository into the desired location: ## Open a Terminal and navigate to the directory where you want to clone into ## In a browser, navigate to the {rEI} page and click the {nav icon=download, name=Clone} button. This will show a URL to our server's copy of the project ## Run the command `hg clone` followed by the URL determined above; e.g. `hg clone https://developer.emblem.net.au/diffusion/EI/echoinstaller/` ## Enter your https://developer.emblem.net.au Phabricator username and VCS password. If you haven't set up a Version Control System password go to your [[/settings/panel/vcspassword/]] page and set it. # Navigate to the newly-cloned location in the Terminal. # Change to the `scripts` subdirectory using `cd scripts` # Run `sudo ./SetupEcho.sh` and follow the prompts. ## Note that `./SetupEcho.sh help` will display some help information. ## Note that this installs build tools for C++, such as the `g++` compiler. If it doesn't work, see [[tools/gpp/|Installing g++]]. NOTE: Before continuing with development you will need to logout then back in so your environment includes the Echo environment variables. Alternatively, when using a terminal you can type `source ~/.profile` and the environment variables will be set for that terminal session. Not doing one of these two things will result in compile and link errors as Echo and dependencies won't be found. ==On Windows== See [[projects/echo_3/building/windows/|Development on Windows]]. =Building Echo= The installer script will attempt to build Echo for all targets that were selected (including Debug and Release for Linux). If you want, or need to, to build manually you can do any one of the following: - Navigate to the cloned EchoInstaller directory and run `./BuildEcho.sh`. The default platform is linux. You can specify the platform you want usinhttps://developer.emblem.net.au/diffusion/EI/echoinstaller/g `PLATFORMS=platformname ./BuildEcho.sh` where `platformname` is the lowercase name of the platform. At the time of this writing the following were available: `linux, android, wii, windowscross`. - Navigate to the `echo3` project folder and issue the command `make CONF=Release` to build a Linux Release build, `CONF` can be set to the platform configuration you want to target. For example `make CONF=Wii` builds the Wii configuration. You can see possible configurations by opening `echo3/nbproject`. Each configuration has a makefile. - Open the `echo3` project in [[tools/netbeans|NetBeans]] and build using the IDE. =Verifying things worked= You should receive output if there were errors to the above processes. The installer will output the build result to a `buildlogs` folder that you can inspect to find errors. Please Please [[https://developer.emblem.net.au/maniphest/task/edit/form/1/|report errors]] that you come across since do want the process to be error free when possible. To verify that everything built and that you can run an Echo project you can run the tests. ``` make test ``` Will run through the unit tests for the library. A lot of these tests are graphical and are set to timeout after 30 seconds or so but you can close windows early. If 30 seconds elapses and the window doesn't close, chances are we forgot to add the timeout. Please [[/maniphest/task/edit/form/1/|report it]] so we can fix it. Once you're satisfied and have had fun playing with the tests you can move to the [[projects/echo_3/getting_started/|Getting started]] page for information on building an application.

NOTE: This document is out of date. It is no longer necessary to use {rEI}, instead you only need to clone {rE} and in the scripts folder are the setup scrips. These instructions should be essentially what you need to follow except use {rE} instead of {rEI}. The recommended way to set up your system and build Echo is to do the following. =Installing Dependencies= ==Prerequisites== # Ensure you have [[tools|Mercurial]] installed first. # Ensure you have access to [[/diffusion|the repositories]]. # ~~Ensure you have updated the host fingerprint as per the [[technical_documents/repositories/|Repositories]] page. This will avoid any certificate errors when attempting to clone.~~ ==On Unix-like platforms (Linux, BSD)== # Clone the {rEI} Echo Installer repository into the desired location: ## Open a Terminal and navigate to the directory where you want to clone into ## In a browser, navigate to the {rEI} page and click the {nav icon=download, name=Clone} button. This will show a URL to our server's copy of the project ## Run the command `hg clone` followed by the URL determined above; e.g. `hg clone https://developer.emblem.net.au/diffusion/EI/echoinstaller/` ## Enter your https://developer.emblem.net.au Phabricator username and VCS password. If you haven't set up a Version Control System password go to your [[/settings/panel/vcspassword/]] page and set it. # Navigate to the newly-cloned location in the Terminal. # Change to the `scripts` subdirectory using `cd scripts` # Run `sudo ./SetupEcho.sh` and follow the prompts. ## Note that `./SetupEcho.sh help` will display some help information. ## Note that this installs build tools for C++, such as the `g++` compiler. If it doesn't work, see [[tools/gpp/|Installing g++]]. NOTE: Before continuing with development you will need to logout then back in so your environment includes the Echo environment variables. Alternatively, when using a terminal you can type `source ~/.profile` and the environment variables will be set for that terminal session. Not doing one of these two things will result in compile and link errors as Echo and dependencies won't be found. ==On Windows== See [[projects/echo_3/building/windows/|Development on Windows]]. =Building Echo= The installer script will attempt to build Echo for all targets that were selected (including Debug and Release for Linux). If you want, or need to, to build manually you can do any one of the following: - Navigate to the cloned EchoInstaller directory and run `./BuildEcho.sh`. The default platform is linux. You can specify the platform you want usinhttps://developer.emblem.net.au/diffusion/EI/echoinstaller/g `PLATFORMS=platformname ./BuildEcho.sh` where `platformname` is the lowercase name of the platform. At the time of this writing the following were available: `linux, android, wii, windowscross`. - Navigate to the `echo3` project folder and issue the command `make CONF=Release` to build a Linux Release build, `CONF` can be set to the platform configuration you want to target. For example `make CONF=Wii` builds the Wii configuration. You can see possible configurations by opening `echo3/nbproject`. Each configuration has a makefile. - Open the `echo3` project in [[tools/netbeans|NetBeans]] and build using the IDE. =Verifying things worked= You should receive output if there were errors to the above processes. The installer will output the build result to a `buildlogs` folder that you can inspect to find errors. Please Please [[https://developer.emblem.net.au/maniphest/task/edit/form/1/|report errors]] that you come across since do want the process to be error free when possible. To verify that everything built and that you can run an Echo project you can run the tests. ``` make test ``` Will run through the unit tests for the library. A lot of these tests are graphical and are set to timeout after 30 seconds or so but you can close windows early. If 30 seconds elapses and the window doesn't close, chances are we forgot to add the timeout. Please [[/maniphest/task/edit/form/1/|report it]] so we can fix it. Once you're satisfied and have had fun playing with the tests you can move to the [[projects/echo_3/getting_started/|Getting started]] page for information on building an application.