Change 18917
|
|
|
| ·0 | |
|
|
|
|
|
Liz Lam commented
9 years ago
@thebamaman Sure! And thanks to @matt_attaway for cleaning up the code! |
| ·0 | |
|
|
|
|
|
thebamaman commented
9 years ago
I've asked before, but any chance to get unit tests released alongside the p4 source? I've seen the tests directory referenced in the Jamfiles... |
| ·0 | |
|
|
|
|
|
Matt Attaway commented
9 years ago
They're unfortunately not quite as portable as I might hope; they rely on a number of internal VMs and datasets that have specific customer scenarios. |
| ·0 | |
|
|
|
|
|
+About file resolution +Jeff Anton +Perforce Software +COMPANY CONFIDENTIAL |
| ·0 | |
|
|
|
|
|
+ SetOSXSdk : -mmacosx-version-min=10.5 -fwrapv ; + + LIBRARY_DEPOLYMENT_SDK = sdk10.5 ; + + case DARWIN13* :
Marc Wensauer (on Jamrules, line 871) commented
9 years ago
I had to change this to |
| ·0 | |
|
|
|
|
|
|
| ·0 | |
|
|
|
|
|
Liz Lam commented
9 years ago
@thebamaman No ETA at the moment, but will definitely get that task in the queue. |
| ·0 | |
|
|
|
|
|
thebamaman commented
9 years ago
Not related to p4 (but P4V, and I have no where to comment on that), but I'm curious about slide 22 in this presentation: http://www.slideshare.net/perforce/build-your-own-monster-in-the-perforce-workshop That somewhat implies that P4V source will show up on here at some point? Is that still the case? |
| ·0 | |
|
|
|
|
|
Liz Lam commented
9 years ago
(edited)
@thebamaman Due to some shifting priorities, open sourcing P4V is in a holding pattern. Were there some features or bugs you wanted to see fixed? By the way, if you're interested, we have a Perforce Community Group on Slack. Email p4slack@perforce.com with 'Add me' in the subject heading for an invite. |
| ·0 | |
|
|