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
Modifications needed for building Kodi 18 on FreeBSD host #12992
Conversation
Those includes are likely just implicit on gnu toolchains. If we can avoid those ifdefs.. |
I'll see how much it's possible to reduce/remove these macros. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thanks, looks good.
As noted by notspiff, reducing the ifdefs as far as possible would be great.
cmake/scripts/common/Platform.cmake
Outdated
if(CORE_SYSTEM_NAME STREQUAL freebsd) | ||
set(CORE_PLATFORM_NAME X11) | ||
endif() | ||
|
||
if(CORE_SYSTEM_NAME STREQUAL linux) |
This comment was marked as spam.
This comment was marked as spam.
Sorry, something went wrong.
@ahtotaat you don't have to close the PR, for updating it. If you force push your changes to your branch the PR will be automatically updated. |
Oki, thanks. I'm doing this for the first time so.. |
no worries, about 95% of new contributors do this :) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please give the commits meaningful commit messages.
Also styling of the includes can be a bit improved. Separate kodi and system headers with an empty line for better readability.
#include <iconv.h> | ||
#elif TARGET_FREEBSD | ||
#include "/usr/include/iconv.h" | ||
#endif |
This comment was marked as spam.
This comment was marked as spam.
Sorry, something went wrong.
This comment was marked as spam.
This comment was marked as spam.
Sorry, something went wrong.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks good to me
Small warning. Looks like @ahtotaat is using the website and is working in master branch. This may cause is issues and commits should be squashed into one or several. |
Sigh, I may as well give up.. It's getting frustrating. |
@ahtotaat any reason to close the PR? |
Reason is fairly simple. I would first have to get the "hang" of the SOP and how this system works, before submitting PR's into fairly big project. Until then I'm pretty much running in circles. I've already had accidental commit where I only wanted to sync between home machine and laptop (I was in hospital at the time) For example, I do not really understand what "This may cause is issues and commits should be squashed into one or several." really means yet or how to achieve that. More trouble than worth and waste of time for everyone included. |
Not a waste of time for sure. If you feel up to it, please re-open the PR and we'll guide you. |
@Rechi. If you would be willing to fix the commit messages, I'd appreciate it. |
@ahtotaat done |
@wsnipex still good to get merged? |
yes, looks good. Thanks for the work and patience @ahtotaat |
I thank you for the patience ;) |
More-or-less minimal changes needed for getting the build finish on FreeBSD machine.
Description
Mostly added necessary macros.
Motivation and Context
Build system failed on FreeBSD right in the beginning.
How Has This Been Tested?
2 installations of FreeBSD (11.1-RELEASE and 11.1-STABLE)
1 installation of Ubuntu 16.04.3 (checked if I introduced some regression by accident)
Screenshots (if appropriate):
https://www.upload.ee/image/7616284/IMG_20171031_231900.jpg
Types of change
Checklist: