-
Notifications
You must be signed in to change notification settings - Fork 845
CMake: clearer sep. between the library and executable code #3858
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
base: master
Are you sure you want to change the base?
Conversation
fce34ad
to
0032cd0
Compare
list(APPEND SOURCE_FILES "../qt/macoshelper.mm") | ||
endif() | ||
|
||
file(GLOB SOURCES_FOREIGN |
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.
Ideally this will go to separate libraries, but we're not there yet.
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 have seen your comment here, but I think if we merge this as is this get even more complicated and we are just moving files around at some point.
0aea1f8
to
8bdf8f4
Compare
8bdf8f4
to
323f225
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.
libwalletqt
must be a library that only that glues together libwallet with Qt. Everything else should not be part of it. See my other comment.
${Qt5Gui_PRIVATE_INCLUDE_DIRS} | ||
) | ||
|
||
target_link_libraries(${PROJECT} |
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.
This here should only link with wallet_api
and ${QT5_LIBRARIES}
. Everything else seems to be unrelated. Same with the unrelated foreign source files that get added.
One more thing to consider, inside the |
So I'm taking a closer look and it seems that it's all interconnected. Either I go all in and fix it all in one go, creating an unrealistically large PR, or we go step-by-step, leveraging "unlocked features" at each step. What's your choice? |
I don't know how you want to organize things so I can't really say at this point. Maybe you can make an overview? |
I'll get back to you on this one soon. |
Separated the (soon to be) testable library code from the GUI executable code and structured the dependencies better.
The project
monero-wallet-gui
now inherits a lot of settings from the library projectwalletqt
, so they don't have to be repeated in the executable's project files.