Re: [certi-dev] Matlab Toolbox

[Christian Stenzel]

Hello Jan, hello Erik,


> May be this include file is only used for the ntohl/htonl function
> (which usually are macro)?
> Those are simple byte reordering functions:
> http://linux.die.net/man/3/ntohl
> they do exist on Windows too:
> http://msdn.microsoft.com/en-us/library/windows/desktop/ms740069%28v=vs.85%29.aspx
> 
> Seems that MinGW expect to have those defined in winsock.h
> https://bugzilla.mozilla.org/show_bug.cgi?id=411055

Erik analysis is correct.
The file rti.cpp  is a mex-wrapper intferace from Matlab to the Cpp-API
of the RTI.

In line 38 arpa/inet.h is included.
The macros ntohl and htonl are used within the function double2net and
net2double.

So a fast fix could be the insertion of that code-fragment:

#if def (_WIN32 || _WIN64) 
  #include <winsock.h>
#elif
  #include <arpa/inet.h>
#endif


> I can help with that :-)

You're very welcome.
You have to check out the current cvs version. 

When you are CERTI member you can checkout the current cvs tree of the
Toolbox with write.
I'm not sure if you know how to get write access to the cvs tree.
Follow these instructions under the headline Project Member CVS Access
via SSH.
http://savannah.nongnu.org/cvs/?group=certi

After that you can checkout the toolbox through
cvs -z3 -d:ext:address@hidden:/sources/certi co -d
MatlabHLA_Tbx applications/MatlabHLA_Toolbox

After that you will find the cvs checkout in the folder MatlabHLA_Tbx.

After that you can change to that folder and do the usual cvs stuff.
For example:
cvs update to update the tree
cvs commit to commit your changes
cvs add file to add new files to the tree
cvs diff -uNR >> ../mychanges.patch (unified, recursive diff adding new
files)

If you are no CERTI member you can checkout anonymously:

cvs -z3 -d:pserver:address@hidden:/sources/certi co
-d MatlabHLA_Tbx applications/MatlabHLA_Toolbox

Then you have no write access. But you can send me patches (probably we
open a special bug tracker on savannah) which I would check and commit.

I opened a bug report for this problem (see 
https://savannah.nongnu.org/bugs/index.php?34524)

There we can discuss the details. So we do not have all discussions on
the devel-mailing list.

Another task is to create a CMake build setup. 
Therefore I will open a new task soon. 
Then I will specify the needed build requirements (e.g. Debug/Release
version and check for appropriate libraries).

The second task will be a 1516 transition.
Hard to say how much time is needed for taht task. 
Obviously we have the current toolbox as template.
In 1516, there are some new methods, methods with different signatures
and new HLA types. That's why we need new conversion method for Matlab
to HLA1516 types and vice versa.
In my opinion the concept of Matlab/HLA bindings is proven through the
current toolbox. So the task is "only a programming task", meaning that
we do not have to develop new concepts but have to map the 1516-API.
Therefore we can introduce a new file rti1516.cpp do the programming
stuff as usual.
The m-file folder could be seperated in a hla13 and a hla1516 part.

My problem here is that I have nearly no time at time. This will change
hopefully in the next year. So if you really need a free 1516-Tbx as
fast as possible you're on your own. I can only support you with some
templates and hints if you need some. If you wait we can do the task
together.

So long and A+,
Christian