-
-
Notifications
You must be signed in to change notification settings - Fork 55
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
Rethink how we integrate resources in binaries. #31
Comments
This comment has been minimized.
This comment has been minimized.
This issue has been automatically marked as stale because it has not had recent activity. It will be now be reviewed manually. Thank you for your contributions. |
@mgautierfr What would be a better approach? |
This issue has been automatically marked as stale because it has not had recent activity. It will be now be reviewed manually. Thank you for your contributions. |
Why not just using a zip blob? Would be easy to read in c++ and easy to build for anybody whatever the platform. We could then just allow to load an external ZIP fs path tomcustomize things. |
At that time, I was thinking about using a zim archive. Now I would use a jubako based container. |
We won't use anything overkill. Package should better be done via tools people are familiar with. Why is a simple tar or zip not good enough? |
We have currently a small solution to embedded resource file in binaries.
The resource file is just store in a C array and the code just read it and interpret it as a file content.
This work well but it could be improved :
This is somehow a pity as we are a project who embedded different files in a read efficient archive, handling file hierarchy and so. We can probably use our own code base to store and read those resource files :)
The text was updated successfully, but these errors were encountered: