On Tue, Oct 18, 2016 at 1:16 PM, Pavel Raiskup <praiskup@xxxxxxxxxx> wrote: > On Tuesday, October 18, 2016 1:10:35 PM CEST Igor Gnatenko wrote: >> > Similarly here, if there was %vpath_builddir, %cmake could have been >> > hacked to support that. >> >> Here comes question, where %vpath_srcdir and %vpath_builddir should be >> defined? I would prefer to see it somewhere in RPM, so other distros >> can use it as well. But I can agree on redhat-rpm-macro or any other >> packages. > > I was about to believe that by default we could have those undefined, so we'll > be sure that we'll clearly see that we don't chagne regular > package builds. ... only those who explicitly opt-in this will be affected. For meson, gyp and some other buildsystems there are no opt-in neither opt-out. It just doesn't work other way, only VPATH build. So my idea was to define those somewhere in RPM and meson/gyp/etc. will use it, others (like cmake) can use it in opt-in model. For CMake I don't think we can/will do anything related to this right now. In the future we can define %cmake_vpath. > > Thanks, Pavel > -- -Igor Gnatenko _______________________________________________ packaging mailing list -- packaging@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to packaging-leave@xxxxxxxxxxxxxxxxxxxxxxx
