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

Move core/hooking to hooking/ #39

Closed
wants to merge 1 commit into from
Closed

Move core/hooking to hooking/ #39

wants to merge 1 commit into from

Conversation

krf
Copy link
Contributor

@krf krf commented Apr 11, 2013

hooking/ builds gammaray_probe which actually uses libgammaray_core
from core/, so it doesn't make sense to keep it in a subdirectory

hooking/ builds gammaray_probe which actually *uses* libgammaray_core
from core/, so it doesn't make sense to keep it in a subdirectory
@krf
Copy link
Contributor Author

krf commented Apr 11, 2013

Note: This should fix the build on Windows.

@vkrause
Copy link
Contributor

vkrause commented Apr 11, 2013

Makes sense, thanks! Feel free to merge after removing the remaining reference to hooking in core/CMakeLists.txt.

Not sure it entirely fixes the Windows build though, we need to make ui/ (partially) a shared lib for that as well, I've some steps locally for that already, I'll try to complete it later today.

@krf
Copy link
Contributor Author

krf commented Apr 11, 2013

Merged:

commit ed7e1d6
Author: Kevin Funk kevin.funk@kdab.com
Date: Thu Apr 11 17:42:27 2013 +0200

Move core/hooking to hooking/

hooking/ builds gammaray_probe which actually *uses* libgammaray_core
from core/, so it doesn't make sense to keep it in a subdirectory

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants