magnum

9986 Commits

21 Branches

19 Tags

70 MiB

Tree: ca16638c65

Commit Graph

Author	SHA1	Message	Date
Vladimír Vondruš	eba7cf6038	{image,scene}converter: print IDs of data that failed to import in --info. Otherwise it's really, REALLY hard to discover which data are missing in the output. Especially for files with 1700 meshes, 800 materials, 3600 textures and such.	4 years ago
Vladimír Vondruš	cc9159d387	{scene,image}converter: add --info options for plugins. Lists features, aliases as well as documented contents of the whole configuration file. Useful to not need to look up online docs when working on the command line.	4 years ago
Vladimír Vondruš	7067ed91c8	{scene,image}converter: split implementation and executable tests. They're each a totally different beast and putting them into the same test file doesn't really make sense: - We want to link certain plugins statically on static builds to test certain code paths in the implementation. However this is counter-productive for the executable tests because there we are checking for plugin presence from the test with the assumption that the executable and the test have the exact same set of plugins available (or linked statically). - The executable tests are implemented on Unix only at the moment, thus it's wasteful to try to build it on any other platforms. Having it in a separate file makes it much easier to deal with.	4 years ago

Author

SHA1

Message

Date

Vladimír Vondruš

eba7cf6038

{image,scene}converter: print IDs of data that failed to import in --info.

Otherwise it's really, REALLY hard to discover which data are missing in
the output. Especially for files with 1700 meshes, 800 materials, 3600
textures and such.

4 years ago

Vladimír Vondruš

cc9159d387

{scene,image}converter: add --info options for plugins.

Lists features, aliases as well as documented contents of the whole
configuration file. Useful to not need to look up online docs when
working on the command line.

4 years ago

Vladimír Vondruš

7067ed91c8

{scene,image}converter: split implementation and executable tests.

They're each a totally different beast and putting them into the same
test file doesn't really make sense:

 - We want to link certain plugins statically on static builds to test
   certain code paths in the implementation. However this is
   counter-productive for the executable tests because there we are
   checking for plugin presence from the test with the assumption that
   the executable and the test have the exact same set of plugins
   available (or linked statically).
 - The executable tests are implemented on Unix only at the moment,
   thus it's wasteful to try to build it on any other platforms. Having
   it in a separate file makes it much easier to deal with.

4 years ago

3 Commits (ca16638c65919126d00616e7f57b81bd2afb13bd)