Skip to content

Commit 5af78b3

Browse files
committed
2 parents 474b1d1 + 81c7422 commit 5af78b3

File tree

1 file changed

+20
-132
lines changed

1 file changed

+20
-132
lines changed

readme.md

Lines changed: 20 additions & 132 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
#Sloeber, the Arduino IDE for Eclipse <img style="float: right" src="https://avatars2.githubusercontent.com/u/25158881?v=3&s=200" height="50"/>
1+
# Sloeber, the Arduino IDE for Eclipse <img style="float: right" src="https://avatars2.githubusercontent.com/u/25158881?v=3&s=200" height="50"/>
22

33
The Eclipse IDE (Integrated Developement Environment) is a full featured programming editor with many fantastic features to help you code more quickly and easily. The Arduino IDE is great for what it does – but it doesn't do much to help writing, navigating and understanding your (and other people's) code.
44

@@ -31,22 +31,10 @@ Please install [git] (http://git-scm.com/downloads) and [maven] (http://maven.ap
3131
```bash
3232
git clone https://github.com/jantje/arduino-eclipse-plugin
3333
cd arduino-eclipse-plugin
34-
mvn clean -Dtest=RegressionTest verify
34+
mvn clean verify -DskipTests=true
3535
```
3636

37-
### Running the build from source IDE/Plugin
38-
39-
Sloeber can be started, e.g. on a 64-bit mac, with:
40-
41-
```bash
42-
open io.sloeber.product/target/products/io.sloeber.product/macosx/cocoa/x86_64/sloeber/sloeber-ide.app
43-
```
44-
45-
On Linux you can start Sloeber using the provided shell script:
46-
47-
```bash
48-
./build_then_launch_plugin.sh
49-
```
37+
### Running the Sloeber you just build
5038

5139
Windows
5240

@@ -57,36 +45,31 @@ Mac OSX and Linux
5745

5846
* ./build_then_launch_plugin.sh
5947

60-
=======
6148

6249
## Build Options
6350

6451
You can control the maven build with the following profiles: (this list may not be complete as new eclipse versions are added nearly immediately)
6552

66-
* oxygen
67-
* neon (builds against the neon repositories (4.6))
68-
* luna (builds agains the luna repositories (4.4))
69-
* mars (builds agains the mars repositories (4.5))
53+
* latest (default, builds against the latest versions)
54+
* 2018-09 (builds against the 2018-09 release. Eclipse stopped naming their releases)
55+
* photon (builds against the photon (4.8) repositories)
56+
* oxygen (builds against the oxygen (4.7) repositories)
57+
* SDK (builds a Sloeber you can program Sloeber in. With Java.)
7058
* win32 (builds for 32 bit windows)
7159
* win64
72-
* linux32
7360
* linux64
7461
* mac64
7562

7663
##### Examples
77-
mvn verify -Plinux32 -Dtest=RegressionTest (builds for neon and linux 32 bits)
78-
mvn verify -Pwin32,mars,linux32 -Dtest=RegressionTest
64+
mvn clean verify -Plinux32 -DskipTests=true (builds for neon and linux 32 bits)
65+
mvn clean verify -PSDK.latest -DskipTests=true (builds the Sloeber SDK. For Sloeber programmers.)
66+
mvn clean verify -P2018-09,linux64 -DskipTests=true (builds against 2018-09 and produces linux64 product)
67+
68+
To build for latest and the platform you are running on:
7969

80-
To build for neon and the platform you are running on:
81-
82-
mvn clean verify -Dtest=RegressionTest
83-
84-
### what is this -Dtest=RegressionTest about
85-
mvn builds and run tests automagically. However many junit tests in Sloeber are very extensive and will always have failures.
86-
By adding -Dtest=RegressionTest anly the regression test is run and this test should be successfull.
87-
88-
### Setting up a repository
70+
mvn clean verify -DskipTests=true
8971

72+
### Importing your build into another Eclipse
9073
If you want to import the latest code based plugin to another Eclipse setup you have then it is possible to setup a local repository to install the plugin you have just built. Just add a local repository with location ```arduino-eclipse-plugin/io.sloeber.product/target/repository```
9174

9275
![alt text](images_plugin_dev_setup/add_local_repository.png "Adding a local repository")
@@ -96,103 +79,18 @@ If you want to import the latest code based plugin to another Eclipse setup you
9679
* Fork the repository on GitHub (https://help.github.com/articles/fork-a-repo) for your changes. Note that your git link should look like this: https://github.com/YOUR_FORK/arduino-eclipse-plugin.git –– we will use it later.
9780
* Checkout locally
9881
* Make changes
99-
* Run ```mvn clean verify -Dtest=RegressionTest``` to build
100-
* Open the self-contained IDE and verify your fix
101-
* (Anything special about Travis CI & builds?)
102-
103-
#### Adding Eclipse PDE (Plugin Development Environment)
104-
105-
You should already have a supported Eclipse version installed (the CDT package makes a good start point). Let's add:
106-
107-
> Help → Install New Software → Work with: → All Available Sites
108-
109-
Now search/select the *Eclipse Plug-in Development Environment*
110-
111-
Note: This may take a while to download all the available packages.
112-
113-
![alt text](images_plugin_dev_setup/adding_pde.png "Adding the Plugin Development Environment")
114-
115-
116-
#### Adding Eclipse JDT (Java Development Tools)
117-
118-
If you're not using Eclipse with the JDT you'll need to install them. To do this you first need to open the Dialog for installing new Software:
119-
120-
> Help → Install New Software
121-
122-
There you select for *Work with:* *YOUR_ECLIPSE_RELEASE - http://download.eclipse.org/releases/YOUR_ECLIPSE_RELEASE*
123-
124-
After that, select
125-
126-
> Programming Languages → Eclipse Java Development Tools
127-
128-
#### Add EGit - Eclipse Git Team Provider
129-
130-
To install EGit you'll need to do the following:
131-
132-
> Help → Install New Software
133-
134-
There have to enter the following URL and press ENTER.
135-
136-
* http://download.eclipse.org/egit/updates
82+
* Run ```mvn clean verify -PSDK,latest -DskipTests=true``` to build
13783

138-
Now you have to open up the *Eclipse Git Team Provider* Category and select *Eclipse Git Team Provider*.
139-
Then press next and follow the instructions.
84+
After the build, find the Sloeber SDK product in the io.sloeber.product.sdk target directory. Unzip it somewhere in your home directory (mind you we cannot handle very long path names)
14085

141-
#### Add nebula (for the plotter)
142-
To install nebula you need the snapshot
86+
Note that Sloeber itself is NOT included in the Sloeber SDK.
14387

144-
> Help → Install New Software
14588

146-
There have to enter the following URL and press ENTER.
147-
* http://download.eclipse.org/nebula/releases/latest/
148-
149-
Now you have to open up the *Nebula Release all widgets and examples* Category and select *Nebula widgets*.
150-
Then press next and follow the instructions.
151-
152-
153-
### Importing an Arduino Plugin Project into Eclipse
154-
155-
After you installed all the plugins you'll need to restart Eclipse.
156-
157-
Eventually your plugin source code will be ready to be used with Eclipse. There are two ways to import your projects into Eclipse:
158-
159-
#### 1. Via a Command Line
160-
161-
If you're using Windows you should first install [GitHub for Windows](http://windows.github.com/).
162-
163-
First you should open a command line, and change the directory to the directory where you want to store your Project.
164-
165-
Now you have to clone your Fork:
166-
167-
```bash
168-
git clone https://github.com/YOUR_FORK/arduino-eclipse-plugin.git
169-
```
170-
171-
After that you should import the Project to Eclipse:
172-
173-
> File → Import → Plug-in Development → Plug-ins and Fragments
174-
175-
You should select all as shown in this picture.
176-
177-
![alt text](images_plugin_dev_setup/plugins_import_config.png "Adding the Plugin Development Environment")
178-
179-
You may need to change the directory to match the directory where you cloned the project into.
180-
181-
Press Next.
182-
183-
In the next window you have to select which Plug-in fragments you want to import.
184-
Select all that are appropriate:
185-
186-
![alt text](images_plugin_dev_setup/plugins_select.png "Adding the Plugin Development Environment")
187-
188-
Now press Finish, and it should import the selected Projects.
189-
190-
191-
#### 2. Via EGit interface.
89+
### Install the projects into the SDK via the EGit interface.
19290

19391
> File → Import → Git → Projects from Git → Clone URI
19492
195-
* Now type your fork in to URI, for example: ```https://github.com/YOUR_FORK/arduino-eclipse-plugin.git```
93+
* Now type your fork in to URI, for example: ```https://github.com/YOUR_USER/arduino-eclipse-plugin.git```
19694
* Press "Next".
19795
* Branch Selection: master
19896
* Local destination: ```/home/your_name/git/arduino-eclipse-plugin``` or ```c:\git\arduino-eclipse-plugin```
@@ -208,16 +106,6 @@ After all it should look like this:
208106

209107
![alt text](images_plugin_dev_setup/Imported_projects.png "Projects imported")
210108

211-
### Set the Code Formatting
212-
213-
To avoid having changes all the time because of different formatting this project uses the standard "Eclipse [built-in]".
214-
215-
Go to
216-
217-
> Window → Preferences → Java → Code Style → Formatter
218-
219-
and check this setting.
220-
221109
### Set the Warning Level
222110

223111
We want to keep the chance of missing a problem in the code to a minimum and to keep clean and tidy code. Development is

0 commit comments

Comments
 (0)