build: add packaging to replace makezip.sh to new cmake setup

[derekbruening]

From derek.br...@gmail.com on March 03, 2009 18:10:49

split from base cmake feature issue #19 we should use cmake/ctest/cpack to create release packages, replacing
makezip.sh

we can remove batch/* and makezip.sh once done

cmake is set up for single-configuration builds so we'll need a
higher-level invocation probably via ctest

we'll use cpack to do that actual packaging so we don't need to rely on
having cygwin or otherwise zip/tar

Original issue: http://code.google.com/p/dynamorio/issues/detail?id=63

[derekbruening]

From derek.br...@gmail.com on March 06, 2009 08:25:52

this is committed in r70 will remove batch/* once do a little more testing to ensure independent of cygwin

• CPack commands in top-level CMakeLists.txt
• still need multiple builds, so added packaging scripts make/package.sh
  and make/package.bat
• moved generated README instructions to regular README file
• moved top-level cmake files into make/
• updates to reflect clients now being named lib.so on Linux
• now including symbols:
  • added pdb files to install rules
  • split debug info from linux binaries to allow symbols w/o 5x larger lib
• spent a long time trying to get CPack to have a separate toplevel dir
  from tarball file name: gave up: it's not so bad having toplevel dir w/
  full caps + version name
• both to simplify the pdb copying, and to plan for issue port libutil/ and tools/DRview.c to 64-bit #28 where we'll
  go ahead and build a 64-bit drdeploy.exe even though we don't technically
  need it, I removed the bin/ dir from the installation tree.
  • drdeploy.exe is in bin32
  • the drdeploy script is in both bin{32,64} with appropriate defaults
• fixed 64-bit /W4 warnings in samples

Status: Fixed