Open GoogleCodeExporter opened 9 years ago
Have you applied this patch?
https://code.google.com/p/mozc/issues/detail?id=185
Original comment by yukawa@google.com
on 7 May 2013 at 2:24
After using the patch in issue 185, there is another error in "python
build_mozc.py build_tools -c Release"
ninja: build stopped: subcommand failed.
Traceback (most recent call last):
File "build_mozc.py", line 1481, in <module>
main()
File "build_mozc.py", line 1466, in main
BuildToolsMain(cmd_opts, cmd_args, original_directory_name)
File "build_mozc.py", line 1001, in BuildToolsMain
BuildMain(options, [build_tools_target], original_directory_name)
File "build_mozc.py", line 1096, in BuildMain
BuildOnWindows(targets)
File "build_mozc.py", line 1076, in BuildOnWindows
RunOrDie([ninja, '-C', target_dir] + tokens)
File "E:\Project\Archieve\C++\mozc\src\build_tools\util.py", line 97, in RunOr
Die
'==========']))
build_tools.util.RunOrDieError:
==========
ERROR: ninja.exe -C out/Release primitive_tools
==========
I use "python build_mozc.py gyp --msvs_version=2012 --noqt" to generate the VC
project file. I guess this might be the problem.
Original comment by saberconer@gmail.com
on 7 May 2013 at 1:32
Hmm. Not reproducible. It succeeds on my client.
Do you have python.exe in your PATH?
If so, please try
set PATH=c:\work\depot_tools;%PATH%
instead of
set PATH=%PATH%;c:\work\depot_tools
c:\work\depot_tools has local python.exe and our build instruction expects we
use that local python.exe.
Original comment by yukawa@google.com
on 7 May 2013 at 11:53
There is no python.exe in my depot_tools folder.
This is where I got it: https://src.chromium.org/svn/trunk/tools/depot_tools.zip
And I update to the latest version using git.
configure.cmd:
@echo off
set PATH=%CD%\depot_tools;%PATH%;D:\Python27
cd src
python build_mozc.py clean
pause
python build_mozc.py gyp --msvs_version=2012 --noqt
pause
python build_mozc.py build_tools -c Release
pause
I put "depot_tools" "src" "configure.cmd" under the same folder, that's why I
using %CD%.
Original comment by saberconer@gmail.com
on 8 May 2013 at 11:46
Could you try to build Mozc in a clean environment?
I confirmed that we can build Mozc at least on a clean environment. Here is the
steps I tried.
1. Create a VM image with VMWare 9.0.2 and install Windows 7 SP1 En x64 into it.
2. Install Visual Studio 2012
3. Install Visual Studio 2012 Update2
4. Extract https://src.chromium.org/svn/trunk/tools/depot_tools.zip into
c:\work\depot_tools
5. set PATH=%PATH%;c:\work\depot_tools
6. Check out Mozc's source code into c:\work\mozc by following the build
instructions.
7. Apply patch in Issue 185
8. python build_mozc.py gyp --msvs_version=2012 --noqt
9. python build_mozc.py build_tools -c Release
10. python build_mozc.py build -c Release package
-> build succeeds.
NOTE: I didn't need to install Python. depot_tools automatically downloaded it
as a local copy.
I'm not sure what happens in your environment but there should be something in
your environment that prevents you from building Mozc.
Original comment by yukawa@google.com
on 9 May 2013 at 11:39
I enconter the same error as the 1st post. Tried the patch in issue 185 and
followed above procedure step by step, work fine if not using QT lib(using
"--noqt" option). But if with QT lib option("--qtdir=c:\Qt\4.7.4"), I get the
error below.
Could you please help to test if you can replicate this issue? Thanks a lot.
[439/439] STAMP obj\win32\build32\mozc_win32_build32.actions_depends.stamp
INFO: Running: ninja.exe -C out/ReleaseDynamic mozc_win32_build32_dynamic
ninja: Entering directory `out/ReleaseDynamic'
[49/351] ACTION Generating Resource file from mozc_tool.qrc
RCC: Warning: No resources in 'tool/mozc_tool.qrc'.
[298/351] CXX obj\gui\base\gui_base.win_util.obj
FAILED: ninja -t msvc -o obj\gui\base\gui_base.win_util.obj -e environment.x86 -
- cl.exe /nologo /showIncludes /FC @obj\gui\base\gui_base.win_util.obj.rsp /c ..
\..\gui\base\win_util.cc /Foobj\gui\base\gui_base.win_util.obj /Fdobj\gui\gui_ba
se.pdb
c:\program files (x86)\microsoft visual studio 11.0\vc\atlmfc\include\atlwinvera
pi.h(75) : error C2039: 'InitializeCriticalSectionEx' : is not a member of '`glo
bal namespace''
c:\program files (x86)\microsoft visual studio 11.0\vc\atlmfc\include\atlwinvera
pi.h(75) : error C3861: 'InitializeCriticalSectionEx': identifier not found
[298/351] CXX obj\gui\base\gui_base.window_title_modifier.obj
ninja: build stopped: subcommand failed.
Traceback (most recent call last):
File "build_mozc.py", line 1481, in <module>
main()
File "build_mozc.py", line 1469, in main
BuildMain(cmd_opts, cmd_args, original_directory_name)
File "build_mozc.py", line 1096, in BuildMain
BuildOnWindows(targets)
File "build_mozc.py", line 1076, in BuildOnWindows
RunOrDie([ninja, '-C', target_dir] + tokens)
File "c:\work\mozc\src\build_tools\util.py", line 97, in RunOrDie
'==========']))
build_tools.util.RunOrDieError:
==========
ERROR: ninja.exe -C out/ReleaseDynamic mozc_win32_build32_dynamic
==========
Original comment by xiaoshit...@gmail.com
on 31 May 2013 at 12:34
Original issue reported on code.google.com by
saberconer@gmail.com
on 7 May 2013 at 2:14