<!DOCTYPE html>
<html>
<head>
<title></title>
<style type="text/css">p.MsoNormal,p.MsoNoSpacing{margin:0}</style>
</head>
<body><div>On Fri, May 18, 2018, at 09:10, Rémi Denis-Courmont wrote:<br></div>
<blockquote type="cite"><div>Le perjantaina 18. toukokuuta 2018, 9.57.54 EEST Steve Lhomme a écrit :<br></div>
<blockquote><div>LUAC='/c/Users/robux/Documents/Programs/Videolabs/work/contrib/x86_64-<br></div>
<div>w64-mingw32/../bin/x86_64-w64-mingw32-luac.exe'<br></div>
</blockquote><div><br></div>
<div>Actually LUAC is probed using CHECK_TOOL, not PATH_TOOL.<br></div>
<div><br></div>
<blockquote><div>Basically the C/C++ are exceptions rather than the norm.<br></div>
</blockquote><div><br></div>
<div>No, that is the norm, not the exception: CC, CXX, OBJC, BUILDCC, OBJDUMP,<br></div>
<div>OBJCOPY, RANLIB, STRIP, NM, WINDRES, unix2dos, PROTOC, DESKTOP_FILE_VALIDATE,<br></div>
<div>LUAC, LEX, BISON, KDE4_CONFIG are all using the simple form.<br></div>
</blockquote><div><br></div>
<blockquote type="cite"><div>And most AC_PATH_PROG calls are cargo-culted/copy-pasted without consideration<br></div>
<div>whether it was actually needed.<br></div>
<div><br></div>
<blockquote><div>Everything else<br></div>
<div>in the environment when you run configure is saved in variables reused<br></div>
<div>when you call make. Changing the environment when you call make has<br></div>
<div>little to no effect at all. I don't see why the PATH should be any<br></div>
<div>different.<br></div>
<div>it's very inconvenient to have to remember to reset your PATH whenever<br></div>
<div>you switch to another build directory and prone to a lot of time wasting<br></div>
<div>errors.<br></div>
</blockquote><div><br></div>
<div>No. It is not using the same environment that is prone to errors.<br></div>
</blockquote><div><br></div>
<div>Exactly, so forcing the user to change the environment for each folder one compiles in is prone to errors.<br></div>
<div><br></div>
<div>You can't say that you have to have the same environment between configure and make (which is correct) and tell the user to often mess with his/her environment.<br></div>
<div><br></div>
<div>All the variables you mention are things needed to compile for a particular target. But the things we build in extra/tools may differ between VLC versions, even if the target is the same. That's especially true for compilers.<br></div>
<div><br></div>
<blockquote type="cite"><div><br></div>
<div>configure even checks to prevent the most obvious errors.<br></div>
<div><br></div>
<div>--<br></div>
<div>Реми Дёни-Курмон<br></div>
<div><a href="http://www.remlab.net/">http://www.remlab.net/</a><br></div>
<div><br></div>
<div><br></div>
<div><br></div>
<div><u>_______________________________________________</u><br></div>
<div>vlc-devel mailing list<br></div>
<div>To unsubscribe or modify your subscription options:<br></div>
<div><a href="https://mailman.videolan.org/listinfo/vlc-devel">https://mailman.videolan.org/listinfo/vlc-devel</a><br></div>
</blockquote><div><br></div>
</body>
</html>