|
|
| Re: Using Oomph to activate a regular target platform (not a Target [message #1816163 is a reply to message #1816154] |
Tue, 22 October 2019 21:12   |
|
Thanks Eike, but using the target file without extension did not do the trick.
<setupTask
xsi:type="pde:TargetPlatformTask"
name="target-platform-latest"/>
I attached the setup file, in case you can have a look at it to see my error.
>Out of curiosity, what was wrong with the Targlet Task?
Nothing, I just wanted to start with something we already have. At a later point I plan to generate the target file via Oomph based on the Targlet.
|
|
|
| Re: Using Oomph to activate a regular target platform (not a Target [message #1816230 is a reply to message #1816163] |
Thu, 24 October 2019 13:49 |
|
It seems you have no task to import the projects (in particular the one that contains the .target file) from the Git clone into the workspace. So PDE can't find the target definition. The Modular Target (Targlet) task would have done that for you. You can also use a task like this:
<?xml version="1.0" encoding="UTF-8"?>
<projects:ProjectsImportTask
xmi:version="2.0"
xmlns:xmi="http://www.omg.org/XMI"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:predicates="http://www.eclipse.org/oomph/predicates/1.0"
xmlns:projects="http://www.eclipse.org/oomph/setup/projects/1.0"
xsi:schemaLocation="http://www.eclipse.org/oomph/predicates/1.0 http://git.eclipse.org/c/oomph/org.eclipse.oomph.git/plain/setups/models/Predicates.ecore http://www.eclipse.org/oomph/setup/projects/1.0 http://git.eclipse.org/c/oomph/org.eclipse.oomph.git/plain/setups/models/Projects.ecore">
<sourceLocator
rootFolder="${git.clone.dartboard.location}"
locateNestedProjects="true">
<predicate
xsi:type="predicates:NotPredicate">
<operand
xsi:type="predicates:NamePredicate"
pattern="dartboard"/>
</predicate>
</sourceLocator>
</projects:ProjectsImportTask>
Cheers
/Eike
----
http://www.esc-net.de
http://thegordian.blogspot.com
http://twitter.com/eikestepper
|
|
|
|
|
|
|
|
|
|
|
|
|
| Re: Using Oomph to activate a regular target platform (not a Target [message #1854460 is a reply to message #1854361] |
Fri, 19 August 2022 09:52 |
 Florent Latombe
Messages: 8
Registered: December 2014 |
Junior Member |
|
|
Eike Stepper wrote on Tue, 16 August 2022 08:28Why does your team not want to use Oomph?
This question triggers me to hijack the topic to mention some issues I have encountered while using Oomph targlets, and which make me at least consider prefering TPD-based target platforms:
* When provisioning an IDE for several projects based on targlets, Oomph composes their targlets by creating one big targlet. This works at runtime but sort-of "breaks" the workflow where you want Oomph to generate your .target file. I described the issue here.
* I had some issues with platform-specific bits in the targlet-based generated .target file and its use in Tycho builds.
If my memory is correct, I needed the targlet to include platform-specific bits so that it resolves correctly on my Windows machine. But I did not want them in the generated .target file because Tycho somehow adds them at build time (?). With the platform-specific bits in the .target file, the Tycho build on a Linux machine complained about mac and windows stuff.
I settled the issue by manually running a script on the generated .target file to remove platform-specific bits.
[Updated on: Fri, 19 August 2022 10:05] Report message to a moderator |
|
|
|
Powered by
FUDForum. Page generated in 0.06455 seconds
] 
Search
Help
Register
Login
Home
