Michael,<div><br></div><div>Thanks, I see it now. I thought you were referring to the JCIFS Readme.txt</div><div><br></div><div>At the time, I did not know about this extra package. There was no reference in the JCIFS readme indicating anything about the midlc package or what it was used for.</div>
<div><br></div><div>Thanks</div><div><br></div><div>Chris</div><div><br><br><div class="gmail_quote">On Fri, Mar 9, 2012 at 12:14 PM, Michael B Allen <span dir="ltr"><<a href="mailto:ioplex@gmail.com">ioplex@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">On Fri, Mar 9, 2012 at 7:53 AM, Chris Dail <<a href="mailto:chrisdail@gmail.com">chrisdail@gmail.com</a>> wrote:<br>
> Michael,<br>
><br>
> Thanks for the pointers. I will take a look at midlc. I looked at the<br>
> README.txt and there does not seem to be a mention of midlc (search turns up<br>
> empty).<br>
<br>
</div>Hi Chris,<br>
<br>
Are you looking at the README.txt that comes with the midlc package in<br>
the JCIFS download area?<br>
<br>
INSTALLATION<br>
<br>
Midlc must be compiled from source. It is known to compile on Linux and<br>
Windows although the Windows implementation currently does not run the<br>
preprocessor (need to implement preprocw.c). Libmba is required<br>
(<a href="http://www.ioplex.com/~miallen/libmba/" target="_blank">http://www.ioplex.com/~miallen/libmba/</a>). Follow the libmba instructions<br>
for the target platform, modify the first line of the Makefile to point to<br>
the libmba directory, and run 'make'. On Windows run 'nmake -f<br>
Makefile.msvc'.<br>
<br>
RUNNING<br>
<br>
usage: ./midlc [-v|-d] [-s <symtab>] [-t c|java] [-o outfile]<br>
[-Dmacro=defn] <filename><br>
<br>
-v verbose - List partial parse tree<br>
-d debug - List full parse tree and insert symbol comments into stub<br>
-s <symtab> - Specify primative data type symbol table (default is<br>
currently symtabjava.txt)<br>
-t c|java - Specify the code type generated (currently only java<br>
is supported)<br>
-o <outfile> - Specify name of output file. Otherwise outfile is same<br>
name as input pathname but with different extension<br>
(e.g. .java)<br>
-Dmacro=defn - Specify a preprocessor macro. All idl files are first<br>
processed by the preprocessor. Additionally setting the<br>
special macro 'package' will insert a 'package xyz;'<br>
statement at the top of the generated Java stub.<br>
<filename> - The pathname of the input IDL file.<br>
<br>
Beware that validation is totally non-existant. The input IDL MUST be<br>
syntactically perfect. Try running your IDL though MIDL to be certain it is<br>
valid.<br>
<br>
EXAMPLE<br>
<br>
$ ./midlc -v src/HelloWorld.idl<br>
<br>
or<br>
<br>
C:\> midlc -v src\HelloWorld.idl<br>
<br>
This will generate a class file src/HelloWorld.java that can encode and<br>
decode NDR into an arbitrary byte array. Create a driver program like the<br>
Jarapac example and run it.<br>
<div class="im"><br>
><br>
> Chris,<br>
><br>
> Thanks for the link you sent. That information will be very helpful.<br>
<br>
</div>I doubt that.<br>
<br>
Mike<br>
</blockquote></div><br></div>