Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

redhawk idl project #12

Open
jsrsarma opened this issue Jul 14, 2016 · 11 comments
Open

redhawk idl project #12

jsrsarma opened this issue Jul 14, 2016 · 11 comments

Comments

@jsrsarma
Copy link

I am trying to use REDHAWK IDL PROJECT to add a new IDL to IDL REPOSITORY
either the full paths or the OSSIEHOME paths are not being recognized.
CF::OctetSequence
PortTypes::UshortSequence both are not being recognized.
on the console, it builds with warnings, when I export it target sdr it is not showing up
in the IDL repository.
thanks
Sivaram


// #include "ossie/CF/PortTypes.idl"

include "/usr/local/redhawk/core/share/idl/ossie/CF/cf.idl

include "/usr/local/redhawk/core/share/idl/ossie/CF/PortTypes.idl"

module Packet
{
typedef unsigned short Stream;
typedef octet SeqNum;
struct StreamControlType
{
boolean endOfStream;
Stream streamId;
};
interface OctetStream : PayloadStatus
{
void pushPacket( in StreamControlType control, in CF::OctetSequence payload );
};

interface UshortStream : PayloadStatus
{
    void pushPacket( in StreamControlType control, in PortTypes::UshortSequence payload );
};

};


@tandersoft
Copy link

Check $OSSIEHOME/include/redhawk and $OSSIEHOME/lib or lib64 and see if
your idl project has really been installed. I believe that even though
RedHawk improved IDL Project so that building new interfaces is easier,
but dragging and dropping the project into Target SDR does NOT complete
the install. I believe that you still need to use commandline "make
install" to complete this (and you may have to be root depending on the
permissions you have set for $OSSIEHOME).

The IDL editor uses a different parser than the one that populates the
IDL Repository but it has the same bug that rejects the use of const
values. But this does not appear to be your current problem. However
the editor often marks a number of other valid IDL constructs as errors
but Project->Build Project or commandline make build it fine. But
perhaps you are not getting it installed successfully and so it does not
show up. If it were not recognizing your full path include statements
then it would not build with only warnings.

Your IDL code looks like only a small part of the standard Packet.idl
file but looks like it should build and install fine. The standard idl
file only has

#include "JtrsCorbaTypes.idl"

but it includes the CF and PortTypes.idl. Once you get the idl paths
set right you should not need any path in the include. In earlier
versions of RedHawk one also had to add additional entries to Libs and
Cflags in $OSSIEHOME/lib or lib64/pkgconfig/ossie.pc or to a project
specific .pc to set the paths for components using the interface in a
component to get them to build properly. I have not verified if this is
still necessary in RH 2.0.

On 7/14/2016 7:31 AM, jsrsarma wrote:

I am trying to use REDHAWK IDL PROJECT to add a new IDL to IDL REPOSITORY
either the full paths or the OSSIEHOME paths are not being recognized.
CF::OctetSequence
PortTypes::UshortSequence both are not being recognized.
on the console, it builds with warnings, when I export it target sdr
it is not showing up
in the IDL repository.
thanks
Sivaram


// #include "ossie/CF/PortTypes.idl"
#include "/usr/local/redhawk/core/share/idl/ossie/CF/cf.idl
#include "/usr/local/redhawk/core/share/idl/ossie/CF/PortTypes.idl"

module Packet
{
typedef unsigned short Stream;
typedef octet SeqNum;
struct StreamControlType
{
boolean endOfStream;
Stream streamId;
};
interface OctetStream : PayloadStatus
{
void pushPacket( in StreamControlType control, in CF::OctetSequence
payload );
};

|interface UshortStream : PayloadStatus { void pushPacket( in
StreamControlType control, in PortTypes::UshortSequence payload ); }; |

};



You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#12, or
mute the thread
https://github.com/notifications/unsubscribe/AKsdIskxU--URWSfzkdvaT21494F5EJPks5qVkhVgaJpZM4JMfqf.

Dr Terry L Anderson
TAndersoft

@jsrsarma
Copy link
Author

I do not have

"JtrsCorbaTypes.idl"

in the system, do i need to do anything to get this into the system.

thanks


From: Terry L Anderson notifications@github.com
Sent: Thursday, July 14, 2016 11:56 AM
To: RedhawkSDR/eclipse-gov.redhawk.ide
Cc: jsrsarma; Author
Subject: Re: [RedhawkSDR/eclipse-gov.redhawk.ide] redhawk idl project (#12)

Check $OSSIEHOME/include/redhawk and $OSSIEHOME/lib or lib64 and see if
your idl project has really been installed. I believe that even though
RedHawk improved IDL Project so that building new interfaces is easier,
but dragging and dropping the project into Target SDR does NOT complete
the install. I believe that you still need to use commandline "make
install" to complete this (and you may have to be root depending on the
permissions you have set for $OSSIEHOME).

The IDL editor uses a different parser than the one that populates the
IDL Repository but it has the same bug that rejects the use of const
values. But this does not appear to be your current problem. However
the editor often marks a number of other valid IDL constructs as errors
but Project->Build Project or commandline make build it fine. But
perhaps you are not getting it installed successfully and so it does not
show up. If it were not recognizing your full path include statements
then it would not build with only warnings.

Your IDL code looks like only a small part of the standard Packet.idl
file but looks like it should build and install fine. The standard idl
file only has

#include "JtrsCorbaTypes.idl"

but it includes the CF and PortTypes.idl. Once you get the idl paths
set right you should not need any path in the include. In earlier
versions of RedHawk one also had to add additional entries to Libs and
Cflags in $OSSIEHOME/lib or lib64/pkgconfig/ossie.pc or to a project
specific .pc to set the paths for components using the interface in a
component to get them to build properly. I have not verified if this is
still necessary in RH 2.0.

On 7/14/2016 7:31 AM, jsrsarma wrote:

I am trying to use REDHAWK IDL PROJECT to add a new IDL to IDL REPOSITORY
either the full paths or the OSSIEHOME paths are not being recognized.
CF::OctetSequence
PortTypes::UshortSequence both are not being recognized.
on the console, it builds with warnings, when I export it target sdr
it is not showing up
in the IDL repository.
thanks
Sivaram


// #include "ossie/CF/PortTypes.idl"
#include "/usr/local/redhawk/core/share/idl/ossie/CF/cf.idl
#include "/usr/local/redhawk/core/share/idl/ossie/CF/PortTypes.idl"

module Packet
{
typedef unsigned short Stream;
typedef octet SeqNum;
struct StreamControlType
{
boolean endOfStream;
Stream streamId;
};
interface OctetStream : PayloadStatus
{
void pushPacket( in StreamControlType control, in CF::OctetSequence
payload );
};

|interface UshortStream : PayloadStatus { void pushPacket( in
StreamControlType control, in PortTypes::UshortSequence payload ); }; |

};


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#12, or
mute the thread
https://github.com/notifications/unsubscribe/AKsdIskxU--URWSfzkdvaT21494F5EJPks5qVkhVgaJpZM4JMfqf.

Dr Terry L Anderson
TAndersoft

You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com//issues/12#issuecomment-232708689, or mute the threadhttps://github.com/notifications/unsubscribe/AAP25Z2otTY1ptxCR3q9y5htnPsjejZqks5qVlwugaJpZM4JMfqf.

@tandersoft
Copy link

I don't know what all IDL you are using, but JtrsCorbaTypes.idl is part
of the publicly released set of JTRS APIs and many of the others in the
set include this idl. It is similar to the module JTRS that you listed
earlier in this chain but has many more types than you showed. Perhaps
you are using an earlier version.

You can download the latest released set from

http://www.public.navy.mil/jtnc/sca/Pages/api1.aspx

If you download the whole set from the button near the top you get a zip
file that contains the documents and the idl. Unfortunately the idl is
a listing in PDF so you have to cut-&-paste or something to get it into
a text file to compile

You have to build and install those you want since RedHawk does not
natively support any of these.

On 7/14/2016 1:14 PM, jsrsarma wrote:

I do not have

"JtrsCorbaTypes.idl"

in the system, do i need to do anything to get this into the system.

thanks


From: Terry L Anderson notifications@github.com
Sent: Thursday, July 14, 2016 11:56 AM
To: RedhawkSDR/eclipse-gov.redhawk.ide
Cc: jsrsarma; Author
Subject: Re: [RedhawkSDR/eclipse-gov.redhawk.ide] redhawk idl project
(#12)

Check $OSSIEHOME/include/redhawk and $OSSIEHOME/lib or lib64 and see if
your idl project has really been installed. I believe that even though
RedHawk improved IDL Project so that building new interfaces is easier,
but dragging and dropping the project into Target SDR does NOT complete
the install. I believe that you still need to use commandline "make
install" to complete this (and you may have to be root depending on the
permissions you have set for $OSSIEHOME).

The IDL editor uses a different parser than the one that populates the
IDL Repository but it has the same bug that rejects the use of const
values. But this does not appear to be your current problem. However
the editor often marks a number of other valid IDL constructs as errors
but Project->Build Project or commandline make build it fine. But
perhaps you are not getting it installed successfully and so it does not
show up. If it were not recognizing your full path include statements
then it would not build with only warnings.

Your IDL code looks like only a small part of the standard Packet.idl
file but looks like it should build and install fine. The standard idl
file only has

#include "JtrsCorbaTypes.idl"

but it includes the CF and PortTypes.idl. Once you get the idl paths
set right you should not need any path in the include. In earlier
versions of RedHawk one also had to add additional entries to Libs and
Cflags in $OSSIEHOME/lib or lib64/pkgconfig/ossie.pc or to a project
specific .pc to set the paths for components using the interface in a
component to get them to build properly. I have not verified if this is
still necessary in RH 2.0.

On 7/14/2016 7:31 AM, jsrsarma wrote:

I am trying to use REDHAWK IDL PROJECT to add a new IDL to IDL
REPOSITORY
either the full paths or the OSSIEHOME paths are not being recognized.
CF::OctetSequence
PortTypes::UshortSequence both are not being recognized.
on the console, it builds with warnings, when I export it target sdr
it is not showing up
in the IDL repository.
thanks
Sivaram


// #include "ossie/CF/PortTypes.idl"
#include "/usr/local/redhawk/core/share/idl/ossie/CF/cf.idl
#include "/usr/local/redhawk/core/share/idl/ossie/CF/PortTypes.idl"

module Packet
{
typedef unsigned short Stream;
typedef octet SeqNum;
struct StreamControlType
{
boolean endOfStream;
Stream streamId;
};
interface OctetStream : PayloadStatus
{
void pushPacket( in StreamControlType control, in CF::OctetSequence
payload );
};

|interface UshortStream : PayloadStatus { void pushPacket( in
StreamControlType control, in PortTypes::UshortSequence payload ); }; |

};


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#12, or
mute the thread

https://github.com/notifications/unsubscribe/AKsdIskxU--URWSfzkdvaT21494F5EJPks5qVkhVgaJpZM4JMfqf.

Dr Terry L Anderson
TAndersoft

You are receiving this because you authored the thread.
Reply to this email directly, view it on
GitHubhttps://github.com//issues/12#issuecomment-232708689,
or mute the
threadhttps://github.com/notifications/unsubscribe/AAP25Z2otTY1ptxCR3q9y5htnPsjejZqks5qVlwugaJpZM4JMfqf.


You are receiving this because you commented.
Reply to this email directly, view it on GitHub
#12 (comment),
or mute the thread
https://github.com/notifications/unsubscribe/AKsdIjMg0-XeqRav7p46hUdFSW3_wtACks5qVpicgaJpZM4JMfqf.

Dr Terry L Anderson
TAndersoft

@jsrsarma
Copy link
Author

jsrsarma commented Aug 3, 2016

Terry

You have been helpful in the redhawk.

I am trying to know how to go about a new IDL project

where the new idl refers to CF.idl

