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
Creating blank image for manipulation #211
Comments
Please try the latest master, I've just commited a couple of fixes. |
Thanks, I will check them out ASAP. A secondary question since I need to try a specific revision instead of just using vcpkg: what am I missing to get static linking working? I can get shared libs working no problem, but when trying with static, it seems to not be compiling in the created .c file from sail-codecs ( My setup is as follows:
If I swap SHARED_LIBS to yes (+ use combine codecs) and remove SAIL_STATIC it does work though, so at least I can test that way for now, but ideally I'd like to statically embed everything. |
You can still use vcpkg, just update
With static libs, SAIL creates an extra library |
The one big thing I'm noticing is missing is that I can't create a SAIL-backed image for manipulation purposes; I can load an image from disk, create a new image with null pixels of WxH of a format, or create an image holding a shallow pointer to an existing block of memory, but I can't create an image and ask SAIL to allocate the required space for me to then work with (a hypothetical
sail::image(width, height, format)
). Currently my only option is to allocate the required space ahead of time, allocate a SAIL image pointing to it, perform operation(s) and then do a deep copy to a newsail::image
so that it now owns the memory.The justification for this is mainly to not need to lug around two different pointers, & that nearly every image library has the option to do this sort of thing (think procedurally generated images or custom conversion routines that aren't currently supported by SAIL, like converting grayscale to a specified indexed palette or something).
The text was updated successfully, but these errors were encountered: