| 21 | | |
| 22 | | == Vista users == |
| 23 | | |
| 24 | | If you're on Vista, first of all you need to disable "installer-detection", which causes strange things to happen for binaries called "setup.exe", amongst other things. Go to `Start -> All Programs -> Accessories > Run` and enter `secpol.msc`. Then under `Security Settings -> Local Policies -> Security Options`, disable `UAC: Detect application installations and prompt for elevation`. Then reboot. |
| 25 | | |
| 26 | | When building against MingW, make sure that the paths of MingW's gcc.exe and cc1.exe are in your PATH environment variable. |
| 27 | | Best put them at the front. Otherwise Cygwin's executables might be found rather than MingW's. If you do not |
| 28 | | set the path's correctly, you may get the following error in config.log: |
| 29 | | {{{ |
| 30 | | configure:3321: checking for C compiler default output file name |
| 31 | | configure:3348: c:/MinGW/bin/gcc conftest.c >&5 |
| 32 | | ld: /mingw/lib/crt2.o: No such file: No such file or directory |
| 33 | | configure:3351: $? = 1 |
| 34 | | configure:3389: result: |
| 35 | | configure: failed program was: |
| 36 | | configure:3396: error: C compiler cannot create executables |
| 37 | | See `config.log' for more details. |
| 38 | | }}} |
| 39 | | From within a Cygwin terminal, you can set PATH like: |
| 40 | | {{{ |
| 41 | | export PATH=/cygdrive/c/MingW/bin/:/cygdrive/c/MingW/libexec/gcc/mingw32/3.4.2/:$PATH |
| 42 | | }}} |
| 43 | | If you are unsure whether you have set PATH correctly, try to compile a simple C program |
| 44 | | with MingW's gcc first. |
| 45 | | |
| 46 | | |