This is the error I get:

src/cpp/redhawk/RS/RS.h:51:59: error: /usr/local/redhawk/core/share/idl/ossie/CF/CF.h: No such file or directory

In file included from src/cpp/redhawk/RS/RSSK.cpp:3:
I have set the project include path for IDL compilation as
/usr/local/redhawk/core/share/idl/ossie/CF/CF.idl
and I have also tried including in the idl file it self.
any suggestions
I appreciate
regards
sivaram


#include "CF.idl"

//#include "/usr/local/redhawk/core/share/idl/ossie/CF/CF.idl"

module RS {
struct ComponentInfoRecordType {
string id;
string version;
string name;
string xmlLocation;
CF::FileSystem fileSystem;
};
}


@tandersoft
Copy link

That is because RedHawk (or OSSIE) spelled the filename as "cf.idl"
rather than the JTRS standard "CF.idl". I just install a symbolic link

$ cd $OSSIEHOME/share/idl/ossie/CF

$ ln -s cf.idl CF.idl

to allow both spellings. Then you need the include in the include path

$OSSIEHOME/share/idl/ossie/CF

but NOT the filename.

On 8/3/2016 10:40 AM, jsrsarma wrote:

Terry

You have been helpful in the redhawk.

I am trying to know how to go about a new IDL project

where the new idl refers to CF.idl

This is the error I get:

src/cpp/redhawk/RS/RS.h:51:59: error:
/usr/local/redhawk/core/share/idl/ossie/CF/CF.h: No such file or directory

In file included from src/cpp/redhawk/RS/RSSK.cpp:3:
I have set the project include path for IDL compilation as
/usr/local/redhawk/core/share/idl/ossie/CF/CF.idl
and I have also tried including in the idl file it self.
any suggestions
I appreciate
regards
sivaram


#include "CF.idl"

//#include "/usr/local/redhawk/core/share/idl/ossie/CF/CF.idl"

module RS {
struct ComponentInfoRecordType {
string id;
string version;
string name;
string xmlLocation;
CF::FileSystem fileSystem;
};
}



You are receiving this because you commented.
Reply to this email directly, view it on GitHub
#12 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AKsdIt2sBcmfk4o9WX4_aEHT9RJ0jpfcks5qcNKMgaJpZM4JMfqf.

Dr Terry L Anderson
TAndersoft

@jsrsarma
Copy link
Author

jsrsarma commented Aug 3, 2016

Hello Terry

when you have a minute, please take a look

I really appreciate it.

regards

Sivaram

I have created an idl project to install SCWIS interface based on the idl files.
when I tried to build using the sudo make install
the CPP works fine with no errors
but java step fails,
resulting in not being shown up as installed in /usr/local/redhawk/core/include/redhawk

Eventhough the RS module is installed , the given below are the new IDL modules I have ported.

burstio BURSTIO FRONTEND JTRS MIM OE PACKET RS SIMPLEPACKET

the errors -------------- C++ build is fine with no errors
find src/java -name '*.java' > build/java.files
/usr/lib/jvm/java/bin/javac -cp /usr/local/redhawk/core/lib/CFInterfaces.jar:/usr/local/redhawk/core/lib/BULKIOInterfaces.jar: -target 1.5 -source 1.5 -d build/java @build/java.files
warning: [options] bootstrap class path not set in conjunction with -source 1.5
src/java/SCWIS/SC_WFOperations.java:38: error: package RS does not exist
void initializeWaveform (RS.ChannelID channelID, String waveformPreset) throws SCWIS.SC_WFPackage.ProcessingSC_CommandException;
^
src/java/SCWIS/SC_WFPOATie.java:62: error: package RS does not exist
public void initializeWaveform (RS.ChannelID channelID, String waveformPreset) throws SCWIS.SC_WFPackage.ProcessingSC_CommandException
^
src/java/SCWIS/_SC_WFStub.java:39: error: package RS does not exist
public void initializeWaveform (RS.ChannelID channelID, String waveformPreset) throws SCWIS.SC_WFPackage.ProcessingSC_CommandException
^
src/java/SCWIS/SC_WFPOA.java:65: error: package RS does not exist
RS.ChannelID channelID = RS.ChannelIDHelper.read (in);

SCWIS.idl_______
#include "CF.idl"
#include "RS.idl"
module SCWIS {
CF::Application createWaveform (
in string baseWF_Name
)
void initializeWaveform (
in RS::ChannelID channelID,
in string waveformPreset
)
}

RS.idl_______

#include "CF.idl"
module RS {
struct ComponentInfoRecordType {
string id;
string version;
string name;
string xmlLocation;
CF::FileSystem fileSystem;
};
}

Dr Terry L Anderson
TAndersoft

You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com//issues/12#issuecomment-237321914, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AAP25YpNsH29oD93HubA6m9Y7GupUQftks5qcNsNgaJpZM4JMfqf.

@tandersoft
Copy link

I have also had some (but not all) interface/IDL projects fail the java
part of make. I have no interest in using Java so I have never
investigated the issue. But since the java build is part of the install
step in make it never installs the cpp parts either. So I have just
installed the parts manually after they build correctly.

$OSSIEHOME/share/idl/redhawk//*.idl

$OSSIEHOME/include/redhawk//*.h

$OSSIEHOME/lib or lib64/Interfaces.*

I imagine that one could delete the java make step and get make install
to work and do these installs, I just have not bothered.

If you need the java interfaces, then this will of course not work. I
am sorry but I do not know why the java fails. It only fails for one of
the four IDL projects that I have built and used and I am not sure why.
I know that you may need to add lines to:

$OSSIEHOME/lib/python/redhawk/codegen/lang/idl.py

adding additional

idlRepo.adSearchPath(os.path.join(os.environ['OSSIEHOME'],
"share/idl/redhawk/'))

but I believe this is only to allow USING an installed package, but if
you installed the RS package and it is referenced in your SCWIS idl
files then you may need this but even this has not been enough for me
with one package.

On 8/3/2016 12:11 PM, jsrsarma wrote:

Hello Terry

when you have a minute, please take a look

I really appreciate it.

regards

Sivaram

I have created an idl project to install SCWIS interface based on the
idl files.
when I tried to build using the sudo make install
the CPP works fine with no errors
but java step fails,
resulting in not being shown up as installed in
/usr/local/redhawk/core/include/redhawk

Eventhough the RS module is installed , the given below are the new
IDL modules I have ported.

burstio BURSTIO FRONTEND JTRS MIM OE PACKET RS SIMPLEPACKET

the errors -------------- C++ build is fine with no errors
find src/java -name '*.java' > build/java.files
/usr/lib/jvm/java/bin/javac -cp
/usr/local/redhawk/core/lib/CFInterfaces.jar:/usr/local/redhawk/core/lib/BULKIOInterfaces.jar:
-target 1.5 -source 1.5 -d build/java @build/java.files
warning: [options] bootstrap class path not set in conjunction with
-source 1.5
src/java/SCWIS/SC_WFOperations.java:38: error: package RS does not exist
void initializeWaveform (RS.ChannelID channelID, String
waveformPreset) throws SCWIS.SC_WFPackage.ProcessingSC_CommandException;
^
src/java/SCWIS/SC_WFPOATie.java:62: error: package RS does not exist
public void initializeWaveform (RS.ChannelID channelID, String
waveformPreset) throws SCWIS.SC_WFPackage.ProcessingSC_CommandException
^
src/java/SCWIS/_SC_WFStub.java:39: error: package RS does not exist
public void initializeWaveform (RS.ChannelID channelID, String
waveformPreset) throws SCWIS.SC_WFPackage.ProcessingSC_CommandException
^
src/java/SCWIS/SC_WFPOA.java:65: error: package RS does not exist
RS.ChannelID channelID = RS.ChannelIDHelper.read (in);

SCWIS.idl_______
#include "CF.idl"
#include "RS.idl"
module SCWIS {
CF::Application createWaveform (
in string baseWF_Name
)
void initializeWaveform (
in RS::ChannelID channelID,
in string waveformPreset
)
}

RS.idl_______

#include "CF.idl"
module RS {
struct ComponentInfoRecordType {
string id;
string version;
string name;
string xmlLocation;
CF::FileSystem fileSystem;
};
}

Dr Terry L Anderson
TAndersoft

You are receiving this because you authored the thread.
Reply to this email directly, view it on
GitHubhttps://github.com//issues/12#issuecomment-237321914,
or mute the
threadhttps://github.com/notifications/unsubscribe-auth/AAP25YpNsH29oD93HubA6m9Y7GupUQftks5qcNsNgaJpZM4JMfqf.


You are receiving this because you commented.
Reply to this email directly, view it on GitHub
#12 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AKsdIv9oQpWrB-ZWM5oB4RsM-pJxXFPlks5qcOf0gaJpZM4JMfqf.

Dr Terry L Anderson
TAndersoft

@jsrsarma
Copy link
Author

jsrsarma commented Aug 3, 2016

I am not using java, I am only interested in CPP generation and installation

and later would like to see them in the eclipse ide drop down menu for the IDL repository.

I have copied the following two (it is part of the of the make installation sudo make install)

$OSSIEHOME/share/idl/redhawk//*.idl

$OSSIEHOME/include/redhawk//*.h

There are jar files in the lib directory which are not built and not needed.

what needs to be moved for the $OSSIEHOME/lib or lib64/Interfaces.*

thanks

sivaram


From: Terry L Anderson notifications@github.com
Sent: Wednesday, August 3, 2016 4:13 PM
To: RedhawkSDR/eclipse-gov.redhawk.ide
Cc: jsrsarma; Author
Subject: Re: [RedhawkSDR/eclipse-gov.redhawk.ide] redhawk idl project (#12)

I have also had some (but not all) interface/IDL projects fail the java
part of make. I have no interest in using Java so I have never
investigated the issue. But since the java build is part of the install
step in make it never installs the cpp parts either. So I have just
installed the parts manually after they build correctly.

$OSSIEHOME/share/idl/redhawk//*.idl

$OSSIEHOME/include/redhawk//*.h

$OSSIEHOME/lib or lib64/Interfaces.*

I imagine that one could delete the java make step and get make install
to work and do these installs, I just have not bothered.

If you need the java interfaces, then this will of course not work. I
am sorry but I do not know why the java fails. It only fails for one of
the four IDL projects that I have built and used and I am not sure why.
I know that you may need to add lines to:

$OSSIEHOME/lib/python/redhawk/codegen/lang/idl.py

adding additional

idlRepo.adSearchPath(os.path.join(os.environ['OSSIEHOME'],
"share/idl/redhawk/'))

but I believe this is only to allow USING an installed package, but if
you installed the RS package and it is referenced in your SCWIS idl
files then you may need this but even this has not been enough for me
with one package.

On 8/3/2016 12:11 PM, jsrsarma wrote:

Hello Terry

when you have a minute, please take a look

I really appreciate it.

regards

Sivaram

I have created an idl project to install SCWIS interface based on the
idl files.
when I tried to build using the sudo make install
the CPP works fine with no errors
but java step fails,
resulting in not being shown up as installed in
/usr/local/redhawk/core/include/redhawk

Eventhough the RS module is installed , the given below are the new
IDL modules I have ported.

burstio BURSTIO FRONTEND JTRS MIM OE PACKET RS SIMPLEPACKET

the errors -------------- C++ build is fine with no errors
find src/java -name '*.java' > build/java.files
/usr/lib/jvm/java/bin/javac -cp
/usr/local/redhawk/core/lib/CFInterfaces.jar:/usr/local/redhawk/core/lib/BULKIOInterfaces.jar:
-target 1.5 -source 1.5 -d build/java @build/java.files
warning: [options] bootstrap class path not set in conjunction with
-source 1.5
src/java/SCWIS/SC_WFOperations.java:38: error: package RS does not exist
void initializeWaveform (RS.ChannelID channelID, String
waveformPreset) throws SCWIS.SC_WFPackage.ProcessingSC_CommandException;
^
src/java/SCWIS/SC_WFPOATie.java:62: error: package RS does not exist
public void initializeWaveform (RS.ChannelID channelID, String
waveformPreset) throws SCWIS.SC_WFPackage.ProcessingSC_CommandException
^
src/java/SCWIS/_SC_WFStub.java:39: error: package RS does not exist
public void initializeWaveform (RS.ChannelID channelID, String
waveformPreset) throws SCWIS.SC_WFPackage.ProcessingSC_CommandException
^
src/java/SCWIS/SC_WFPOA.java:65: error: package RS does not exist
RS.ChannelID channelID = RS.ChannelIDHelper.read (in);

SCWIS.idl_______
#include "CF.idl"
#include "RS.idl"
module SCWIS {
CF::Application createWaveform (
in string baseWF_Name
)
void initializeWaveform (
in RS::ChannelID channelID,
in string waveformPreset
)
}

RS.idl_______

#include "CF.idl"
module RS {
struct ComponentInfoRecordType {
string id;
string version;
string name;
string xmlLocation;
CF::FileSystem fileSystem;
};
}

Dr Terry L Anderson
TAndersoft

You are receiving this because you authored the thread.
Reply to this email directly, view it on
GitHubhttps://github.com//issues/12#issuecomment-237321914,
or mute the
threadhttps://github.com/notifications/unsubscribe-auth/AAP25YpNsH29oD93HubA6m9Y7GupUQftks5qcNsNgaJpZM4JMfqf.

You are receiving this because you commented.
Reply to this email directly, view it on GitHub
#12 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AKsdIv9oQpWrB-ZWM5oB4RsM-pJxXFPlks5qcOf0gaJpZM4JMfqf.

Dr Terry L Anderson
TAndersoft

You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com//issues/12#issuecomment-237357764, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AAP25Ul2j2rCXt0Z6pKwnm6J6O7ftVetks5qcPZ3gaJpZM4JMfqf.

@tandersoft
Copy link

depending on your version and whether you have 32 or 64bit CentOS you
need to add to $OSSIEHOME/lib or lib64

libInterfaces.a

libInterfaces.la

libInterfaces.so

libInterfaces.so.0

libInterfaces.so.0.0.0

you will find these in the directory .libs in your workspace/

note that only the .a and the .so.0.0.0 are real files the other three
are symbolic links. It may be easier to simply remake the three
symbolic links in the lib directory after copying the two real files
(use ls -l to see what the links were).

You will also fine a file

libInterfaces.lai

which you do not need.
This should be enough to have your interfaces appear in the IDL
Repository and allow you to use them.

On 8/3/2016 2:19 PM, jsrsarma wrote:

I am not using java, I am only interested in CPP generation and
installation

and later would like to see them in the eclipse ide drop down menu for
the IDL repository.

I have copied the following two (it is part of the of the make
installation sudo make install)

$OSSIEHOME/share/idl/redhawk//*.idl

$OSSIEHOME/include/redhawk//*.h

There are jar files in the lib directory which are not built and not
needed.

what needs to be moved for the $OSSIEHOME/lib or
lib64/Interfaces.*

thanks

sivaram


From: Terry L Anderson notifications@github.com
Sent: Wednesday, August 3, 2016 4:13 PM
To: RedhawkSDR/eclipse-gov.redhawk.ide
Cc: jsrsarma; Author
Subject: Re: [RedhawkSDR/eclipse-gov.redhawk.ide] redhawk idl project
(#12)

I have also had some (but not all) interface/IDL projects fail the java
part of make. I have no interest in using Java so I have never
investigated the issue. But since the java build is part of the install
step in make it never installs the cpp parts either. So I have just
installed the parts manually after they build correctly.

$OSSIEHOME/share/idl/redhawk//*.idl

$OSSIEHOME/include/redhawk//*.h

$OSSIEHOME/lib or lib64/Interfaces.*

I imagine that one could delete the java make step and get make install
to work and do these installs, I just have not bothered.

If you need the java interfaces, then this will of course not work. I
am sorry but I do not know why the java fails. It only fails for one of
the four IDL projects that I have built and used and I am not sure why.
I know that you may need to add lines to:

$OSSIEHOME/lib/python/redhawk/codegen/lang/idl.py

adding additional

idlRepo.adSearchPath(os.path.join(os.environ['OSSIEHOME'],
"share/idl/redhawk/'))

but I believe this is only to allow USING an installed package, but if
you installed the RS package and it is referenced in your SCWIS idl
files then you may need this but even this has not been enough for me
with one package.

On 8/3/2016 12:11 PM, jsrsarma wrote:

Hello Terry

when you have a minute, please take a look

I really appreciate it.

regards

Sivaram

I have created an idl project to install SCWIS interface based on the
idl files.
when I tried to build using the sudo make install
the CPP works fine with no errors
but java step fails,
resulting in not being shown up as installed in
/usr/local/redhawk/core/include/redhawk

Eventhough the RS module is installed , the given below are the new
IDL modules I have ported.

burstio BURSTIO FRONTEND JTRS MIM OE PACKET RS SIMPLEPACKET

the errors -------------- C++ build is fine with no errors
find src/java -name '*.java' > build/java.files
/usr/lib/jvm/java/bin/javac -cp

/usr/local/redhawk/core/lib/CFInterfaces.jar:/usr/local/redhawk/core/lib/BULKIOInterfaces.jar:
-target 1.5 -source 1.5 -d build/java @build/java.files
warning: [options] bootstrap class path not set in conjunction with
-source 1.5
src/java/SCWIS/SC_WFOperations.java:38: error: package RS does not exist
void initializeWaveform (RS.ChannelID channelID, String
waveformPreset) throws SCWIS.SC_WFPackage.ProcessingSC_CommandException;
^
src/java/SCWIS/SC_WFPOATie.java:62: error: package RS does not exist
public void initializeWaveform (RS.ChannelID channelID, String
waveformPreset) throws SCWIS.SC_WFPackage.ProcessingSC_CommandException
^
src/java/SCWIS/_SC_WFStub.java:39: error: package RS does not exist
public void initializeWaveform (RS.ChannelID channelID, String
waveformPreset) throws SCWIS.SC_WFPackage.ProcessingSC_CommandException
^
src/java/SCWIS/SC_WFPOA.java:65: error: package RS does not exist
RS.ChannelID channelID = RS.ChannelIDHelper.read (in);

SCWIS.idl_______
#include "CF.idl"
#include "RS.idl"
module SCWIS {
CF::Application createWaveform (
in string baseWF_Name
)
void initializeWaveform (
in RS::ChannelID channelID,
in string waveformPreset
)
}

RS.idl_______

#include "CF.idl"
module RS {
struct ComponentInfoRecordType {
string id;
string version;
string name;
string xmlLocation;
CF::FileSystem fileSystem;
};
}

Dr Terry L Anderson
TAndersoft

You are receiving this because you authored the thread.
Reply to this email directly, view it on

GitHubhttps://github.com//issues/12#issuecomment-237321914,
or mute the

threadhttps://github.com/notifications/unsubscribe-auth/AAP25YpNsH29oD93HubA6m9Y7GupUQftks5qcNsNgaJpZM4JMfqf.

You are receiving this because you commented.
Reply to this email directly, view it on GitHub

#12 (comment),
or mute the thread

https://github.com/notifications/unsubscribe-auth/AKsdIv9oQpWrB-ZWM5oB4RsM-pJxXFPlks5qcOf0gaJpZM4JMfqf.

Dr Terry L Anderson
TAndersoft

You are receiving this because you authored the thread.
Reply to this email directly, view it on
GitHubhttps://github.com//issues/12#issuecomment-237357764,
or mute the
threadhttps://github.com/notifications/unsubscribe-auth/AAP25Ul2j2rCXt0Z6pKwnm6J6O7ftVetks5qcPZ3gaJpZM4JMfqf.


You are receiving this because you commented.
Reply to this email directly, view it on GitHub
#12 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AKsdItlObW6LvDfNJh90YgMPhObA1ut_ks5qcQXLgaJpZM4JMfqf.

Dr Terry L Anderson
TAndersoft

@jsrsarma
Copy link
Author

jsrsarma commented Aug 8, 2016

Terry
I have included the path in the Makefile
for IDL_INCLUDES, IDLJ_INCLUDES, PY_IDL_INCLUDES
so it builds using sudo make install
But I do not see it in the expanded Target SDR -> IDL Repository.
The IDL in the eclipse ide still shows the errors about the #include "CF.idl"

Any ideas.
I appreciate.
thanks
sivaram

#include "CF.idl"
module RS {
struct ComponentInfoRecordType {
string id;
string version;
string name;
string xmlLocation;
CF::FileSystem fileSystem;
};
}


From: Terry L Anderson notifications@github.com
Sent: Wednesday, August 3, 2016 6:05 PM
To: RedhawkSDR/eclipse-gov.redhawk.ide
Cc: jsrsarma; Author
Subject: Re: [RedhawkSDR/eclipse-gov.redhawk.ide] redhawk idl project (#12)

depending on your version and whether you have 32 or 64bit CentOS you
need to add to $OSSIEHOME/lib or lib64

libInterfaces.a

libInterfaces.la

libInterfaces.so

libInterfaces.so.0

libInterfaces.so.0.0.0

you will find these in the directory .libs in your workspace/

note that only the .a and the .so.0.0.0 are real files the other three
are symbolic links. It may be easier to simply remake the three
symbolic links in the lib directory after copying the two real files
(use ls -l to see what the links were).

You will also fine a file

libInterfaces.lai

which you do not need.
This should be enough to have your interfaces appear in the IDL
Repository and allow you to use them.

On 8/3/2016 2:19 PM, jsrsarma wrote:

I am not using java, I am only interested in CPP generation and
installation

and later would like to see them in the eclipse ide drop down menu for
the IDL repository.

I have copied the following two (it is part of the of the make
installation sudo make install)

$OSSIEHOME/share/idl/redhawk//*.idl

$OSSIEHOME/include/redhawk//*.h

There are jar files in the lib directory which are not built and not
needed.

what needs to be moved for the $OSSIEHOME/lib or
lib64/Interfaces.*

thanks

sivaram


From: Terry L Anderson notifications@github.com
Sent: Wednesday, August 3, 2016 4:13 PM
To: RedhawkSDR/eclipse-gov.redhawk.ide
Cc: jsrsarma; Author
Subject: Re: [RedhawkSDR/eclipse-gov.redhawk.ide] redhawk idl project
(#12)

I have also had some (but not all) interface/IDL projects fail the java
part of make. I have no interest in using Java so I have never
investigated the issue. But since the java build is part of the install
step in make it never installs the cpp parts either. So I have just
installed the parts manually after they build correctly.

$OSSIEHOME/share/idl/redhawk//*.idl

$OSSIEHOME/include/redhawk//*.h

$OSSIEHOME/lib or lib64/Interfaces.*

I imagine that one could delete the java make step and get make install
to work and do these installs, I just have not bothered.

If you need the java interfaces, then this will of course not work. I
am sorry but I do not know why the java fails. It only fails for one of
the four IDL projects that I have built and used and I am not sure why.
I know that you may need to add lines to:

$OSSIEHOME/lib/python/redhawk/codegen/lang/idl.py

adding additional

idlRepo.adSearchPath(os.path.join(os.environ['OSSIEHOME'],
"share/idl/redhawk/'))

but I believe this is only to allow USING an installed package, but if
you installed the RS package and it is referenced in your SCWIS idl
files then you may need this but even this has not been enough for me
with one package.

On 8/3/2016 12:11 PM, jsrsarma wrote:

Hello Terry

when you have a minute, please take a look

I really appreciate it.

regards

Sivaram

I have created an idl project to install SCWIS interface based on the
idl files.
when I tried to build using the sudo make install
the CPP works fine with no errors
but java step fails,
resulting in not being shown up as installed in
/usr/local/redhawk/core/include/redhawk

Eventhough the RS module is installed , the given below are the new
IDL modules I have ported.

burstio BURSTIO FRONTEND JTRS MIM OE PACKET RS SIMPLEPACKET

the errors -------------- C++ build is fine with no errors
find src/java -name '*.java' > build/java.files
/usr/lib/jvm/java/bin/javac -cp

/usr/local/redhawk/core/lib/CFInterfaces.jar:/usr/local/redhawk/core/lib/BULKIOInterfaces.jar:
-target 1.5 -source 1.5 -d build/java @build/java.files
warning: [options] bootstrap class path not set in conjunction with
-source 1.5
src/java/SCWIS/SC_WFOperations.java:38: error: package RS does not exist
void initializeWaveform (RS.ChannelID channelID, String
waveformPreset) throws SCWIS.SC_WFPackage.ProcessingSC_CommandException;
^
src/java/SCWIS/SC_WFPOATie.java:62: error: package RS does not exist
public void initializeWaveform (RS.ChannelID channelID, String
waveformPreset) throws SCWIS.SC_WFPackage.ProcessingSC_CommandException
^
src/java/SCWIS/_SC_WFStub.java:39: error: package RS does not exist
public void initializeWaveform (RS.ChannelID channelID, String
waveformPreset) throws SCWIS.SC_WFPackage.ProcessingSC_CommandException
^
src/java/SCWIS/SC_WFPOA.java:65: error: package RS does not exist
RS.ChannelID channelID = RS.ChannelIDHelper.read (in);

SCWIS.idl_______
#include "CF.idl"
#include "RS.idl"
module SCWIS {
CF::Application createWaveform (
in string baseWF_Name
)
void initializeWaveform (
in RS::ChannelID channelID,
in string waveformPreset
)
}

RS.idl_______

#include "CF.idl"
module RS {
struct ComponentInfoRecordType {
string id;
string version;
string name;
string xmlLocation;
CF::FileSystem fileSystem;
};
}

Dr Terry L Anderson
TAndersoft

You are receiving this because you authored the thread.
Reply to this email directly, view it on

GitHubhttps://github.com//issues/12#issuecomment-237321914,
or mute the

threadhttps://github.com/notifications/unsubscribe-auth/AAP25YpNsH29oD93HubA6m9Y7GupUQftks5qcNsNgaJpZM4JMfqf.

You are receiving this because you commented.
Reply to this email directly, view it on GitHub

#12 (comment),
or mute the thread

https://github.com/notifications/unsubscribe-auth/AKsdIv9oQpWrB-ZWM5oB4RsM-pJxXFPlks5qcOf0gaJpZM4JMfqf.

Dr Terry L Anderson
TAndersoft

You are receiving this because you authored the thread.
Reply to this email directly, view it on
GitHubhttps://github.com//issues/12#issuecomment-237357764,
or mute the
threadhttps://github.com/notifications/unsubscribe-auth/AAP25Ul2j2rCXt0Z6pKwnm6J6O7ftVetks5qcPZ3gaJpZM4JMfqf.


You are receiving this because you commented.
Reply to this email directly, view it on GitHub
#12 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AKsdItlObW6LvDfNJh90YgMPhObA1ut_ks5qcQXLgaJpZM4JMfqf.

Dr Terry L Anderson
TAndersoft


You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com//issues/12#issuecomment-237389663, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AAP25eBDkgV9QMLfpr5VV_ivBksvl_ynks5qcRCpgaJpZM4JMfqf.

@tandersoft
Copy link

But did you add the symbolic link

$ cd $OSSIEHOME/share/idl/ossie/CF

$ ln -s cf.idl CF.idl

that I told you about before. OSSIE/RedHawk spells the file name
differently than the JTRS Standard. And make sure that
$OSSIEHOME/share/idl/ossie/CF is in the RedHawk
Window->Preferences->REDHAWK->Target Platform->IDL Locations list not
just ossie but ossie/CF must be there.

On 8/8/2016 9:34 AM, jsrsarma wrote:

Terry
I have included the path in the Makefile
for IDL_INCLUDES, IDLJ_INCLUDES, PY_IDL_INCLUDES
so it builds using sudo make install
But I do not see it in the expanded Target SDR -> IDL Repository.
The IDL in the eclipse ide still shows the errors about the #include
"CF.idl"

Any ideas.
I appreciate.
thanks
sivaram

#include "CF.idl"
module RS {
struct ComponentInfoRecordType {
string id;
string version;
string name;
string xmlLocation;
CF::FileSystem fileSystem;
};
}


From: Terry L Anderson notifications@github.com
Sent: Wednesday, August 3, 2016 6:05 PM
To: RedhawkSDR/eclipse-gov.redhawk.ide
Cc: jsrsarma; Author
Subject: Re: [RedhawkSDR/eclipse-gov.redhawk.ide] redhawk idl project
(#12)

depending on your version and whether you have 32 or 64bit CentOS you
need to add to $OSSIEHOME/lib or lib64

libInterfaces.a

libInterfaces.la

libInterfaces.so

libInterfaces.so.0

libInterfaces.so.0.0.0

you will find these in the directory .libs in your workspace/

note that only the .a and the .so.0.0.0 are real files the other three
are symbolic links. It may be easier to simply remake the three
symbolic links in the lib directory after copying the two real files
(use ls -l to see what the links were).

You will also fine a file

libInterfaces.lai

which you do not need.
This should be enough to have your interfaces appear in the IDL
Repository and allow you to use them.

On 8/3/2016 2:19 PM, jsrsarma wrote:

I am not using java, I am only interested in CPP generation and
installation

and later would like to see them in the eclipse ide drop down menu for
the IDL repository.

I have copied the following two (it is part of the of the make
installation sudo make install)

$OSSIEHOME/share/idl/redhawk//*.idl

$OSSIEHOME/include/redhawk//*.h

There are jar files in the lib directory which are not built and not
needed.

what needs to be moved for the $OSSIEHOME/lib or
lib64/Interfaces.*

thanks

sivaram


From: Terry L Anderson notifications@github.com
Sent: Wednesday, August 3, 2016 4:13 PM
To: RedhawkSDR/eclipse-gov.redhawk.ide
Cc: jsrsarma; Author
Subject: Re: [RedhawkSDR/eclipse-gov.redhawk.ide] redhawk idl project
(#12)

I have also had some (but not all) interface/IDL projects fail the java
part of make. I have no interest in using Java so I have never
investigated the issue. But since the java build is part of the install
step in make it never installs the cpp parts either. So I have just
installed the parts manually after they build correctly.

$OSSIEHOME/share/idl/redhawk//*.idl

$OSSIEHOME/include/redhawk//*.h

$OSSIEHOME/lib or lib64/Interfaces.*

I imagine that one could delete the java make step and get make install
to work and do these installs, I just have not bothered.

If you need the java interfaces, then this will of course not work. I
am sorry but I do not know why the java fails. It only fails for one of
the four IDL projects that I have built and used and I am not sure why.
I know that you may need to add lines to:

$OSSIEHOME/lib/python/redhawk/codegen/lang/idl.py

adding additional

idlRepo.adSearchPath(os.path.join(os.environ['OSSIEHOME'],
"share/idl/redhawk/'))

but I believe this is only to allow USING an installed package, but if
you installed the RS package and it is referenced in your SCWIS idl
files then you may need this but even this has not been enough for me
with one package.

On 8/3/2016 12:11 PM, jsrsarma wrote:

Hello Terry

when you have a minute, please take a look

I really appreciate it.

regards

Sivaram

I have created an idl project to install SCWIS interface based on the
idl files.
when I tried to build using the sudo make install
the CPP works fine with no errors
but java step fails,
resulting in not being shown up as installed in
/usr/local/redhawk/core/include/redhawk

Eventhough the RS module is installed , the given below are the new
IDL modules I have ported.

burstio BURSTIO FRONTEND JTRS MIM OE PACKET RS SIMPLEPACKET

the errors -------------- C++ build is fine with no errors
find src/java -name '*.java' > build/java.files
/usr/lib/jvm/java/bin/javac -cp

/usr/local/redhawk/core/lib/CFInterfaces.jar:/usr/local/redhawk/core/lib/BULKIOInterfaces.jar:

-target 1.5 -source 1.5 -d build/java @build/java.files
warning: [options] bootstrap class path not set in conjunction with
-source 1.5
src/java/SCWIS/SC_WFOperations.java:38: error: package RS does not
exist
void initializeWaveform (RS.ChannelID channelID, String
waveformPreset) throws
SCWIS.SC_WFPackage.ProcessingSC_CommandException;
^
src/java/SCWIS/SC_WFPOATie.java:62: error: package RS does not exist
public void initializeWaveform (RS.ChannelID channelID, String
waveformPreset) throws
SCWIS.SC_WFPackage.ProcessingSC_CommandException
^
src/java/SCWIS/_SC_WFStub.java:39: error: package RS does not exist
public void initializeWaveform (RS.ChannelID channelID, String
waveformPreset) throws
SCWIS.SC_WFPackage.ProcessingSC_CommandException
^
src/java/SCWIS/SC_WFPOA.java:65: error: package RS does not exist
RS.ChannelID channelID = RS.ChannelIDHelper.read (in);

SCWIS.idl_______
#include "CF.idl"
#include "RS.idl"
module SCWIS {
CF::Application createWaveform (
in string baseWF_Name
)
void initializeWaveform (
in RS::ChannelID channelID,
in string waveformPreset
)
}

RS.idl_______

#include "CF.idl"
module RS {
struct ComponentInfoRecordType {
string id;
string version;
string name;
string xmlLocation;
CF::FileSystem fileSystem;
};
}

Dr Terry L Anderson
TAndersoft

You are receiving this because you authored the thread.
Reply to this email directly, view it on

GitHubhttps://github.com//issues/12#issuecomment-237321914,

or mute the

threadhttps://github.com/notifications/unsubscribe-auth/AAP25YpNsH29oD93HubA6m9Y7GupUQftks5qcNsNgaJpZM4JMfqf.

You are receiving this because you commented.
Reply to this email directly, view it on GitHub

#12 (comment),

or mute the thread

https://github.com/notifications/unsubscribe-auth/AKsdIv9oQpWrB-ZWM5oB4RsM-pJxXFPlks5qcOf0gaJpZM4JMfqf.

Dr Terry L Anderson
TAndersoft

You are receiving this because you authored the thread.
Reply to this email directly, view it on

GitHubhttps://github.com//issues/12#issuecomment-237357764,
or mute the

threadhttps://github.com/notifications/unsubscribe-auth/AAP25Ul2j2rCXt0Z6pKwnm6J6O7ftVetks5qcPZ3gaJpZM4JMfqf.


You are receiving this because you commented.
Reply to this email directly, view it on GitHub

#12 (comment),
or mute the thread

https://github.com/notifications/unsubscribe-auth/AKsdItlObW6LvDfNJh90YgMPhObA1ut_ks5qcQXLgaJpZM4JMfqf.

Dr Terry L Anderson
TAndersoft


You are receiving this because you authored the thread.
Reply to this email directly, view it on
GitHubhttps://github.com//issues/12#issuecomment-237389663,
or mute the
threadhttps://github.com/notifications/unsubscribe-auth/AAP25eBDkgV9QMLfpr5VV_ivBksvl_ynks5qcRCpgaJpZM4JMfqf.


You are receiving this because you commented.
Reply to this email directly, view it on GitHub
#12 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AKsdIj_jf-KhOdaUg74AJtDA3xswGaJrks5qd1qXgaJpZM4JMfqf.

Dr Terry L Anderson
TAndersoft

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants