On Thu, Mar 10, 2016 at 3:41 PM, Hongxu Jia wrote:
> On 03/10/2016 04:08 PM, Khem Raj wrote:
>
> We should submit these kind of changes upstream first and get an opinion
> before forking like this
>
>
> OK, I will have a try.
IMO this could be an improvement in all packages that you have
modified
On 03/10/2016 04:08 PM, Khem Raj wrote:
We should submit these kind of changes upstream first and get an
opinion before forking like this
OK, I will have a try.
+Although there is CMAKE_USE_RELATIVE_PATHS, but upstream
+explicitly did not support relative path.
+In git://cmak
We should submit these kind of changes upstream first and get an opinion
before forking like this
On Mar 10, 2016 2:25 PM, "Hongxu Jia" wrote:
> While '__FILE__' is used in C/C++ source file, we need to
> compile with relative path to avoid build path issue.
>
> If a recipe(such as waffle) inheri
While '__FILE__' is used in C/C++ source file, we need to
compile with relative path to avoid build path issue.
If a recipe(such as waffle) inherit cmake, it invoke native
cmake to generate Makefile:
Without the fix:
vim ./build.make
|cd /Build/tmp/work/core2-64-poky-linux/waffle/1.5.2-r0/
bui
