GNOME Bugzilla – Bug 744845
Fix running exectuable in builddir when builddir != srcdir
Last modified: 2015-03-09 10:56:21 UTC
Running sound-juicer from the build directory when builddir !== srcdir is broken as it looks in the builddir directory rather than the srcdir for the uninstalled ui and encoding profile files.
Created attachment 297358 [details] [review] Fix out of tree build Running sound-juicer from the build directory when builddir !== srcdir was broken as it was looking in the wrong place for the uninstalled ui and encoding profile files.
Created attachment 298087 [details] [review] Fix running in builddir when bulilddir != srcdir I've reworded the commit subject line to make it clearer that it is running the executable from the builddir that fails rather than building it. Running sound-juicer from the build directory when builddir !== srcdir was broken as it was looking in the wrong place for the uninstalled ui and encoding profile files.
Review of attachment 298087 [details] [review]: ::: Makefile.am @@ +11,3 @@ -I$(top_srcdir)/libjuicer \ -DGNOMELOCALEDIR=\""$(datadir)/locale"\" \ + -DTOPSRCDIR=\""$(top_srcdir)"\" \ could be $abs_top_srcdir too, not sure which one is best...
(In reply to Christophe Fergeau from comment #3) > Review of attachment 298087 [details] [review] [review]: > > ::: Makefile.am > @@ +11,3 @@ > -I$(top_srcdir)/libjuicer \ > -DGNOMELOCALEDIR=\""$(datadir)/locale"\" \ > + -DTOPSRCDIR=\""$(top_srcdir)"\" \ > > could be $abs_top_srcdir too, not sure which one is best... Yes I wondered about that but was concerned that you could end up with an installed executable using the wrong ui and encoding profile files from $(abs_top_srcdir).
Attachment 298087 [details] pushed as 4d07f24 - Fix running in builddir when bulilddir != srcdir