On Wednesday 09 February 2005 04:22 am, Daniel Leidert wrote: > Miguel wrote: > > > Next: I found the next cyclic dependency during my work to provide > > > common Debian packages. The point is, that I need jmolApis.jar and > > > jmolIO.jar for compiling the CDK-classes, and then I need the > > > CDK-classes for compiling Jmol(Applet). > > > > Why do we need the CDK classes to compile? > > jmol2cdk.jar and jmolappletcdk.jar contain cdk classes. I'm working on a > situation, where I do not need any precompiled java libs. I know, that > someone is working on vecmath and Acme for Debian. At the moment, I can > substitute all other jars with Debian ones. There are only the above > mentioned libs (and vecamth + Acme) left. So I took a look into them and > found, that they contain cdk classes. So my way is: > > - build jmolApis.jar and jmolIO.jar > - use them to create the cdk jars > - use cdk-*.jar instead of jmol2cdk.jar and jmolappletcdk.jar to compile > Jmol and JmolApplet > > That's the idea behind. If I'm right, there is no need for me to use > jmol2cdk.jar and jmolappletcdk.jar.
Correct. Jmol should compile against the latest CVS. If not, I have to fix the problems. > > Is it because of the CdkModelAdapter? > > Yes. But there are also Jmol.java and JmolEditBus.java, which try to > import cdk-classes (also see > 'find src | xargs grep -n import.*\.cdk\. | less') Miguel, I agree that there need to be interfaces for stuff that Jmol needs. Let's try to identify what interfaces are required. Anyway, it keeps a messy stuff, these circular dependencies, because: 1. in Debian packages are build from one source.tar.gz (or from CVS...) resulting in one or more binary .deb packages. 2. however, CDK requires some compiled Jmol interfaces, and Jmol requires some compiled CDK interfaces (or will...) But, as mentioned in 1., Debian expects to build the whole of the package to be compiled... > > > So I patched build.xml, that I > > > can compile the jmolApis.jar and jmolIO.jar only (without compiling the > > > whole source). Means: I made a apisio.classes files and the targets > > > apis-jar/io-jar depend on their own project-path and classes-directory. > > > > > > Q: Can I add this to the upstream build.xml? It will not affect the > > > upstream. It is only for compile _only_ jmolApis.jar and jmolIO.jar, > > > without compiling the whole Jmol source. > > > > OK > > Thx. > > [sample directory in source distribution] > > > > Q: Can we agree to exclude the sample directory from the source tarball > > > and better distribute the samples in their own tarball? > > > > Agreed! > > I will upload the necessary changes with my next updates to build.xml. Thanx for your excellent work! Egon ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Jmol-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jmol-developers
