On Thu, Sep 21, 2017 at 10:03 AM, Nicolas George <geo...@nsup.org> wrote: > Le jour de la Récompense, an CCXXV, Jacob Trimble a écrit : >> But without this, you can't have a compiler path that has a space in >> it. Plus, AFAIK, there is no way to escape the space through a bash >> variable. Meaning there is no way for $cc to have an escaped space in >> it. Is this just something that won't be supported? > > Do you know any build system that does? > > Regards, > > -- > Nicolas George
Now that I think about it more, I guess that is the correct behavior. I guess I am just used to working in non-configure-based build systems that separate out the compiler path from the flags/wrappers. It would be nice to be able to specify it as --cc='a path/gcc' --cc_wrapper=ccache --cflags=-m32, but I see that changing it would break everything and that is not the ./configure style. NVM _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
