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.

Sign up for GitHub

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

Jump to bottom

Portability #175

Open
fvalasiad opened this issue Mar 24, 2023 · 0 comments
Open

Portability #175

fvalasiad opened this issue Mar 24, 2023 · 0 comments
Labels
portability Extend support for non-typical use case

Comments

@fvalasiad
Copy link
Collaborator

Seeing as our future plans involve porting build-recorder to other systems, it would be great to re-arrange our code structure now before the code gets significantly more complicated from the performance improvements we have planned.

What I mean to say is that for the most part, all the platform-specific code is located in src/tracer.c, but it is mixed with platform-independent code, should we perhaps separate the two and abstract away some code in order to make the platform-independent code reusable?
@fvalasiad fvalasiad added the portability Extend support for non-typical use case label Mar 24, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
portability Extend support for non-typical use case
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@fvalasiad