-
Notifications
You must be signed in to change notification settings - Fork 87
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
Do not include source files and/or name include files properly #32
Comments
This source file is a special inclusion which works as .c and header file as well depending on purpose...it is included by design and is intentional. |
@drprajap can the relative directory #includes be fixed as well? If your cmake is already including -I 'pkg-config -cflags igdgmm', then all includes should relate on that absolute directory and includes should look like: #include "Utility/CpuSwizzleBit/CPUswizzleBit.h" While you're at it, maybe it is time to fix #5 It may seem like a lot of work, but a clean API including a public one will benefit everyone using this library. Please seriously consider taking the hit now and not later. c files should not be included. If that's your design, please review your design. |
Yes, relative directory path can be fixed and I was checking the builds with that change. when I use I am looking into the issue right now and will update on that. Regarding other includes, we can fix all other hard coded paths with this change. But reorganizing headers requires bigger effort, which cannot be taken at this point, because team is working on other higher priority tasks. Once all the clients transition is successful with DLL, We will take the reorganization with priority along with API cleanup. That is next task in our plate. Regarding c file inclusion, as per design, CpuSwizzleBlt is standalone feature and we wanted to keep it independent so that it can be used in other projects/tools without any dependency. If we divide in 2 headers, we add additional dependency for other projects and it easily gets polluted with other non-relevant stuff. This file rarely changes so we do not want to consider change to the design. |
Please fix this asap... media-driver won't compile when using gmmlib from pkg-config settings.
Clearly, I see
|
@uartie: I am using gmmlib from pkg-config, but I don't see this issue. I am not CentOS 7.5. This issue looks to be compiler/OS specific. Maybe you can provide a PR fix for that since you can try it? |
@dvrogozh please make sure you don't have a stale installation of gmmlib (i.e. remove your old |
I wouldn't suspect install would be compiler/os specific other than the base install prefix |
My apologies, turns out I had a stale install of gmmlib, doh (foot in mouth)! Error is gone for me now. |
Fixes: intel#32 Signed-off-by: drprajap <[email protected]>
With 18.3 tag checked out , I am getting below error:
Looks like it is related issue. |
@nehudesi : you build error don't seem to be related with gmmlib at all. Instead this seem to be related with mismatch libva and media-driver. Please, make sure that you checked out the following tags, build and install dependencies in the following order:
|
Appreciate your reply @dvrogozh ! I will work on that and let you know! |
gmmlib/Source/GmmLib/inc/External/Common/GmmCommonExt.h
Line 63 in 3bbe741
Please, do not include source files and/or name include files properly. Other places may exist.
The text was updated successfully, but these errors were encountered: