This is the mail archive of the
mailing list for the Cygwin project.
CLASSPATHS, and static inclusion.
- From: Me Myself and I <stargate7thsymbol at live dot co dot uk>
- To: <cygwin at cygwin dot com>
- Date: Wed, 4 Apr 2012 12:32:04 +1030
- Subject: CLASSPATHS, and static inclusion.
I have managed to get a copy of ecj.jar
-I havn't been able to follow the instructions for cygpath very well.
Is there a
sort of statement I can just put in /etc/profile? , that won't leave
any problems for my compiled program (presumably my import statement classes
get put in my final gcj program)?? Could I have an example?
-As an aside, when it comes to classes in external packages in external (non-default) jar files,
does one usually have dynamic linking from the gcj compiled program to the
seperate package jar file (needed at runtime), or static linking where
the seperate jar necessary classes and related are all physically
included inside the gcj compiled program?
If I only want static linking of those seperate jar classes (physical inclusion),
may I get away with a CLASSPATH statement only?
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple