eellak / build-recorder

GNU Lesser General Public License v2.1
25 stars 8 forks source link

Portability #175

Open fvalasiad opened 1 year ago

fvalasiad commented 1 year ago

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?