blob: 0642f20ce0eada109da23e342db98f72d72bd5a1 (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
|
<?xml version="1.0" encoding="UTF-8"?>
<configuration>
<!-- Package Description information to be picked up by www.eclipse.org/packages -->
<!-- PackageName is the title of your package
maintainer is the project or persons that are maintaining the package
iconurl is the fully qualified URL to the icon you wish to use on the site (48x48)
bugzillaComponentID is used to gather bugzilla information about your package. This should be given to you after provisioning of the package is finished
testPlan is the fully qualified URL to the test plan for this package
-->
<packageMetaData
packageName="Eclipse IDE for Embedded C/C++ Developers"
maintainer="Eclipse Packaging Project"
iconurl="http://www.eclipse.org/downloads/images/cdt.png"
bugzillaComponentId="embedcpp-package"
githubName="eclipse-embed-cdt/eclipse-plugins"
testPlan="http://www.eclipse.org/epp/testplan.php" >
<!-- Description is wrapped in CDATA tags to allow you to insert HTML code if necessary -->
<description><![CDATA[
An <a href="https://eclipse-embed-cdt.github.io">IDE for Embedded C/C++ developers</a>. It includes managed cross build plug-ins (<b>Arm</b> and <b>RISC-V</b>) and debug plug-ins (SEGGER <b>J-Link</b>, <b>OpenOCD</b>, <b>pyocd</b>, and <b>QEMU</b>), plus a number of templates to create ready to run blinky projects.
<br/>
<br/>
To avoid compatibility issues with pre 6.x plug-ins, it is recommended to <b>create a new workspace</b> with the new version and <b>import the projects</b> there.
]]></description>
<!-- packageTesters is a list of the people that are testing the package -->
<packageTesters>
<tester>Liviu Ionescu</tester>
<tester>Jonah Graham</tester>
</packageTesters>
</packageMetaData>
<!-- name, the name of the product, used in naming the created files. -->
<product name="eclipse-embedcpp-2022-09-M2" />
</configuration>
|
