Jamrules #7

  • //
  • guest/
  • perforce_software/
  • p4ruby/
  • main/
  • Jamrules
  • Commits
# Change User Description Committed
#7 14682 Git Fusion Git Fusion branch management

Imported from Git
 ghost-of-change-num: 960958
 ghost-of-sha1: 005052ae424bd69f426f7209e741ca1c8c3253c7
 ghost-precedes-sha1: ad052c71a568ef12165e143a6866ad9ceffbb4a1
 parent-branch: None@960958
 push-state: incomplete
#6 14672 tony Tweak P4Ruby jam rules to be a little cleaner
#5 14635 jmistry p4conf.rb fix for SSL:

Added new configuration option '--ssl=<ssl library path>' to specify the ssl
libraries.  If using '--ssl' with no path then ssl libraries are included, but path
is assumed to be set by the system.

User visible change to be documented in release notes.
#4 14591 noahf Use P4APIDIR.
 Don't run regression tests when building dist.
#3 14567 tony Pull latest changes from p09.2 branch back home to main

Integration-only change
#2 14563 tony Update Jam build environment for the scripting interfaces so
that (a) all builds are full builds - it's too complicated to
bring jam's smarts to these build environments and (b) all the
tests are run as part of the build
#1 14557 tony First pass at making P4Ruby build with Jam.
This picks up the API from
the P4 tree, so you must jam the API first, then it simply uses the
API folder and invokes p4conf.rb and make. Not for inclusion in the
MANIFEST, so it should never go to customers.