Re: Updating ACE[] using jcifs

Michael,

Thanks, I see it now. I thought you were referring to the JCIFS Readme.txt

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.

Thanks

Chris


On Fri, Mar 9, 2012 at 12:14 PM, Michael B Allen <[email protected]> wrote:

> On Fri, Mar 9, 2012 at 7:53 AM, Chris Dail <[email protected]> wrote:
> > Michael,
> >
> > Thanks for the pointers. I will take a look at midlc. I looked at the
> > README.txt and there does not seem to be a mention of midlc (search
> turns up
> > empty).
>
> Hi Chris,
>
> Are you looking at the README.txt that comes with the midlc package in
> the JCIFS download area?
>
> INSTALLATION
>
> Midlc  must  be  compiled  from  source. It is known to compile on Linux
> and
> Windows  although  the  Windows  implementation  currently does not run the
> preprocessor   (need   to   implement   preprocw.c).   Libmba  is  required
> (http://www.ioplex.com/~miallen/libmba/).  Follow  the  libmba
> instructions
> for  the target platform, modify the first line of the Makefile to point to
> the   libmba   directory,   and  run  'make'.  On  Windows  run  'nmake  -f
> Makefile.msvc'.
>
> RUNNING
>
> usage: ./midlc [-v|-d] [-s <symtab>] [-t c|java] [-o outfile]
> [-Dmacro=defn] <filename>
>
> -v verbose   - List partial parse tree
> -d debug     - List full parse tree and insert symbol comments into stub
> -s <symtab>  - Specify primative data type symbol table (default is
>               currently symtabjava.txt)
> -t c|java    - Specify the code type generated (currently only java
>               is supported)
> -o <outfile> - Specify name of output file. Otherwise outfile is same
>               name as input pathname but with different extension
>               (e.g. .java)
> -Dmacro=defn - Specify a preprocessor macro. All idl files are first
>               processed by the preprocessor. Additionally setting the
>               special macro 'package' will insert a 'package xyz;'
>               statement at the top of the generated Java stub.
> <filename>   - The pathname of the input IDL file.
>
> Beware  that  validation  is  totally  non-existant.  The input IDL MUST be
> syntactically perfect. Try running your IDL though MIDL to be certain it is
> valid.
>
> EXAMPLE
>
>  $ ./midlc -v src/HelloWorld.idl
>
> or
>
>  C:\> midlc -v src\HelloWorld.idl
>
> This  will  generate  a  class file src/HelloWorld.java that can encode and
> decode  NDR  into an arbitrary byte array. Create a driver program like the
> Jarapac example and run it.
>
> >
> > Chris,
> >
> > Thanks for the link you sent. That information will be very helpful.
>
> I doubt that.
>
> Mike
>