From: Freek D. <sf_...@ma...> - 2010-01-29 02:33:38
|
brett lentz wrote: > The tiles directory is specifically for the images of hex tiles. Let's > create a new path for the logos. Calling it either 'images' or 'logos' > is fine by me. 'images' it is. > The correct location for the jarbundler is in the same lib directories > as the Log4j and Batik libraries. It looks like you did that > correctly. I'm not sure about this. This means that it will end up in the final lib folder of releases as well, even though that is not necessary: jarbundler is only necessary during the build of the mac application, not during it's execution. It would unnecessarily increase the size of the application. I am confused by build.xml (which builds the current jar file). Apparently, the build sequence is as follows: * clean build directories (classes, jar) * create a classes and a build ("rails-$version") folder * copy all(!) files, except .java files from root to classes folder (including log, README, tiles, lib) * compile all .java sources in root, and put the classes in the classes folder. * copy all files, except log, lib from classes to jar folder * copy doc, lib from root to build folder * combine all files in jar folder, and and create the .jar file in the build folder. Two questions on the build: * Why are files copied from root to classes? * Why does the .jar include all files by default? This seems unnecessary to me. For example, the jar contains scripts like tiles/CombineTiles.pl, even though those are not needed during the game play. Two more questions: One adverted consequence about the inclusion of jarbundler was that the sources, which came with jarbundler where also compiled, copied to classes, and finally included in the rails.jar file (in lib/jarbundler-2.1.0/src). I kind of doubt that is intended. Should we fix this by only compiling sources in rails/ or test/ during the build-process? Or by making sure there are no other source files? Last -- what would be the preferred output folder for the mac application? I know choose MacRails-1.1.2. Do you have better suggestions? Regards, Freek |