Time Nick Message 00:02 MTDiscord It can be through relicensing. 00:02 MTDiscord Simply adding a "The Minetest iOS binary and its code is licensed as X" clause would make it legal 00:03 sfan5 who will track down every contributor and make them agree to relicensing to ... what even? 00:04 MTDiscord The Multicraft devs cannot just change the MT license...every single major MT contributor would have to agree to that first AFAIK 00:05 MTDiscord It can be relicensed to GPL, which the App Store allows 00:05 MTDiscord Or is it the other way around.. 00:06 sfan5 LGPL is more permissive so I don't see how GPL would be allowed but LGPL wouldn't 00:06 sfan5 in any case the legal opinions saying that you can't have LGPL on the App Store are about 10 years old, who knows if that still applies today 00:08 MTDiscord Even if Apple would allow MT there is another problem: You have to pay $100 per year to keep it available there...not so easy when the app has absolutely no way to generate revenue 00:12 MTDiscord Geez its such a grey area 00:12 MTDiscord The issue is that certain versions of [L]GPL have clauses that are incompatible with App Store requirements, but some people say certain versions of the two licenses are compatible 00:13 MTDiscord There are quite a few major apps using GPL3, not that it means the issue is cut and dry 01:12 Wuzzy Given a random but valid texture string with any possible combination of modifiers, is it always legally possible to blindly append another modifier like "^[transformR180"? 01:13 Wuzzy or are the some weird edge cases in which this would not be possible? 11:39 jonadab The issue with Apple's App Store is the clause in the developer terms of service that says it's a violation of their TOS to upload anything that's share-alike licensed. 11:40 jonadab There are a lot of share-alike-licensed things in the app store, because it's not consistently enforced. 11:40 jonadab But the clause is there. 11:41 jonadab Note that, once it's uploaded, users who download/install it are not in violation of anything. 11:41 jonadab Only the person who uploaded it, has violated terms of service. 11:51 jonadab Although, hmm, I can't seem to find that document now (the one that says what you as a developer are allowed to upload to the app store or not). 11:55 jonadab It is vaguely possible that the situation has changed. But the clause was always buried deep in a sea of legalese in a TOS agreement nobody actually read. Further investigation may be warranted. 11:57 jonadab Now I wish I'd taken notes about the exact wording. That would make it easier to confirm whether it's still there or not. 15:43 nerzhul_ sfan5, you are publishing a new ittlichtmt release used by main mt or now it's smooth and use the latest irrlicht mt build ? 15:45 sfan5 I published 1.9.0mt1 15:45 sfan5 and pushed the commit to your PR to make that works 15:45 nerzhul_ perfect ty 20:22 v-rob I'm getting three linker errors on Visual Studio with our Irrlicht fork, using either of https://github.com/minetest/irrlicht/releases x64s. Anyone else had this problem (or even tried VS?) 20:24 sfan5 I was under the impression mingw compiled libraries do not work with VS 20:24 v-rob Oh, those are mingw? Oops 20:25 sfan5 yea 20:26 v-rob The readme says it can be compiled on "Windows via MinGW". Does that mean Visual Studio will not work, or just that it hasn't been done yet? 20:27 sfan5 latter 20:29 v-rob I guess I'll try it then. I've never yet been able to compile Minetest with MinGW 20:30 v-rob I'm surprised I only got three linker error with a MinGW lib file. Either they're very similar, or Visual Studio gave up early 21:41 v-rob How do I get Irrlicht to compile without Direct3D 9? Adding /DNO_IRR_COMPILE_WITH_DIRECT3D_9_ to CMAKE_CXX_FLAGS seems to have no effect 21:52 sfan5 do that in the irrcompileconfig.h 21:52 sfan5 i'm pretty sure it's already disabled though 21:52 v-rob No, it isn't 21:52 v-rob It probably should be though. Very few people use it, and obviously not on Linux 21:53 sfan5 "defined(_IRR_WINDOWS_API_) && (!defined(__GNUC__) || defined(IRR_COMPILE_WITH_DX9_DEV_PACK)" I guess that's why 21:53 sfan5 (it's disabled on mingw by default) 21:53 v-rob That explains it 21:54 sfan5 if you plan to make a PR with msvc build settings I'd just turn that into #if defined(_IRR_WINDOWS_API_) && defined(IRR_COMPILE_WITH_DX9_DEV_PACK) 21:59 v-rob Ugh, now I get link errors for a bunch of things in the C standard library. Why can't compilers ever be easy? 22:21 v-rob Now I'm really annoyed. IrrlichtMt finally compiled, but when I try to compile Minetest with it, I get the exact same three link errors plus two more. 22:21 sfan5 what are those errors? 22:23 v-rob "Unresolved external symbol " where the unmangled symbols are createDevice, createDeviceEx, MATERIAL_MAX_TEXTURES_USED, IdentityMaterial, and IdentityMatrix 22:23 v-rob With the MinGW lib, there were the same except for createDevice(Ex) 22:23 sfan5 that sounds like all of the symbols irrlicht should provide (all the c++ stuff goes through indirection or something..) 22:24 sfan5 I think msvc had some speciality where you had to mark symbols as exported (shouldn't existing code do that?) 22:25 sfan5 compiling gave you a .lib file and you selected that in mt's cmake right? 22:26 v-rob Yes 22:32 v-rob Weirdly, Irrlicht's CMakeLists.txt is building all Windows libs to the Win32-gcc directory with the comment "Good enough" regardless of compiler 22:32 v-rob Although I doubt that's the problem here 22:36 v-rob Oh, Irrlicht's CMake "build shared library" got unchecked somehow. But now the C standard library refuses to link again. *Sigh* 22:37 sfan5 what are the linker errors regarding the standard lib? 22:38 v-rob "Unresolved external symbol " where symbol is things like malloc, fopen, atoi, and a bunch of other C standard library functions. 22:38 v-rob This is IrrlichtMt getting these, not Minetest if that wasn't clear 22:39 sfan5 hm 22:39 sfan5 I strongly suggest comparing the linker/compile flags 22:47 v-rob I don't see anything myself, but if it's any help, this is the full CMake config: https://user-images.githubusercontent.com/31123645/112553023-f9ba5280-8d80-11eb-8361-05563c9c6c56.png 22:48 sfan5 I can't make sense of those two/three letter combos, documentation could help 22:49 v-rob Like this? https://docs.microsoft.com/en-us/cpp/build/reference/compiler-options-listed-by-category?view=msvc-160&viewFallbackFrom=vs-2017 22:49 sfan5 though those look like cmake defaults, not the ones the CMakeLists.txt sets 22:52 v-rob It looks like you might be right there, they don't match 22:53 sfan5 yeah but I mean the ones in the cmakelists are probably wrong, very wrong 22:54 v-rob I see. I suppose I'd better try compiling Minetest with MinGW again since I don't seem any closer with Irrlicht and Visual Studio 22:56 v-rob Minetest's readme is entirely unhelpful, and the wiki is very outdated. Do you know of any newer/better MinGW instructions? 22:56 sfan5 no but I think mingw comes with a package manager these days which should save you from lots of the trouble 22:56 sfan5 and/or you can use the same libs as the buildbot 22:57 v-rob Thanks, I'll look into that