-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Finish physical redesign #4997
Finish physical redesign #4997
Conversation
e604953
to
e068be2
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## develop #4997 +/- ##
=======================================
Coverage 71.3% 71.3%
=======================================
Files 796 796
Lines 66987 66987
Branches 10886 10865 -21
=======================================
+ Hits 47765 47791 +26
+ Misses 19222 19196 -26
|
4d2f327
to
e25ebac
Compare
e25ebac
to
b2463c1
Compare
Note, this is moving files from
|
b2463c1
to
b00160d
Compare
@thejohnfreeman thanks for addressing this concern. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I like this a lot.
b00160d
to
d3e2788
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I noticed that the most recent rebase has reverted the change to which I refer here
#4997 (comment)
Is it intentional ?
d3e2788
to
75ac07d
Compare
Thanks @thejohnfreeman , I see that's fixed now. |
75ac07d
to
d40a7c6
Compare
I'm trying to follow the directions for merging an in-process branch with the physical restructure. Everything was going well until I ran The output from
The leftover files was a surprise, and the instructions did not say what to do if that happened, so I'm reporting it here. Additionally, I checked the sort order of Suggestions? Thanks. |
@scottschurr what branch did you try? |
@thejohnfreeman, this is the branch I tried: https://github.com/scottschurr/rippled/tree/blocked-book |
I just merged that branch without a hitch: https://github.com/thejohnfreeman/rippled/tree/blocked-book I'll try to replicate your experience on macOS soon. |
Thanks. And if there are any experiments you would like me to try I'm happy to do so. Best of luck. |
d40a7c6
to
92bd4ca
Compare
The problem is what I expected, the environment. The requirements I found missing on macOS are:
Can you run the script in a Linux environment? Alternatively, if you can get these programs on your |
I don't have a readily available Linux environment, but I can install |
- Remove CMake module "MultiConfig". - Update clang-format configuration, CodeCov configuration, levelization script. - Replace source lists in CMake with globs.
714bee1
to
f27aad0
Compare
- Remove CMake module "MultiConfig". - Update clang-format configuration, CodeCov configuration, levelization script. - Replace source lists in CMake with globs.
f27aad0
to
7cf4611
Compare
* upstream/develop: (32 commits) fixInnerObjTemplate2 amendment (XRPLF#5047) Set version to 2.3.0-b1 Ignore restructuring commits (XRPLF#4997) Recompute loops (XRPLF#4997) Rewrite includes (XRPLF#4997) Rearrange sources (XRPLF#4997) Move CMake directory (XRPLF#4997) Add bin/physical.sh (XRPLF#4997) Prepare to rearrange sources: (XRPLF#4997) Change order of checks in amm_info: (XRPLF#4924) Add the fixEnforceNFTokenTrustline amendment: (XRPLF#4946) Replaces the usage of boost::string_view with std::string_view (XRPLF#4509) docs: explain how to find a clang-format patch generated by CI (XRPLF#4521) XLS-52d: NFTokenMintOffer (XRPLF#4845) chore: remove repeat words (XRPLF#5041) Expose all amendments known by libxrpl (XRPLF#5026) fixReducedOffersV2: prevent offers from blocking order books: (XRPLF#5032) Additional unit tests for testing deletion of trust lines (XRPLF#4886) Fix conan typo: (XRPLF#5044) Add new command line option to make replaying transactions easier: (XRPLF#5027) ...
- Remove CMake module "MultiConfig". - Update clang-format configuration, CodeCov configuration, levelization script. - Replace source lists in CMake with globs.
This is the final and most disruptive phase of the physical redesign. It makes these changes:
cmake/
directory.include/xrpl/
.src/libxrpl/
.src/xrpld/
.ripple
C++ namespace is unchanged.xrpl/
andripple/
subdirectories of the header installation prefix. (ripple/
is a symbolic link toxrpl/
, even on Windows.) They include each other with path prefixxrpl/
, but existing projects can continue to include them with path prefixripple/
and migrate to prefixxrpl/
at their own pace.rippled
andxrpld
. (xrpld
is a symbolic link torippled
, even on Windows.)There is a non-trivial (but, I think, easy) process to merge existing branches-in-progress with this one. I will describe it here. Look at the sequence of commits. Notice the commit with subject "Add bin/physical.sh". Call that the checkpoint commit. There are no file movements before the checkpoint commit. The four commits following the checkpoint commit are generated by running the
bin/physical.sh
script added in the checkpoint commit.When you want to merge, you should:
develop
. Resolve conflicts yourself. Be sure that all of the source files added in your branch (if any) appear in the correct source lists inBuilds/CMake/RippledCore.cmake
, between theBEGIN
/END
marker comments (example) . The restructure script moves only the files in these lists, and stops early if any files are leftover (because they were omitted from the lists). Remember the commit ID of this merge. Call it your marker commit.bin/physical.sh
, passing it your marker commit from the first step:Builds/levelization/results/ordering.txt
. Lines beginning withxrpl.
must appear before lines beginning withxrpld
. Different versions ofsort
have been inconsistent on this matter in my experience. On my machine,sort
putsxrpl.
afterxrpld
, which does not match the output ofsort
in our CI job that checks the file.Then you can
git merge -X ours $upstream
whereupstream
points to the head of this branch. It will automatically resolve conflicts in your branch's favor. Then you cangit diff $upstream
and see your work ported.This PR requires the same finishing steps as #4966:
develop
. The commit sequence that predates the review should be preserved. Fixes made since the review opened should be merged into earlier commits..git-blame-ignore-revs
.