|
|
Re: Generating PDE Target Definition files for a targlet located in the workspace [message #1803716 is a reply to message #1803709] |
Thu, 07 March 2019 08:29   |
Eclipse User |
|
|
|
My Setup file is located on a separate GIT.
Whereas my project sources and the target definition are located on an SVN (which will soon be migrated to another GIT).
I already achieved generating the .target from the setup to the project's sources. So my annotation is already in worksform.
My issue was how I may move the target requirements definition (the targlet) to the project's sources. So that whenever I switch to another project's branch or tag, I can rely on the appropriate definition, without using a different setup.
I'd like to keep 2 separated repositories, with :
- My setup in one git, which knows nothing about the project's versions and dependencies. (I always use the master branch during checkout, but may eventually switch manually later in the workspace)
- My project in a separate repository, along with the target platform requirements. Which may evolve from a version to another, and gets tagged at each new delivered version.
I could control the targlet definition to locate it in the project's repository, but then, that would mean the setup file (in the setup repository) points to the project's repository's head. So whenever I launch a perform Setup Tasks, target platform would be reset to the head one. Hence it would not be easy to work with older versions of the project.
Which is the reason why I was looking for a way to move the targlet itself to the workspace (or ${git.clone.location}).
A simple workaround would be to use the control described above and declare that anyone working on older versions must set the generated target platform manually and not use the Modular Target. But that would be quite painful for these cases, when I know the appropriate targlet is here in the workspace/git clone, just at reach of hand.
[Updated on: Thu, 07 March 2019 08:30] by Moderator
|
|
|
|
Re: Generating PDE Target Definition files for a targlet located in the workspace [message #1803743 is a reply to message #1803739] |
Fri, 08 March 2019 01:54  |
Eclipse User |
|
|
|
OK.
I was using the targlet as I was using the .tpd, to express the whole target platform requirements, without the Source Locator, and checkouting the sources independently.
That did not come to my mind that I could use the features from my project in the Targlet to take their dependencies dynamically without redunding them in the requirements.
Now, that makes much more sense. I'll try that as soon as I move my project sources to GIT.
Many thanks Ed.
|
|
|
Powered by
FUDForum. Page generated in 0.91634 seconds