Nicolas. Winbuilder 3.4-2 already includes a fix for this. In
installations where the path is likely to be too long for the build
the following warning is issued at the start of the build process:

-- KiCad-Winbuilder V3.4
CMake Warning at KiCadWinbuilder.cmake:182 (message):
  Your install path maybe too long to be able to successfully build KiCad.
  Try re-installing to a root directory if the build fails!

Best Regards,

Brian.

On 16 July 2014 15:07, Nicolas Matringe <email address hidden> wrote:
> I wrote this small piece of code to check for pathname length:
>
> @echo off
> set workdir=%cd%
> echo.%workdir%>len
> for %%a in (len) do set /a len=%%~za -2
> set l=%len%
> del len
> if %l% gtr 30 echo Pathname is too long
>
> 30 was just a random value to check it worked, I haven't checked what
> the maximum length should be for winbuilder to work ok.
>
> --
> You received this bug notification because you are a bug assignee.
> Matching subscriptions: winbuilder-bugs
> https://bugs.launchpad.net/bugs/1289983
>
> Title:
>   winbuilder3.3 fails on windows 7 about boost
>
> Status in KiCad Windows Builder:
>   Fix Released
>
> Bug description:
>   I have downloaded winbuilder from here, and double clicked make.bat:
>   https://launchpad.net/kicad-winbuilder/trunk/3.3/+download/kicad-winbuilder-3.3.7z
>   -- KiCad-Winbuilder V3.3
>   -- Build type: Release
>   -- Checking for environment problems
>   -- Checking for installed Bazaar
>   -- Checking for installed MinGW compiler
>   -- Using installed MinGW compiler, version: 4.8.1
>   -- Checking for wxPython
>   -- Downloading wxPython
>   -- Decompressing wxPython
>   -- Downloading Latest Library Archive...
>   -- Checking out KiCad Documentation source (BZR head)
>   You have not informed bzr of your Launchpad ID, and you must do this to
>   write to Launchpad or access private data.  See "bzr help launchpad-login".
>   -- Checking for BZIP2Build phase:Apply phase:adding file 30/36
>   -- Downloading BZIP2 Source
>   -- Building BZIP2 Library
>   -- Checking for GLEW
>   -- Downloading
>   You have not informed bzr of your Launchpad ID, and you must do this to
>   write to Launchpad or access private data.  See "bzr help launchpad-login".
>   -- Building GLEW/s / Build phase:Apply phase:adding file 10/17
>   -- GLEW build finished
>   -- Checking for Cairo
>   -- Downloading cairo-dev_1.10.2-2_win32.zip
>   -- Decompressing Cairo
>   -- Checking out KiCad source code (BZR head)
>   You have not informed bzr of your Launchpad ID, and you must do this to
>   write to Launchpad or access private data.  See "bzr help launchpad-login".
>   -- Cleaning PCBNEW Python files to ensure good build...e 50/606
>   -- Using KiCad Options:
>   -- -DKICAD_SCRIPTING=ON
>   -- -DKICAD_SCRIPTING_MODULES=ON
>   -- -DKICAD_SCRIPTING_WXPYTHON=ON
>   -- -DPYTHON_ROOT_DIR=C:/Users/Cedric/Downloads/kicad-winbuilder-3.3/env/python
>   -- -DBUILD_GITHUB_PLUGIN=ON
>   --
>    Configuring KiCad ( Release )
>   -- Building Release version of KiCad revision: 4739
>
>   -- KiCad Release was NOT built successfully! Please view the logs
>   Press any key to continue . . .
>
>   it looks like the problem is with boost:
>   [  1%] creating 'boost scratch repo' specifically for boost to track boost patches
>   [  1%] adding pristine boost files to 'boost scratch repo'
>   CMakeFiles\boost.dir\build.make:150: recipe for target 'C:/Users/Cedric/Downloads/kicad-winbuilder-3.3/src/kicad/.downloads-by-cmake/boost_1_54_0/src/boost-stamp/boost-bzr_add_boost' failed
>   CMakeFiles\Makefile2:62: recipe for target 'CMakeFiles/boost.dir/all' failed
>   Makefile:115: recipe for target 'all' failed
>
>   Please see the attached logs.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/kicad-winbuilder/+bug/1289983/+subscriptions