Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 339590 - Need logic to build the TCF agent as a VxWorks component
Summary: Need logic to build the TCF agent as a VxWorks component
Status: RESOLVED NOT_ECLIPSE
Alias: None
Product: TCF
Classification: Tools
Component: Agent (show other bugs)
Version: unspecified   Edit
Hardware: PC Linux
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-03-10 15:39 EST by Peder Andersen CLA
Modified: 2011-05-02 19:45 EDT (History)
1 user (show)

See Also:


Attachments
Proposed changes (11.90 KB, patch)
2011-03-10 15:39 EST, Peder Andersen CLA
no flags Details | Diff
2 - static task instantiation (2.09 KB, patch)
2011-03-10 15:58 EST, Peder Andersen CLA
no flags Details | Diff
1 - proposed changes (11.89 KB, patch)
2011-03-10 17:01 EST, Peder Andersen CLA
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Peder Andersen CLA 2011-03-10 15:39:38 EST
Created attachment 190922 [details]
Proposed changes

The attached changeset adds the make/configuration rules necessary to build the TCF agent sources as part of a Wind River component.  Includes the "do_install.sh"
script used to install a checked-out source tree as a component, which is useful for developing with TCF but may not be desirable in the upstream repository.

This also adds a method for registering arbitrary services with the
VxWorks agent, similar to the plugin capability offered on other
platforms.  The first problem is that the external service lacks a
way of getting a handle to the agent's Protocol object.  Adding the
tcf_init_service() routine solves this, but there may be other
(concurrency, etc.) issues we will need to tackle as well.

Legal Message: I, Peder Andersen, declare that I developed attached code from
scratch, without referencing any 3rd party materials except material licensed
under the EPL and EDL. I am authorized by my employer, Wind River, to make this
contribution under the EPL and EDL.
Comment 1 Peder Andersen CLA 2011-03-10 15:58:40 EST
Created attachment 190926 [details]
2 - static task instantiation

This attached patch further improves the Vx support by statically declaring storage for TCF's tasks. 


Legal Message: I, Peder Andersen, declare that I developed attached code from
scratch, without referencing any 3rd party materials except material licensed
under the EPL and EDL. I am authorized by my employer, Wind River, to make this
contribution under the EPL and EDL.
Comment 2 Peder Andersen CLA 2011-03-10 17:01:40 EST
Created attachment 190935 [details]
1 - proposed changes

An updated version of the original patch: a more complete conversion from version 0.1 to version 0.3.

Legal Message: I, Peder Andersen, declare that I developed attached code from
scratch, without referencing any 3rd party materials except material licensed
under the EPL and EDL. I am authorized by my employer, Wind River, to make this
contribution under the EPL and EDL.
Comment 3 Eugene Tarassov CLA 2011-03-11 15:06:37 EST
Most of the files in the patch appears to be very specific for Wind River VxWorks build system. Is there a good reason to put them into the agent source directory?
In fact, one of file names in the patch points somewhere outside TCF repository:
.../osconfig/vxworks/cdf/01comp_tcfagent.cdf

I think theses files don't belong to TCF repository and need to be kept somewhere else.
Comment 4 Eugene Tarassov CLA 2011-04-29 14:37:20 EDT
I believe we agreed that VxWorks specific file should not be kept in the TCF repository.

The only other change in the patches is changing event_thread variable from static to extern. I suggest creating a separate Bugzilla for that. Also, changing the variable to be extern is rather dirty approach, we need to consider something more elegant.

Changing status to NOT_ECLIPSE.
Comment 5 Peder Andersen CLA 2011-05-02 19:45:29 EDT
(In reply to comment #4)
> The only other change in the patches is changing event_thread variable from
> static to extern. I suggest creating a separate Bugzilla for that.

Submitted bug 344514 for this issue.

> Also,
> changing the variable to be extern is rather dirty approach, we need to
> consider something more elegant.

Agreed, the attached changes around the event_thread were just meant to illustrate the problem.