The Windows cross-compile build examples are missing the autogen.sh
step. Without that step, configure
doesn’t exist and you get this error:
bash: ./configure: No such file or directory
Using Ubuntu 16.04 64 bit.
The Windows cross-compile build examples are missing the autogen.sh
step. Without that step, configure
doesn’t exist and you get this error:
bash: ./configure: No such file or directory
Using Ubuntu 16.04 64 bit.
But in practice most people following this guide seem to be cloning from git. No one uses the source tarball. It’s mostly developers that follow this guide in the first place. Also IIRC we mention autogen.sh
in all other places (such as build-unix.md).
It could ofc. be added that it is optional.
if/fi
that checks for the configure file or explain the example is for source code packages?
Maybe I can add an if/fi that checks for the configure file or explain the example is for source code packages?
Maybe just add a comment after it # not required when building from tarball
. Adding a fi/if construction sounds like overkill, and anyhow this is based on information only the user can know.
26@@ -27,15 +27,15 @@ To build executables for Windows 32-bit:
27 cd depends
28 make HOST=i686-w64-mingw32 -j4
29 cd ..
30- ./configure --prefix=`pwd`/depends/i686-w64-mingw32
31+ ./autogen.sh && ./configure --prefix=`pwd`/depends/i686-w64-mingw32
Is it okay like this?
0cd ..
1./autogen.sh # not required when building from tarball
2./configure --prefix=`pwd`/depends/i686-w64-mingw32
If you agree, I will make the change and squash into one commit.
AmirAbrams
laanwj
luke-jr
MarcoFalke
Labels
Docs