Forum Replies Created
-
AuthorPosts
-
Yeah it’s the gcc version from this site. I think I’ll just bite the bullet and reinstall Windows. This all started after a hard drive failure, even though the particular drive didn’t actually have any compiler/monkey2 related stuff on it, it won’t hurt to re-install as it’s an old installation now and it won’t hurt to have a refresh
Thanks Amon, yeah I’ve done all that but no joy. I’m pretty sure I’d either be getting “cl isn’t recognised as a command line” or “can’t find include file”, but it is running cl and stdout is showing that everything is including ok so that all seems ok. Something odd is up seeing as I can’t compile with either mingw or visual c. Here’s my windows_env file, which is pretty much default plus the version changes:
Lua123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187'Hyper experimental thread builds!'MX2_THREADS=1'Use MX2_USE_MSVC=1 to force use of msvc, or MX2_USE_MSVC=0 to force use of mingw. If MX2_USE_MSVC=1, msvc paths'below are used.''If MX2_USE_MSVC is not set (or blank) mx2cc will attempt to autodetect msvc and msvc paths.'MX2_USE_MSVC=1'Build architecture: x86 or x64, x64 only working with msvc.'MX2_ARCH_WINDOWS=x86'Semi-colon separated list of module root dirs, relative to MX2_HOME or absolute.''mx2cc always adds local modules/ dir to start of list.''MX2_MODULE_DIRS=modules;modules_ext'If you change anything below, you should rebuild all!'***** WINDOWS DESKTOP TARGET - MINGW *****'Note: Requires MinGW compilers+build tools, see: http://monkeycoder.co.nz/monkey2-files.''(Note: TDM GCC not recommended, as it uses SJLJ exceptions which are very slow)'PATH=${MX2_HOME}\devtools\i686-6.2.0-posix-dwarf-rt_v5-rev1\mingw32\bin;${PATH}'Need this to override installed mingw.'GCC_EXEC_PREFIX='Linker optionsMX2_LD_OPTS_WINDOWS=-s -static -m32MX2_LD_OPTS_WINDOWS_DEBUG=MX2_LD_OPTS_WINDOWS_RELEASE='C Compiler options. Note: -D_WIN32_WINNT=0x0601 means headers for Windows 7, ie: Windows 7 is min SDK!MX2_CC_OPTS_WINDOWS=-std=gnu99 -D_WIN32_WINNT=0x0603 -m32MX2_CC_OPTS_WINDOWS_DEBUG=-O2MX2_CC_OPTS_WINDOWS_RELEASE=-O3 -DNDEBUG'C++ Compiler optionsMX2_CPP_OPTS_WINDOWS=-std=c++11 -D_WIN32_WINNT=0x0603 -m32MX2_CPP_OPTS_WINDOWS_DEBUG=-O2MX2_CPP_OPTS_WINDOWS_RELEASE=-O3 -DNDEBUG'***** WINDOWS DESKTOP TARGET - MSVC *****'Note: these paths are only used if legacy MX2_USE_MSVC=1''If MX2_USE_MSVC is not set, mx2cc attempts to autodetect latest version of msvc and latest windows kit.'MX2_MSVC_DIR=${ProgramFiles(x86)}\Microsoft Visual Studio\2017\Community\VCMX2_MSVC_TOOLS_DIR=${MX2_MSVC_DIR}\Tools\MSVC\14.16.27023MX2_WINDOWS_KITS_DIR=${ProgramFiles(x86)}\Windows Kits\10MX2_WINDOWS_KIT=10.0.17763.0MX2_MSVC_PATH_X86=${MX2_MSVC_TOOLS_DIR}\bin\Hostx86\x86MX2_MSVC_INCLUDE_X86=${MX2_MSVC_TOOLS_DIR}\include;MX2_MSVC_INCLUDE_X86=${MX2_MSVC_INCLUDE_X86}${MX2_WINDOWS_KITS_DIR}\Include\${MX2_WINDOWS_KIT}\ucrt;MX2_MSVC_INCLUDE_X86=${MX2_MSVC_INCLUDE_X86}${MX2_WINDOWS_KITS_DIR}\Include\${MX2_WINDOWS_KIT}\shared;MX2_MSVC_INCLUDE_X86=${MX2_MSVC_INCLUDE_X86}${MX2_WINDOWS_KITS_DIR}\Include\${MX2_WINDOWS_KIT}\um;MX2_MSVC_LIB_X86=${MX2_MSVC_TOOLS_DIR}\lib\x86;MX2_MSVC_LIB_X86=${MX2_MSVC_LIB_X86}${MX2_WINDOWS_KITS_DIR}\Lib\${MX2_WINDOWS_KIT}\ucrt\x86;MX2_MSVC_LIB_X86=${MX2_MSVC_LIB_X86}${MX2_WINDOWS_KITS_DIR}\Lib\${MX2_WINDOWS_KIT}\um\x86;MX2_MSVC_PATH_X64=${MX2_MSVC_TOOLS_DIR}\bin\Hostx64\x64MX2_MSVC_INCLUDE_X64=${MX2_MSVC_TOOLS_DIR}\include;MX2_MSVC_INCLUDE_X64=${MX2_MSVC_INCLUDE_X64}${MX2_WINDOWS_KITS_DIR}\Include\${MX2_WINDOWS_KIT}\ucrt;MX2_MSVC_INCLUDE_X64=${MX2_MSVC_INCLUDE_X64}${MX2_WINDOWS_KITS_DIR}\Include\${MX2_WINDOWS_KIT}\um;MX2_MSVC_INCLUDE_X64=${MX2_MSVC_INCLUDE_X64}${MX2_WINDOWS_KITS_DIR}\Include\${MX2_WINDOWS_KIT}\shared;MX2_MSVC_LIB_X64=${MX2_MSVC_TOOLS_DIR}\lib\x64;MX2_MSVC_LIB_X64=${MX2_MSVC_LIB_X64}${MX2_WINDOWS_KITS_DIR}\Lib\${MX2_WINDOWS_KIT}\ucrt\x64;MX2_MSVC_LIB_X64=${MX2_MSVC_LIB_X64}${MX2_WINDOWS_KITS_DIR}\Lib\${MX2_WINDOWS_KIT}\um\x64;'***** MSVC COMMAND LINE OPTIONS *****'Linker optionsMX2_LD_OPTS_MSVC=user32.libMX2_LD_OPTS_MSVC_DEBUG=MX2_LD_OPTS_MSVC_RELEASE='C Compiler optionsMX2_CC_OPTS_MSVC=-EHs -W0 -MT -utf-8 -bigobjMX2_CC_OPTS_MSVC_DEBUG=-O1MX2_CC_OPTS_MSVC_RELEASE=-O2 -DNDEBUG'C++ Compiler optionsMX2_CPP_OPTS_MSVC=-EHs -W0 -MT -utf-8 -bigobjMX2_CPP_OPTS_MSVC_DEBUG=-O1MX2_CPP_OPTS_MSVC_RELEASE=-O2 -DNDEBUG'assembler optsMX2_AS_OPTS_MSVC=-DBOOST_CONTEXT_EXPORT='***** EMSCRIPTEN TARGET *****'This is for the emsdk download available at http://monkeycoder.co.nz/monkey2-files/''If you have a different emscripten installation installed that you want to use, comment this lot out.'EMSDK=${MX2_HOME}\devtools\emsdk-1.37.35_64bitEM_CONFIG=${EMSDK}\.emscriptenBINARYEN_ROOT = ${EMSDK}\clang\e1.37.35_64bit\binaryenJAVA_HOME = ${EMSDK}\java\8.152_64bitEMSCRIPTEN = ${EMSDK}\emscripten\1.37.35PATH=${EMSDK};${PATH}PATH=${EMSDK}\clang\e1.37.35_64bit;${PATH}PATH=${EMSDK}\node\8.9.1_64bit\bin;${PATH}PATH=${EMSDK}\python\2.7.5.3_64bit;${PATH}PATH=${EMSDK}\java\8.152_64bit\bin;${PATH}PATH=${EMSDK}\emscripten\1.37.35;${PATH}'Add mserver_winnt emscripten mini-server/launcher.'MX2_MSERVER="${MX2_HOME}\devtools\mserver-v86c\mserver_winnt.exe"'If you have installed the emsdk download from monkeycoder, you can use this one instead...''MX2_MSERVER="${EMSDK}\mserver-v86c\mserver_winnt.exe"'Linker optionsMX2_LD_OPTS_EMSCRIPTEN=-s FETCH=1 -s USE_SDL=2 -s TOTAL_MEMORY=536870912 -s DISABLE_EXCEPTION_CATCHING=1MX2_LD_OPTS_EMSCRIPTEN_WASM=-s BINARYEN=1MX2_LD_OPTS_EMSCRIPTEN_DEBUG=-O2 -s ASSERTIONS=2MX2_LD_OPTS_EMSCRIPTEN_RELEASE=-O3'C Compiler optionsMX2_CC_OPTS_EMSCRIPTEN=-std=gnu99 -s USE_SDL=2 -s TOTAL_MEMORY=536870912 -s DISABLE_EXCEPTION_CATCHING=1MX2_CC_OPTS_EMSCRIPTEN_DEBUG=-O2MX2_CC_OPTS_EMSCRIPTEN_RELEASE=-O3 -DNDEBUG'C++ Compiler optionsMX2_CPP_OPTS_EMSCRIPTEN=-std=c++11 -Wno-all -s USE_SDL=2 -s TOTAL_MEMORY=536870912 -s DISABLE_EXCEPTION_CATCHING=1MX2_CPP_OPTS_EMSCRIPTEN_DEBUG=-O2MX2_CPP_OPTS_EMSCRIPTEN_RELEASE=-O3 -DNDEBUG'***** ANDROID TARGET *****'Note: Requires Android Studio + Android NDK, see: https://developer.android.com/studio/index.html'This is where *my* ndk-bundle is located - yours is probably somewhere else!''For android builds, you need to either set this correctly or make sure 'ndk-build' is available from the command line via you PATH.''PATH=D:\devtools\Android\sdk\ndk-bundle;${PATH}'Application.mk'MX2_ANDROID_APP_CFLAGS=-std=gnu99 -fno-stack-protectorMX2_ANDROID_APP_CPPFLAGS=-std=c++11 -fno-stack-protector -frtti -fexceptionsMX2_ANDROID_APP_PLATFORM=android-14MX2_ANDROID_APP_ABI=armeabi-v7a x86MX2_ANDROID_APP_STL=c++_static'***** RASPBIAN *****MX2_RASPBIAN_TOOLS=${MX2_HOME}\devtools\SysGCC\Raspberry\bin'Linker optionsMX2_LD_OPTS_RASPBIAN=-s -staticMX2_LD_OPTS_RASPBIAN_DEBUG=MX2_LD_OPTS_RASPBIAN_RELEASE='C Compiler optionsMX2_CC_OPTS_RASPBIAN=-std=gnu99MX2_CC_OPTS_RASPBIAN_DEBUG=-OsMX2_CC_OPTS_RASPBIAN_RELEASE=-O3 -DNDEBUG'C++ Compiler optionsMX2_CPP_OPTS_RASPBIAN=-std=c++11MX2_CPP_OPTS_RASPBIAN_DEBUG=-OsMX2_CPP_OPTS_RASPBIAN_RELEASE=-O3 -DNDEBUGI tried cloning the git repository and downloading mingw (from download page here) and doing a rebuild but the same message.
Also tried installing Visual Studio 2017 but having issues with that as well:
Monkey12345678910111213141516171819202122232425262728293031The system cannot find the path specified.E:\monkey2-git\scripts>echo off***** Rebuilding mx2cc *****Mx2cc version 1.1.09***** Making module 'monkey' (windows release x64 msvc) *****Parsing...Semanting...Translating...Compiling...The system cannot find the path specified.Build error: System command failed:cl -c -EHs -W0 -MT -utf-8 -bigobj -O2 -DNDEBUG -I"E:/monkey2-git/modules/" -I"E:/monkey2-git/modules/monkey/native" -showIncludes -Fo"E:/monkey2-git/modules/monkey/monkey.buildv1.1.09/windows_release_msvc_x64/build/monkey_0monkey.cpp.obj" "E:/monkey2-git/modules/monkey/monkey.buildv1.1.09/windows_release_msvc_x64/src/monkey_monkey.cpp" >tmp/stdout1.txtmonkey_monkey.cppMicrosoft (R) C/C++ Optimizing Compiler Version 19.16.27024.1 for x64Copyright (C) Microsoft Corporation. All rights reserved.***** Fatal mx2cc error *****Internal mx2cc build errorNot entirely sure what the “System cannot find the path specified.” All the version numbers and paths are correct in windows_env, and tmp/stdout doesn’t show any errors. Not sure what to do to fix/diagnose further.
VS is installed in C:\Program Files x86\Microsoft Visual Studio\2017
and Window Kits in C:\Program Files x86\Windows Kits\10
Good idea!
That’s great Mark, thanks.
So if I wanted to save a zip would I compress stuff to a data buffer as above and then save the databuffer to disk, would that work?
zip::stream sounds awesome if you can add that
Thanks for the example, didn’t know about memory:: looks like something I could use in the meantime.
It was really cool in Blitzmax the way you could pass either a string or object to the image loader and it would handle it, so would be a nice feature to have. I’m looking to update TimelineFX to be able to load .eff files (basically zip files) rather then the need to unpack them first.
Is there anyway yet to load an image straight from a zip file without the need to extract it to disk first?
Chipmunk has 2d raycasting, and also my own timelinefx has collisions with a raycasting function, there’s an example in the samples folder. Not sure about mojo3d but it uses bullet which must have raycasting functions built into it?
Thanks, glad you like it
I wrote my own xml parser because there wasn’t one around at the time, but I guess I could look at using tinyxml2 in the next version. In the meantime you might have to use namespaces to specify the module you want to use.
I fixed the Blendmode issue and uploaded a new version for Mark to verify, or you can grab from github: https://github.com/peterigz/timelinefx.monkey2
I think those samples are just tests and not much to do with using the actual particle effects so everything else should be ok.
It was running ok and I *think* I have the latest version of mx2 but will check later tonight and fix if there’s any issues.
Just tried out the demo, looks really good!
This was on Windows, I didn’t try the ide rebuild yet, will do that next time.
Thanks for checking, I think actually it’s because there’s no debug version of the modules, will rebuild again and see if that works
Edit: Yep that worked. There was a module (wpm-game) that wasn’t compiling so the rebuildall script was finishing early and I didn’t notice.
Sorry I only just spotted this thread!
It’s a good question, I can’t remember exactly – this is where I should be making better use of git commit comments
I suspect though that I did it purely to keep things as simple as possible.
-
AuthorPosts