I'm suspecting the problem is in the Windows version of ninja or cmake's ninja generator. Using make from a cygwin bash works for creating the library fails, but than fails later with "command line too long" when trying to build library files from a couple hundred source files.
*(╯°□°）╯︵ ┻━┻* If I happen to find a solution I'll report back :) -Floh. Am Freitag, 20. Januar 2017 12:09:47 UTC+1 schrieb Floh: > > Hi, > > I'm having a build problem with the following setup: > > - compiling on Windows7 (OSX and Linux works fine) > - emscripten incoming > - cmake to generate ninja files (since I didn't get make to work properly > on Windows) > - ninja to build > > The problem happens both in PowerShell and the normal DOS shell when > creating the static library files, it looks like path separators are lost > in llvm-ar, e.g.: > > [122/332] Linking CXX static library code\foundation\libfoundation.a > C:/n3h5/fips-sdks/win/emsdk_portable/clang/fastcomp/build_incoming_vs2013_64/RelWithDebInfo/bin\llvm-ar: > > codefoundationCMakeFilesfoundation.dirappapplication.cc.o: no such file or > directory. > [325/332] Linking CXX static library code\render\librender.a > C:/n3h5/fips-sdks/win/emsdk_portable/clang/fastcomp/build_incoming_vs2013_64/RelWithDebInfo/bin\llvm-ar: > > coderenderCMakeFilesrender.dirapprenderrenderapplication.cc.o: no such file > or directory. > > Note how the path before the "no such file of directory" has no path > separators. > > Has anybody seen this problem on Windows? > > Thanks! > -Floh. > > > > > -- You received this message because you are subscribed to the Google Groups "emscripten-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
