🚀 go-pugleaf

On 3/16/2005 at 5:54:51 PM, David Bolsover wrote:

> Thanks again.. but I'm not sure what you did..
> 
> > You should be able to construct a native executable yourself in
> > JBuilder 2005, using the JBuilder executable from JBuilder X.  In
> > fact, as a simple test, you can just take the native executable you
> > built, and tack the JBuilder X launcher on to the front of it....

Are you talking about how I tacked the JBuilder launcher on to the front
of it?  I am not sure if this is what you were referring to, since you
placed that quote after your comment.

Assuming that is it, I just concatenated the two files.  I actually used
the "cat" command from the CygWin toolkit, but the plain old Windows COPY
command will do the same thing.  I think the syntax is:

    COPY JBuilder.exe + Native.exe NewNative.exe

In the above, JBuilder.exe is the JBuilder executable from the JBuilder X
/bin directory and Native.exe is the native executable that you generated
using JBuilder 2005.  The resulting NewNative.exe should run on Windows ME.

Of course, you will probably want to do this differently in production,
since NewNative.exe will contain an copy of the JBuilder 2005 Java
launcher that is not used.  You should be able to just create a JAR file
and and append it to the JBuilder X launcher.  For example:

    COPY JBuilder.exe + App.jar App.exe

With the above approach, you will also need to place the configuration
information in the ZIP comment of the JAR file.  You can build a native
executable using the normal means and then examine the ZIP comment to see
what is needed.

Another approach is to package your files the same way that JBuilder is
packaged.  Instead of appending the JAR file to the executable, you can
place the JAR file in the same directory as the executable, along with a
.config file.  This would eliminate the need to set the ZIP comment for
the JAR file before you concatenate the file.  It also eliminates the need
to have duplicates of all of your classes if you want to include both
Windows and command line versions of the program.  This technique is
described here:

http://bdn.borland.com/article/0,1410,22496,00.html

It is important to note that if you build an executable using the JBuilder
launcher executable, there may be some licensing implications, even though
that is the same executable used by the native executable builder.  Of
course, I am not a lawyer, nor do I speak for Borland, so you will want to
review the license issues yourself, with whatever legal help you feel is
necessary.  There is an article on the Borland community site about using
the launcher:

http://community.borland.com/article/0,1410,27562,00.html

-- 
Regards,

John McGrath [TeamB]

---------------------------------------------------
Before sending me e-mail, please read:
    http://www.JPMcGrath.net/newsgroups/e-mail.html