No, it's not, not weirder than the copyright law itself. The program has one license, and the game container format has another.Lopy {l Wrote}:The licensing seems weird.
Yes.Lopy {l Wrote}:You say that TirNanoG is under GPL3-or-later,
The game format, which is a container file format, licensed like that, not the engine.Lopy {l Wrote}:but that games created with it are under CC-BY-NC-SA or some proprietary license.
Wrong about that. The license of the program has nothing to do with the license of the output, read this. Likewise for the player application, its license has nothing to do with the license of the input.Lopy {l Wrote}:How are you restricting the license of games made with your engine? It cannot be from the way you allow the use of the engine, since it it released under GPL.
No, nothing comes from the "engine files" (whatever that supposed to mean). The editor stores no GPL licensed parts in the output; the distributed game files contain no GPL'd code; and the player application must be installed independently and separately to the game files.Lopy {l Wrote}:Nor can it be by adding CC-BY-NC-SA covered material in the savefile, since those would come from the engine files
The engine isn't licensed under NC, and it does not make it non-free. As a matter of fact, that's what makes the file format TRULY free, like free as in free beer too. You want a different license for your game or do you want to use proprietary licensed assets? You can, that's why the game container format is dual licensed.Lopy {l Wrote}:I consider that the NC requirement is a bad idea that makes the engine non-free
Yes, licensing isn't up to debate, because that's carefully chosen to fulfill all copyright law requirements, to allow creating free games from free assets by default, but also allow non-free commercial games too under some circumstances. Simply put: if you want to make money with my intellectual property, you can, but you must ask my permission to do so first. Blame the copyright law for this restriction.Lopy {l Wrote}:but you probably made your mind about that already.
Thanks! Be aware, it isn't finished yet!mdtrooper {l Wrote}:It seems awesome.
Hah, you've run into a dependency hell for good! This is exactly why autoconf and cmake and all the other tools suck big time! You actually have everything for the compilation, "configure" returned no errors, except the tool that supposed to generate the Makefile is actually newer, and should be backward compatible, but it's not, god knows why... People should just learn how to write Makefiles, and the world would be a much better place imho!mdtrooper {l Wrote}:I was trying to compile but I have a problem with the versions of aclocal: https://gitlab.com/bztsrc/tirnanog-editor/-/issues/1
It's not a matter of your interest. You have to use the libraries in the source tree, because not all platform provides the required shared libraries, and even if they do provide them, they often provide out-dated versions with incompatible API. Not to mention that the included libraries are heavily stripped down, configured with only the minimal feature set that TirNanoG actually needs and nothing else.dulsi {l Wrote}:I'm not interested in building all the dependencies
Not surprising, it was never intended to work with system libraries, except for SDL. (For that, use "USE_DYNSDL=1 make all")dulsi {l Wrote}:It fails to compile.
Ehm, yes, and? I wrote the code, so yeah, I'm well aware of that. What are you trying to say with this? I've already told you linking with system libraries won't work, instead use the source Luke! :-)dulsi {l Wrote}:You are using some new functions in SDL2_mixer which are not in 2.0.4.
bzt {l Wrote}:I don't really understand the point of your post, could you please elaborate? You're saying you haven't tried it as it's intended to work, and (obviously) you've failed to compile it in a way which was never supposed to work. So, I don't get it. What's your point?
bzt {l Wrote}:It's not a matter of your interest. You have to use the libraries in the source tree, because not all platform provides the required shared libraries, and even if they do provide them, they often provide out-dated versions with incompatible API. Not to mention that the included libraries are heavily stripped down, configured with only the minimal feature set that TirNanoG actually needs and nothing else.
The resulting portable executable is ca. 7 Mbytes in size, no more (no installation required). This wouldn't be possible if it were depending on an armada of DLL / .so files.
Maybe in the future when distros will be up to the task. Won't work for now, sorry that I haven't made that more obvious in the doc.dulsi {l Wrote}:You included instructions to use system libraries. If you don't want people to try that I would recommend not including in the documentation.
You said it yourself that you don't have the latest version as a system library. It won't work if your system libraries provide incompatible API (which is sadly the case with SDL_mixer) :-(dulsi {l Wrote}:That's not the case. Fedora is generally very good at including up to date libraries.
That's the thing, you don't have up-to-date system libraries. (Just for the records, I use a rolling-release distro and it doesn't have it either.) Besides, that 7 Mbytes already includes ALL the required libraries (except libc).dulsi {l Wrote}:A 7 Mbytes executable is great for someone looking for minimum disk usage but I already have the libraries. Having it use up to date common libraries is more valuable to me.
bzt {l Wrote}:Hi All,
I'd like to ask for a little help, I would like to know if anybody else has issues with compiling libtheora (which is included in the source tree).
I've tried with 3 different versions of automake and on 2 distros, yet I wasn't able to reproduce this "syntax error in configure" issue @mdtrooper is having. Maybe with more feedback I would be able to provide a workaround.
Cheers,
bzt
(...)
libtool: link: ar cru build/.libs/libSDL2_mixer.a build/load_aiff.o build/load_voc.o build/mp3utils.o build/music_cmd.o build/music_flac.o build/music_fluidsynth.o build/music_mad.o build/music_mikmod.o build/music_modplug.o build/music_mpg123.o build/music_nativemidi.o build/music_ogg.o build/music_opus.o build/music_timidity.o build/music_wav.o build/music_xmp.o build/effect_position.o build/effect_stereoreverse.o build/effects_internal.o build/mixer.o build/music.o build/utils.o
libtool: link: ranlib build/.libs/libSDL2_mixer.a
libtool: link: ( cd "build/.libs" && rm -f "libSDL2_mixer.la" && ln -s "../libSDL2_mixer.la" "libSDL2_mixer.la" )
checking build system type... x86_64-pc-linux-gnu
checking host system type... x86_64-pc-linux-gnu
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a race-free mkdir -p... /bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking whether to enable maintainer-specific portions of Makefiles... yes
checking whether make supports nested variables... (cached) yes
checking whether make supports the include directive... yes (GNU style)
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether the compiler supports GNU C... yes
checking whether gcc accepts -g... yes
checking for gcc option to enable C11 features... none needed
checking whether gcc understands -c and -o together... yes
checking dependency style of gcc... gcc3
checking dependency style of gcc... gcc3
checking for gcc... (cached) gcc
checking whether the compiler supports GNU C... (cached) yes
checking whether gcc accepts -g... (cached) yes
checking for gcc option to enable C11 features... (cached) none needed
checking whether gcc understands -c and -o together... (cached) yes
checking dependency style of gcc... (cached) gcc3
checking how to run the C preprocessor... gcc -E
checking how to print strings... printf
checking for a sed that does not truncate output... /bin/sed
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for fgrep... /bin/grep -F
checking for ld used by gcc... /usr/x86_64-pc-linux-gnu/bin/ld
checking if the linker (/usr/x86_64-pc-linux-gnu/bin/ld) is GNU ld... yes
checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
checking the name lister (/usr/bin/nm -B) interface... BSD nm
checking whether ln -s works... yes
checking the maximum length of command line arguments... 1572864
checking how to convert x86_64-pc-linux-gnu file names to x86_64-pc-linux-gnu format... func_convert_file_noop
checking how to convert x86_64-pc-linux-gnu file names to toolchain format... func_convert_file_noop
checking for /usr/x86_64-pc-linux-gnu/bin/ld option to reload object files... -r
checking for objdump... objdump
checking how to recognize dependent libraries... pass_all
checking for dlltool... dlltool
checking how to associate runtime and link libraries... printf %s\n
checking for ar... ar
checking for archiver @FILE support... @
checking for strip... strip
checking for ranlib... ranlib
checking command to parse /usr/bin/nm -B output from gcc object... ok
checking for sysroot... no
checking for a working dd... /bin/dd
checking how to truncate binary pipes... /bin/dd bs=4096 count=1
checking for mt... no
checking if : is a manifest tool... no
checking for stdio.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for strings.h... yes
checking for sys/stat.h... yes
checking for sys/types.h... yes
checking for unistd.h... yes
checking for dlfcn.h... yes
checking for objdir... .libs
checking if gcc supports -fno-rtti -fno-exceptions... no
checking for gcc option to produce PIC... -fPIC -DPIC
checking if gcc PIC flag -fPIC -DPIC works... yes
checking if gcc static flag -static works... yes
checking if gcc supports -c -o file.o... yes
checking if gcc supports -c -o file.o... (cached) yes
checking whether the gcc linker (/usr/x86_64-pc-linux-gnu/bin/ld -m elf_x86_64) supports shared libraries... yes
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... no
checking whether to build static libraries... yes
configure: WARNING: *** doxygen not found, API documentation will not be built
configure: WARNING: *** Format Specification will not built.
checking for ld used by gcc... (cached) /usr/x86_64-pc-linux-gnu/bin/ld
checking if the linker (/usr/x86_64-pc-linux-gnu/bin/ld) is GNU ld... (cached) yes
checking how to control symbol export... --version-script
checking for pkg-config... yes
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for OGG... yes
checking for VORBIS... yes
checking for SDL... yes
checking for sys/soundcard.h... yes
checking for PNG... yes
checking for TIFFReadRGBAImage in -ltiff... yes
checking for tiffio.h... yes
./configure: line 16318: syntax error near unexpected token `else'
./configure: line 16318: ` else'
make: *** [Makefile:163: libtheora/lib/.libs/libtheora.a] Erro 2
make all
USE_DYNLIBS=1 make all
USE_DYNSDL=1 make all
Nope, it's the same "syntax error in configure script" problem after the TIFF check. Frankly I have no idea what to do with it. BTW I've uploaded a version of configure in which I've commented out the libtiff check entirely (there's no "--disable-tiff" option arghhh.) You seem to use an older version, or you have regenerated the configure script?farrer {l Wrote}:Tried it here, but also failed to compile (not sure, but seems a different error than the one reported by mdtrooper, but also related to libtheora compilation):
bzt {l Wrote}:That's the thing, you don't have up-to-date system libraries. (Just for the records, I use a rolling-release distro and it doesn't have it either.)
Yeah, deliberately, because only the latest version provides the API I need. (Which is the GetDuration call that returns the length of samples. I have no idea why this hasn't been implemented sooner, seems pretty basic.)dulsi {l Wrote}:That's because you are not using a released version. You are using a snapshot of latest development branch.
Don't you worry, sooner or later the development version becomes the release version.dulsi {l Wrote}:I don't know if any distro uses the latest snapshots from git repos. I doubt anyone would.
Thanks! I did actually listen to the complaints and I've tried to address them all!mdtrooper {l Wrote}:Ohh, the current Makefile is awesome. It is very easy to build. I think it was a big work to change.
Vielen Dank! But I don't consider myself fluent, I had to rely on GT more than I'd like to admit. I remember most of the grammar, but my vocabulary is pretty poor, haven't practiced German for years so I have forgotten the words.PeterX {l Wrote}:Hello as a German I can say something about the German translation:
The German translation is generally very good. One can see that you (or whoever wrote it) is quite fluent in German.
Oooops, that's a typo, how could I missed that? Fixed right away!PeterX {l Wrote}:But it is "Deutsch" not "Deutch".
Good to know, fixed!PeterX {l Wrote}:It should be "Action-Rollenspiele".
Bem-vindo a TIRNANOG!
TirNanoG Editor é desenvolvido para criar jogos RPG de Aventura e Ação sem a necessidade de conhecimentos de programação.
Download (Linux) Visualizar o Código-Fonte
O link de download direciona ao binário de seu SO. Para jogar os jogos criados com este editor, você precisará do TirNanoG Player.
Esta aplicação é de código aberto e livre! Licenciada baixo GPLv3+.
O formato de arquivo de TirNanoG é licenciado de maneira dupla, ou CC-BY-NC-SA ou, sob permissão, qualquer outra licença, mesmo proprietária.
Templates
Você não precisa recomeçar tudo a cada novo projeto, o editor pode utilizar templates de jogos!
Multilíngue
Tanto o editor como os jogos criados possuem suporte completo a UNICODE e incluem ferramentas de tradução.
Cenas de Transição
TirNanoG possui um editor completo de cenas de transição, com opções de exibição de slides e subtítulos.
Mapas
Mundo aberto, com bilhões de mapas associáveis em 6 direções. Cmpatível com o editor de mapas Tiled!
Instalação
1. baixe um dos arquivos tnge-*.zip (~4Mb) para seu computador do repositório.
2. extraia para: C:\Arquivos de Programas (Windows), /usr (Linux), /Applications (MacOS)
3. Divirta-se!
Templates de Jogos
Salve os templates baixados para ~/TirNanoG. Não descompacte, somente salve. Você poderá selecioná-lo no editor quando criar um novo projeto.
Liberated Pixel Cup
Ortográfico, contém muitos - mas muitos mesmo - elementos para mapas e personagens modulares em quatro direções.
FantasyCore
Isométrico, com alguns elementos de mapa e somente um herói e uma heroína como personagens, mas em oito direções.
Templates de Módulo
Estes templates expandem seu projeto, para serem utilizados na função de "Importar template".
Documentação
* Manual do Usuário
* Estrutura detalhada do projeto e descrição dos arquivos
* Especificação do formato de arquivos do TirNanoG
Capturas de Tela
Tela "Acerca"
Fontes bitmap, pixmap e vetoriais
Importador de sprites
Editor de cenas de transição
Controladores de atributos e eventos
O editor de mapas
Users browsing this forum: No registered users and 0 guests