-
Notifications
You must be signed in to change notification settings - Fork 282
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
Updating documentation on main to respect ctest #2034
Conversation
Codecov Report
@@ Coverage Diff @@
## main #2034 +/- ##
=======================================
Coverage 61.38% 61.38%
=======================================
Files 96 96
Lines 19214 19214
Branches 9852 9852
=======================================
Hits 11794 11794
Misses 5096 5096
Partials 2324 2324 Continue to review full report at Codecov.
|
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.
As always, you took care of keeping the documentation up-to-date and put great attention to the details 👏
It looks great to me 👍
@@ -118,9 +118,9 @@ if( EXIV2_BUILD_SAMPLES ) | |||
WORKING_DIRECTORY ${PROJECT_SOURCE_DIR}/tests | |||
COMMAND cmake -E env EXIV2_BINDIR=${CMAKE_RUNTIME_OUTPUT_DIRECTORY} ${Python3_EXECUTABLE} runner.py --verbose tiff_test | |||
) | |||
add_test(NAME lensTests |
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.
Why remove lensTest, they were running fine?
CMakeLists.txt
Outdated
add_test(NAME versionTest | ||
WORKING_DIRECTORY ${PROJECT_SOURCE_DIR}/tests | ||
COMMAND cmake -E env EXIV2_BINDIR=${CMAKE_RUNTIME_OUTPUT_DIRECTORY} ${Python3_EXECUTABLE} runner.py --verbose lens_tests | ||
COMMAND cmake -E env EXIV2_BINDIR=${CMAKE_RUNTIME_OUTPUT_DIRECTORY} ${Python3_EXECUTABLE} runner.py --verbose bash_tests/version_test.py |
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.
Why is there a need for this, isn't version_test.py run as part of bashTests above already? I see below you wanted to have just the minimal versionTest w/o samples/unit tests (good idea), but then it should be addition, not removal of lensTests, no?
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.
That's a mistake. I'll restore lensTest tomorrow.
I find the version test very useful. When I think "what have we got here", my finger rattle out $ make version_test
. In future it'll be $ ctest -R version
. In DOS, I have to type$ ctest -R version -C Release
. The people at Kitware didn't think out the ctest -C option
very well.
README-CONAN.md
Outdated
@@ -110,7 +110,7 @@ _Profiles for Visual Studio are discussed in detail here: [Visual Studio Notes]( | |||
| _**1**_ | Get conan to fetch dependencies<br><br>The output can be quite<br>long as conan downloads and/or builds<br>zlib, expat, curl and other dependencies.| $ conan install ..<br> --build missing | c:\\..\\build> conan install .. --build missing<br> --profile msvc2019Release64 | | |||
| _**2**_ | Get cmake to generate<br>makefiles or sln/vcxproj | $ cmake .. | c:\\..\\build> cmake .. -G "Visual Studio 16 2019" | |||
| _**3**_ | Build | $ cmake --build . | c:\\..\\build> cmake --build . --config Release<br>You may prefer to open exiv2.sln and build using the IDE. | | |||
| _**4**_ | Optionally Run Test Suite | $ make tests | c:\\..\\build> cmake --build . --config Release --target tests<br/>[README.md](README.md) | | |||
| _**4**_ | Optionally Run Test Suite | $ make test | c:\\..\\build> cmake --build . --config Release --target test<br/>[README.md](README.md) | |
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.
Aren't we removing "make test" everywhere in favor of ctest?
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.
Yes. We are. It's work-in-progress.
$ make tests | ||
$ sudo make install | ||
$ ctest | ||
$ sudo cmake --build . --target install |
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.
Or even shorter/recommended cmake --install .
, but six vs half a dozen really...
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'd prefer to keep the cmake --build . --target install
version because that is consistent with everything else.
I didn't know about cmake --install .
. That's getting more involved with cmake than necessary. It's much the same with conan and ctest, there are many options. I like to keep life simple and give the user the minimum required for success.
README.md
Outdated
... lots of output ... | ||
$ cmake --build . --target test |
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.
ctest
instead?
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 think I fixed that this morning on 0.27-maintenance. That's when I realised "there's still a lot of work to be done here. I'll focus on getting 0.27-maintenance
correct. Then punt to 'main'.". So, then I made the 'main' PR a draft.
We were boozing last night. I'll run tomorrow morning, then I'll have fun fixing everything. It's our son's wedding anniversary today, so they've gone to Bath for the weekend.
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.
Enjoy!
README.md
Outdated
|
||
```bash | ||
> cd <exiv2dir>/build | ||
> cmake --build . --target tests | ||
> cmake --build . --target python_tests | ||
> cmake --build . --target test |
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.
ctest
?
README.md
Outdated
|
||
The name **bash_tests** is historical. They are implemented in python. | ||
| | $ cd \<exiv2dir\>/build | \> cd \<exiv2dir\>/build | | ||
| test | $ ctest | \> cmake --build . --config Release --target test | |
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.
The --config Release
is now redundant everywhere since we made it default.
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 need to carefully consider and document cmake --config option
.
I should not have removed lensTest on 'main'. lensTest on 0.27-maintenance is broken was broken and effectively ran all the tests for a second time. I'll put it back on 'main' tomorrow and investigate adding it to 0.27-maintenance. I've marked both PRs (for 'main' and '0.27-maintence') as "Draft". I'm having a day off (hell, it's Saturday). I'll deal with all your comments tomorrow. My aim is tiny differences between the two branches will (or even no difference at all). @piponazo Thank You for your words of praise and encouragement. I consider these documents to be very important. It's time well spent to ensure they are accurate and comprehensive. I'm very pleased by the effort that @postscript-dev put into the exiv2 man page. |
…and 0.27-maintenance/README.md.
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.
Just a couple of typos Robin
I've fixed the This has been well worth the effort and good team-work. Happy Holidays Everybody. |
Thanks to a4865g for bring up this subject in #2031.