1elftosb 2.x read me 2------------------- 3 4Directories 5 6elftosb2 - elftosb 2.x 7sbtool - sbtool 1.x 8keygen - keygen 1.x 9common - source files common between elftosb2, sbtool, and keygen 10winsupport - files needed only by the windows build 11elftosb - old elftosb 1.x, does not use anything from common 12generatekeys - old key generation tool for elftosb 1.x 13decrypt - old decryption tool for elftosb 1.x 14unittests - old unit tests for elftosb 1.x 15test_files - test ELF and Srecord files 16old - contains old makefiles for elftosb 1.x 17 18Development 19 20The preferred way to work on elftosb and related tools is to use Xcode on Mac OS X. The 21elftosb.xcodeproj directory is an Xcode project "file". It has targets for elftosb, 22keygen, sbtool, and an aggregate target that builds all of the above. The main reason 23to use Xcode is that the project is set up so that the flex and bison input files are 24processed automatically and the output files compiled. 25 26The Windows project and Linux makefile are not configured to build the flex or bison 27source files. They simply use the output files copied into the elftosb2 directory. 28You can run flex or bison manually to generate these files if you don't want to use Xcode. 29If you do use the Xcode project and make changes to the .l or .y files, be sure to copy 30the output .cpp files into the elftosb2 directory before you move the changes to either 31Windows or Linux. 32 33Building 34 35On Windows, open the .sln file in Microsoft Visual Studio. The solution contains projects 36for each of the individual projects, including the old elftosb 1.x and related tools. 37 38For Linux, run 'make all' from within the top level elftosb directory. This will build only 39the new elftosb 2.x, sbtool, and keygen. The old makefile to build elftosb 1.x and its 40tools is located in the "old" directory. 41 42On Mac OS X just open the .xcodeproj project and build the "Everything" target. 43 44 45 46