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 cc/*py tests to python subdir and introduce c standalone test binary #426

Merged
merged 2 commits into from
Mar 4, 2016

Conversation

drzaeus77
Copy link
Collaborator

Moves the python tests to the python subdir. Adds a libbcc.a target for those statically inclined.

Brenden Blanco added 2 commits March 3, 2016 15:39
They didn't quite make sense where they were. At one point 'cc' meant
compiler, and yes they were testing the compiler. Now lets use the
convention that different tests/ subdirectories test different bindings
(c, python, other).

Signed-off-by: Brenden Blanco <[email protected]>
This creates a new static library target for bcc. Add one trivial c test
case that links against it.

Signed-off-by: Brenden Blanco <[email protected]>
set_target_properties(bcc-shared PROPERTIES VERSION ${REVISION_LAST} SOVERSION 0)
set_target_properties(bcc-shared PROPERTIES OUTPUT_NAME bcc)

add_library(bcc-loader-static libbpf.c perf_reader.c)
Copy link
Member

Choose a reason for hiding this comment

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

why split it into another lib?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

There's a dependency (bpf_map_create) required by both bcc and clang_frontend. This gets resolved at final link-time.

@drzaeus77
Copy link
Collaborator Author

Buildbots failed, that's fixed now.

4ast added a commit that referenced this pull request Mar 4, 2016
Move cc/*py tests to python subdir and introduce c standalone test binary
@4ast 4ast merged commit ee79363 into master Mar 4, 2016
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