Skip to content
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

Refactor the CMake 3rdparty/Vc-related bits #1903

Merged
merged 1 commit into from
May 13, 2024
Merged

Refactor the CMake 3rdparty/Vc-related bits #1903

merged 1 commit into from
May 13, 2024

Conversation

brndnmtthws
Copy link
Owner

@brndnmtthws brndnmtthws commented May 8, 2024

  • Include the 3rdparty/ dir from top-level
  • Set includes/libs at top-level
  • Remove the inner CMake version requirement
  • Fix deprecated use of CMake's exec_program()

@brndnmtthws brndnmtthws requested a review from Caellian May 8, 2024 16:41
@github-actions github-actions bot added 3rdparty suggests changes to 3rd party dependencies build system related to build system (CMake) and/or building process/assumptions labels May 8, 2024
Copy link

netlify bot commented May 8, 2024

Deploy Preview for conkyweb canceled.

Name Link
🔨 Latest commit 08b79c9
🔍 Latest deploy log https://app.netlify.com/sites/conkyweb/deploys/663bbdcc63858d0008a9bcc4

 * Include the 3rdparty/ dir from top-level
 * Set includes/libs at top-level
 * Remove the inner CMake version requirement
 * Fix deprecated use of CMake's exec_program()
Comment on lines -3 to -7
set(conky_libs ${conky_libs} Vc)
set(conky_includes ${conky_includes} "${CMAKE_CURRENT_SOURCE_DIR}/Vc")

set(conky_libs ${conky_libs} PARENT_SCOPE)
set(conky_includes ${conky_includes} PARENT_SCOPE)
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why not keep 3rdparty related build configuration in 3rdparty/CMakeLists.txt?

Copy link
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I dislike this because it feels like the dependency is going in the wrong direction (from lower -> upper scope). The child shouldn't know about the parent (i.e., you should be able to take the code out of 3rdparty/ and move it elsewhere and it should work all the same).

Comment on lines 47 to +50
add_subdirectory(3rdparty)
add_subdirectory(3rdparty/toluapp)
set(conky_libs ${conky_libs} toluapp_lib_static)
set(conky_libs ${conky_libs} Vc)
set(conky_includes ${conky_includes} "${CMAKE_SOURCE_DIR}/3rdparty/Vc")
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

And move toluapp from here there?

It's simpler to have to modify a single file when adding/removing dependencies than doing so in 2 places.
So I'd change one of the following:

  • Put all thirdparty configuration in thirdparty to avoid cluttering main CMake file.
    • Some add_subdirectory in the future might require 10 sets before and huge mark_as_advanced as Eigen did. I personally prefer minimally invasive approach because its a lot less work to update sources that way.
  • Completely remove 3rdparty/CMakeLists.txt
  • Something in-between those two options is to set(vc_includes "${CMAKE_CURRENT_SOURCE_DIR}/Vc" PARENT_SCOPE) in 3rdparty/CMakeLists.txt and then do set(conky_includes ${conky_includes} ${vc_includes}), for both Vc and toluapp.
    • This separates details on where 3rdparty libraries keep their libs and includes from conky configuration.

Copy link
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd like to maintain the hierarchy. I'm okay with removing 3rdparty/CMakeLists.txt entirely, but I prefer keeping the paths within 3rdparty/ isolated such that they don't depend paths higher up the chain.

Copy link
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also this isn't a hill I'm willing to die on, more a matter of preference.

Copy link
Collaborator

@Caellian Caellian May 13, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd like to maintain the hierarchy. I'm okay with removing 3rdparty/CMakeLists.txt entirely, but I prefer keeping the paths within 3rdparty/ isolated such that they don't depend paths higher up the chain.

I get what you mean.

Also this isn't a hill I'm willing to die on, more a matter of preference.

I die on every hill (lack of experience), even when wrong sometimes, so sorry if I'm being too nit-picky.

After looking at the comment again, I noticed how the tone might've come off wrong - the two comments are a single question but I posted them in a thread to reference multiple parts of the code, didn't mean it as "Why this? AND YOU DID THIS?", so I'm sorry if you received it that way, that wasn't my intention. I should've use ...see next... at the end or something like that.

I value your input and opinion, you've got more experience than me and have worked with OSS and this project much longer than I.

@Caellian Caellian merged commit 71d0251 into main May 13, 2024
63 checks passed
@Caellian Caellian deleted the cmake-vc-tweaks branch May 13, 2024 11:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
3rdparty suggests changes to 3rd party dependencies build system related to build system (CMake) and/or building process/assumptions
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants