The output location for .o files is completely controlled by your build system by the emcc -o <path> directives. You can pass a emcc -o /my/output/directory/file.o to specify which directory to build to. This is identical and compatible to how gcc and clang work in native builds. Perhaps the build system you are using has this set up to build to the same directory as the source files?
2014-08-08 10:20 GMT+03:00 Sergey Solozhentsev <[email protected] >: > I have big library I want to port using emscripten. > I compile it into .bc file but it also generate .o files in the same > directory as source files. Can I put it into separate directory? > > -- > 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. > -- 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.
