On Thu, Mar 10, 2016 at 3:41 PM, Hongxu Jia <hongxu....@windriver.com> 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, so submit them all > >> >> +Although there is CMAKE_USE_RELATIVE_PATHS, but upstream >> +explicitly did not support relative path. >> +In git://cmake.org/cmake.git >> +... >> +commit 1335992c8f4e8b96f1a21d5dcc7d65a9fbd84c11 >> +Author: Stephen Kelly <steve...@gmail.com> >> +Date: Mon Jun 1 19:56:46 2015 +0200 >> + >> + Remove CMAKE_USE_RELATIVE_PATHS variable. >> +... >> +The reason is in https://cmake.org/Wiki/CMake_FAQ >> +(Why does CMake use full paths, or can I copy my build tree?) > > > Currently, The upstream explicitly do not support it. > > //Hongxu > >> + >> +But oe-core need the source file path relative while compiling >> +to avoid build path issue. The fix partly refer the above commit, >> +but in order to minimize the influence, it only tweak gcc compiling >> +rule in generated Makefile (With "Building ** object" message). > > > -- _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
