This topic contains 2 replies, has 2 voices, and was last updated by 
Mark Sibly
2 years, 4 months ago.
Viewing 3 posts - 1 through 3 (of 3 total)
-
Posts
-
I’m trying to have a play with the latest Monkey 2 release and Pyro 2 and I’m getting failures when trying to build the Pyro 2 demos via Ted2Go for desktop. On first attempt the pacmanish demo builds and runs in debug mode but if I try to rebuild then it fails with the following output:
1234567891011121314151617Mx2cc version 1.1.01***** Building app 'C:/Users/Damian/Documents/Data/Dev/Projects/Monkey2/essentials/demos/pacman-ish/pacman-ish.monkey2' *****Parsing...Semanting...Translating...Compiling...Build error: System command 'g++ -I"C:/Users/Damian/Documents/Data/Dev/Tools/Monkey2-v1.1.01/modules/" -I"C:/Users/Damian/Documents/Data/Dev/Tools/Monkey2-v1.1.01/modules/monkey/native" -I"C:/Users/Damian/Documents/Data/Dev/Projects/Monkey2/essentials/demos/pacman-ish/" -std=c++11 -m32 -I"C:/Users/Damian/Documents/Data/Dev/Tools/Monkey2-v1.1.01/modules/freetype/freetype-2.6.3/include/" -I"C:/Users/Damian/Documents/Data/Dev/Tools/Monkey2-v1.1.01/modules/openal/openal-soft/include/" -I"C:/Users/Damian/Documents/Data/Dev/Tools/Monkey2-v1.1.01/modules/gles20/angle/include/" -I"C:/Users/Damian/Documents/Data/Dev/Tools/Monkey2-v1.1.01/modules/sdl2/SDL/include/" -c -MM "C:/Users/Damian/Documents/Data/Dev/Tools/Monkey2-v1.1.01/modules/pyro-scenegraph/pyro-scenegraph.buildv1.1.01/windows_debug/include/_r.cpp" >"C:/Users/Damian/Documents/Data/Dev/Projects/Monkey2/essentials/demos/pacman-ish/pacman-ish.buildv1.1.01/windows_debug/build/_1_1_1_1_1_1_1_1Tools_2Monkey2_5v1.1.01_2modules_2pyro_5scenegraph_2pyro_5scenegraph.buildv1.1.01_2windows_0debug_2include_2_0r.cpp.deps"' failed.g++ -I"C:/Users/Damian/Documents/Data/Dev/Tools/Monkey2-v1.1.01/modules/" -I"C:/Users/Damian/Documents/Data/Dev/Tools/Monkey2-v1.1.01/modules/monkey/native" -I"C:/Users/Damian/Documents/Data/Dev/Projects/Monkey2/essentials/demos/pacman-ish/" -std=c++11 -m32 -I"C:/Users/Damian/Documents/Data/Dev/Tools/Monkey2-v1.1.01/modules/freetype/freetype-2.6.3/include/" -I"C:/Users/Damian/Documents/Data/Dev/Tools/Monkey2-v1.1.01/modules/openal/openal-soft/include/" -I"C:/Users/Damian/Documents/Data/Dev/Tools/Monkey2-v1.1.01/modules/gles20/angle/include/" -I"C:/Users/Damian/Documents/Data/Dev/Tools/Monkey2-v1.1.01/modules/sdl2/SDL/include/" -c -MM "C:/Users/Damian/Documents/Data/Dev/Tools/Monkey2-v1.1.01/modules/pyro-scenegraph/pyro-scenegraph.buildv1.1.01/windows_debug/include/_r.cpp" >"C:/Users/Damian/Documents/Data/Dev/Projects/Monkey2/essentials/demos/pacman-ish/pacman-ish.buildv1.1.01/windows_debug/build/_1_1_1_1_1_1_1_1Tools_2Monkey2_5v1.1.01_2modules_2pyro_5scenegraph_2pyro_5scenegraph.buildv1.1.01_2windows_0debug_2include_2_0r.cpp.deps"***** Fatal mx2cc error *****Internal mx2cc build errorIf I delete the build directory then it will build successfully (again, just once).
Alternatively, if I try to build in release mode it fails first time with this output:
123456789101112131415161718192021Mx2cc version 1.1.01***** Building app 'C:/Users/Damian/Documents/Data/Dev/Projects/Monkey2/essentials/demos/pacman-ish/pacman-ish.monkey2' *****Parsing...Semanting...Translating...Compiling...Build error: System command 'g++ -I"C:/Users/Damian/Documents/Data/Dev/Tools/Monkey2-v1.1.01/modules/" -I"C:/Users/Damian/Documents/Data/Dev/Tools/Monkey2-v1.1.01/modules/monkey/native" -I"C:/Users/Damian/Documents/Data/Dev/Projects/Monkey2/essentials/demos/pacman-ish/" -std=c++11 -m32 -O3 -DNDEBUG -I"C:/Users/Damian/Documents/Data/Dev/Tools/Monkey2-v1.1.01/modules/freetype/freetype-2.6.3/include/" -I"C:/Users/Damian/Documents/Data/Dev/Tools/Monkey2-v1.1.01/modules/openal/openal-soft/include/" -I"C:/Users/Damian/Documents/Data/Dev/Tools/Monkey2-v1.1.01/modules/gles20/angle/include/" -I"C:/Users/Damian/Documents/Data/Dev/Tools/Monkey2-v1.1.01/modules/sdl2/SDL/include/" -c -o "C:/Users/Damian/Documents/Data/Dev/Projects/Monkey2/essentials/demos/pacman-ish/pacman-ish.buildv1.1.01/windows_release/build/_1_1_1_1_1_1_1_1Tools_2Monkey2_5v1.1.01_2modules_2pyro_5scenegraph_2pyro_5scenegraph.buildv1.1.01_2windows_0release_2include_2_0r.cpp.o" "C:/Users/Damian/Documents/Data/Dev/Tools/Monkey2-v1.1.01/modules/pyro-scenegraph/pyro-scenegraph.buildv1.1.01/windows_release/include/_r.cpp"' failed.g++ -I"C:/Users/Damian/Documents/Data/Dev/Tools/Monkey2-v1.1.01/modules/" -I"C:/Users/Damian/Documents/Data/Dev/Tools/Monkey2-v1.1.01/modules/monkey/native" -I"C:/Users/Damian/Documents/Data/Dev/Projects/Monkey2/essentials/demos/pacman-ish/" -std=c++11 -m32 -O3 -DNDEBUG -I"C:/Users/Damian/Documents/Data/Dev/Tools/Monkey2-v1.1.01/modules/freetype/freetype-2.6.3/include/" -I"C:/Users/Damian/Documents/Data/Dev/Tools/Monkey2-v1.1.01/modules/openal/openal-soft/include/" -I"C:/Users/Damian/Documents/Data/Dev/Tools/Monkey2-v1.1.01/modules/gles20/angle/include/" -I"C:/Users/Damian/Documents/Data/Dev/Tools/Monkey2-v1.1.01/modules/sdl2/SDL/include/" -c -o "C:/Users/Damian/Documents/Data/Dev/Projects/Monkey2/essentials/demos/pacman-ish/pacman-ish.buildv1.1.01/windows_release/build/_1_1_1_1_1_1_1_1Tools_2Monkey2_5v1.1.01_2modules_2pyro_5scenegraph_2pyro_5scenegraph.buildv1.1.01_2windows_0release_2include_2_0r.cpp.o" "C:/Users/Damian/Documents/Data/Dev/Tools/Monkey2-v1.1.01/modules/pyro-scenegraph/pyro-scenegraph.buildv1.1.01/windows_release/include/_r.cpp"Assembler messages:Fatal error: can't create C:/Users/Damian/Documents/Data/Dev/Projects/Monkey2/essentials/demos/pacman-ish/pacman-ish.buildv1.1.01/windows_release/build/_1_1_1_1_1_1_1_1Tools_2Monkey2_5v1.1.01_2modules_2pyro_5scenegraph_2pyro_5scenegraph.buildv1.1.01_2windows_0release_2include_2_0r.cpp.o: No such file or directory***** Fatal mx2cc error *****Internal mx2cc build errorThe file it’s trying to create there has a path length of 261 chars. Windows MAX_PATH is 260 chars. Is there some workaround/setting to adjust the filename munging to avoid this (other than telling me to move the project).
Oops. I should have mentioned that I have checked and both issues do go away if I shorten the path. That’s fine but my directory structure is hardly crazily deep. The build process is the thing generating an extra 180+ characters on the path.
The latest mx2cc up at github should fix some/most/all of the crazy-long tmp file name issues.
Viewing 3 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic.